Skip to content

Post-transaction flow

Send the Travel Rule message alongside broadcast and reconcile later updates.

Use this flow when your approval and release checks run before message creation. Send Travel Rule information as soon as the on-chain transfer is broadcast and the hash is available. Coordinate timing according to your requirements; the API does not broadcast or schedule the transfer.

1. Create the message with its hash

Set API_KEY to the key for the selected environment. Replace the example transaction and party values with your own data:

curl --location --request POST 'https://api-dev.cryptoswift.eu/transactions' \
  --header "x-api-key: $API_KEY" \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "asset": "BTC",
      "amount": 0.00341,
      "blockchainInfo": {
          "blockchain": "Bitcoin",
          "transactionHash": "cca7507897abc89628f450e8b1e0c6fca4ec3f7b34cccf55f3f531c659ff4d79",
          "origin": "17SkEw2md5avVNyYgj6RiXuQKNwkXaxFyQ",
          "destination": "1MLh2UVHgonJY4ZtsakoXtkcXDJ2EPU6RY",
          "destinationType": "CUSTODIAL"
      },
      "vaspInfo": {
          "beneficiaryVaspName": "SwiftExchange"
      },
      "originator": {
          "type": "NATURAL",
          "name": "Marwin Hillar",
          "accountNumber": "04143282398",
          "address": "Alexanderplatz 25, Berlin",
          "country": "DE"
      },
      "beneficiary": {
          "type": "NATURAL",
          "name": "Hanne Nikol",
          "accountNumber": "1MLh2UVHgonJY4ZtsakoXtkcXDJ2EPU6RY"
      }
  }'

The example assumes a published policy whose fallback rule returns PROCEED. Your tenant's published rules and current transaction data determine the actual decision; without published rules, ruleEngine.decision is null.

The request returns the Travel Rule message with an id. Store that ID alongside your internal withdrawal and blockchain transaction hash.

2. Handle the response and later updates

StatusMeaning for your integration
PENDINGDelivery or beneficiary identification is still pending.
DELIVEREDThe message reached the beneficiary VASP; its review may still be pending.
CONFIRMEDThe beneficiary accepted the message.
DECLINEDThe beneficiary declined; inspect statusReasoning and follow your exception process.
FAILEDProcessing encountered an error; retrieve the record and investigate.

The initial response can also contain risk results, warnings, and a Rule Engine result. Use the shared data model for field definitions. An API response is not confirmation of blockchain settlement.

Use webhooks for updates and recovery polling when notifications are missed. Reconcile by transaction ID and allow later updates to the same record.

3. Handle exceptions

A declined or failed message can arrive after funds have moved. Apply your exception and investigation process; changing a Travel Rule record does not reverse the blockchain transfer.

If you need a decision before sending funds, use the pre-transaction flow. For corrections to a message, follow the update constraints.

Next steps