Submit originator data for Travel rule information request

POST 
/compliance/v1/information-requests/{externalId}/actions

Submits originator information for a crypto payment that BVNK is holding under the Travel Rule after the customer has sent the payment.

Only use this endpoint to release payments held for missing Travel Rule information. This situation occurs when you request a payment below 3,000 currency units without Travel Rule details, but the customer sends a higher amount. BVNK will then hold the payment and send a bvnk:compliance:v1:information-request webhook requesting the required information.

To proceed, provide the requested information programmatically by passing the data.id from the webhook as externalId. Once accepted, the payment will resume processing.

To prevent this scenario, always include Travel Rule information when creating a payment, regardless of the amount. For more details, see Provide additional party information.

Held payments may be direct crypto deposits, channel transactions, or crypto payments (MPS), as indicated by data.relatedPayment.type in the webhook. These payments also appear in the Missing Contacts queue in the Portal, where you can assign an originator manually if preferred.

Entity-specific requirements

The contact service has different externalId requirements based on entity type:

• INDIVIDUAL: externalId is required.
• COMPANY: externalId is optional.

Request

Responses

• 200
• 400
• 404
• 500

Information accepted; the held payment will resume processing.