Update Travel Rule transactions
Attach a hash, correct writable data, or record a permitted status decision.
Use PATCH /transactions/{id} from your backend to update fields supported by the Update transaction endpoint (Sandbox). Send only the fields you intend to change.
Writable data and restrictions
The update schema supports optional transaction data such as amount, asset, metadata, party/VASP information, and supported blockchain fields. Consult the endpoint schema for the full contract.
directioncannot change after creation.blockchainInfo.destinationis excluded from the update schema. Verify the destination before creating the record.id,travelRuleMessageSource,amountUsd, andamountEurare not writable update fields.- For CodeVASP outgoing messages, you may attach the first hash or resend the identical hash; an existing hash cannot be replaced or cleared.
- Network-specific identifiers, including CodeVASP recipient entity IDs and Ospree transfer IDs, cannot be changed through the corresponding outgoing VASP extra-info field.
Attach a transaction hash
curl --request PATCH "https://api-dev.cryptoswift.eu/transactions/{transactionId}" \
--header "x-api-key: $API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"blockchainInfo": {
"transactionHash": "cca7507897abc89628f450e8b1e0c6fca4ec3f7b34cccf55f3f531c659ff4d79"
}
}'
HTTP/1.1 200 OK
This success response has no body. Do not parse it as JSON.
Read the updated record:
curl --location 'https://api-dev.cryptoswift.eu/transactions/233e3fd4-2ef0-477c-a398-8f993d131a19' \ --header "X-Api-Key: $API_KEY"
{
"id": "233e3fd4-2ef0-477c-a398-8f993d131a19",
"status": "DELIVERED",
"statusReasoning": null,
"direction": "OUTGOING",
"createdAt": "2026-11-11T09:00:00.000Z",
"asset": "BTC",
"amount": 0.00341,
"amountUsd": 240.18,
"amountEur": 221.5,
"metadata": null,
"blockchainInfo": {
"transactionHash": "cca7507897abc89628f450e8b1e0c6fca4ec3f7b34cccf55f3f531c659ff4d79",
"origin": "17SkEw2md5avVNyYgj6RiXuQKNwkXaxFyQ",
"destination": "1MLh2UVHgonJY4ZtsakoXtkcXDJ2EPU6RY",
"destinationType": "CUSTODIAL",
"blockchain": "Bitcoin",
"isDestinationConfirmed": true,
"destinationWalletId": 7069
},
"vaspInfo": {
"originatorVaspName": "Example Originator VASP",
"originatorVaspEmail": "support@originator.example",
"beneficiaryVaspName": "SwiftExchange",
"beneficiaryVaspEmail": "support@beneficiary.example",
"beneficiaryVaspExtraInfo": null
},
"originator": {
"type": "NATURAL",
"name": "Marwin Hillar",
"accountNumber": "04143282398",
"address": "Alexanderplatz 25, Berlin",
"country": "DE"
},
"beneficiary": {
"type": "NATURAL",
"name": "Hanne Nikol",
"accountNumber": "1MLh2UVHgonJY4ZtsakoXtkcXDJ2EPU6RY"
},
"travelRuleMessageSource": "CryptoSwift",
"riskScore": {
"originatorRiskScore": 18,
"originatorRiskSeverity": "low",
"beneficiaryRiskScore": 12,
"beneficiaryRiskSeverity": "low",
"sanctions": {
"originatorWallet": {
"isSanctioned": false,
"details": []
},
"beneficiaryWallet": {
"isSanctioned": false,
"details": []
}
}
},
"ruleEngine": {
"decision": "PROCEED",
"ruleEngineId": "6292e827-ce05-4cae-a3c8-43e1fb073e1e",
"ruleId": "hash-attached",
"ruleName": "Payment broadcast",
"conditions": {
"all": [
{
"field": "hasTxHash",
"operator": "EQ",
"value": true
}
],
"any": []
},
"ruleEngineVersion": 3,
"scope": "OUTGOING",
"waitForSeconds": null,
"onTimeoutDecision": null
},
"warnings": []
}
Adding the hash links an existing message to the transfer. It does not confirm beneficiary review or blockchain settlement.
Apply a status decision
| Record direction | Status decision |
|---|---|
INCOMING | Use CONFIRMED to accept the message or DECLINED with a non-empty statusReasoning to decline it. You cannot set CANCELLED or change the status of a record already cancelled by its originator. |
OUTGOING | Use CANCELLED with a non-empty statusReasoning when abandoning a payment before broadcast. Do not set responder statuses such as CONFIRMED or DECLINED. |
Cancellation is rejected with 422 when the outgoing message is already CONFIRMED or DECLINED and has a transaction hash. Unsupported direction/status changes and missing required reasons return 400. Updating the message never reverses an on-chain transfer.