Instruction action required
Fires when compliance asks you for another document on a payment instruction. The instruction returns to review once you upload it.
Authorizations
JWT bearer token. Include as Authorization: Bearer <token>. See the Authentication guide for how to obtain one.
Body
Body of every webhook delivery. The event metadata sits at the top level and the event object in data. The body is identical on every retry and replay of the same event, and it is the exact content covered by the Webhook-Signature header.
Payload delivered for beneficiary payment-instruction lifecycle events (BENEFICIARY_INSTRUCTION_CREATED, BENEFICIARY_INSTRUCTION_APPROVED, BENEFICIARY_INSTRUCTION_REJECTED, BENEFICIARY_INSTRUCTION_ACTION_REQUIRED).
Each event corresponds to one payment instruction transition. The payload includes the affected instruction plus enough beneficiary context (id, customerId, entity, relationshipType) to act on the event without an extra lookup. To see the full set of payment instructions attached to a beneficiary, call GET /v1/beneficiaries/{beneficiaryId} on the fx-payment API.
Response
Acknowledged. Trace Finance considers any 2xx response a successful delivery.