Transactions

Refund transaction

Send funds back to the source of a transaction.

POST/refund-transaction/{transaction_id}

Authorization

If set, the API uses an API key for authentication. Include the following header in your requests: X-blnk-key: <api-key>.

Replace <api-key> with your secret API key. Ensure the key is kept secure and not exposed in public repositories or client-side code.

See also: Core API key.

Path

transaction_idstringrequiredpath

The original transaction ID from the lineage. Blnk resolves refundable records through parent lineage - use the ID returned when you recorded the transaction, or the split parent in meta_data.QUEUED_PARENT_TRANSACTION. Do not pass a VOID child’s ID.

Body

skip_queuebooleandefault falsebody

When true, processes the refund synchronously instead of placing it on the transaction queue. Requests without a body keep the default queued behavior.

dry_runbooleandefault falsebody

When true, Blnk projects the refund without writing anything and returns a preview. See Dry-run a transaction.

descriptionstringbody

Narration for the refund. When omitted or empty, the refund copies the original transaction’s description.

meta_dataobjectbody

Additional metadata for the refund. Blnk merges these keys onto the metadata inherited from the original transaction. Keys you send replace matching keys; other keys stay on the refund. An empty object is ignored. The original transaction is not modified.

Response

Same JSON structure as Record a transaction