result value is matched against the gateway node’s continuesWith configuration to determine which path the flow takes next.
ce-type: Finish
Payload
Outcome label matched by the flow’s gateway node.
Transaction result data returned by the integration service.
Data variants
The shape of thedata object depends on the integration and the result value. Common variants are shown below with their required fields.
Manual capture
When present and true this indicates a manual capture is required for the transaction.
3DS challenge
Payment transaction
Transaction status (required).
Transaction amount in minor units.
ISO 4217 currency code, e.g.
EUR.Array of decline reason codes (when applicable).
ISO 8601 timestamp when processing started.
ISO 8601 timestamp when processing finished.
External payment identifier from the processor.
Processor failure reasons (when applicable).
Internal payment identifier.
Merchant identifier at the payment processor.
Processor name.
Processor’s transaction identifier.
Processor-provided transaction timestamp.
Transaction type.
Bank transfer / payout
Data fields
Thedata object contains the beneficiary and routing details for the transfer. These fields are required when the bank_transfer variant is used; include them at the top of the bank_transfer payload so clients can quickly access routing information.
bic— Bank BIC/SWIFT code (required)beneficiary— Beneficiary name (required)iban— Beneficiary IBAN (required)reference— Payment reference (required)
data object:
Transfer status (required).
Transfer identifier.
Transfer type.
Start timestamp.
End timestamp.