result value is matched against the gateway node’s continuesWith configuration to determine which path the flow takes next.
ce-type: Finish
Payload
string
required
Outcome label matched by the flow’s gateway node.
object
required
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
boolean
required
When present and true this indicates a manual capture is required for the transaction.
3DS challenge
object
Payment transaction
object
string
required
Transaction status (required).
number
Transaction amount in minor units.
string
ISO 4217 currency code, e.g.
EUR.array
Array of decline reason codes (when applicable).
string
ISO 8601 timestamp when processing started.
string
ISO 8601 timestamp when processing finished.
string
External payment identifier from the processor.
array
Processor failure reasons (when applicable).
string
Internal payment identifier.
string
Merchant identifier at the payment processor.
string
Processor name.
string
Processor’s transaction identifier.
string
Processor-provided transaction timestamp.
string
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: