Transaction types

Each of these is a step you can drop into a checkpoint from the Step Palette to run an actual payment transaction against a gateway.

Step	What it does	Notes
Get Payment Method Info	Not itself a transaction – pulls a stored payment method's brand, BIN, and address onto the canvas	Only needed when the checkpoint routes on card attributes (including BIN metadata) or another step needs card details. Otherwise, send the payment method token in the request.
Authorization	Reserves funds without capturing them	Requires transaction.amount and transaction.currency; supports stored-credential fields, an SCA provider key, network tokenization flags (attemptNetworkToken, provisionNetworkToken), and a callback URL/format for async (3DS/offsite) results
Purchase	Authorizes and captures in one step	Same Gateway Token pattern as Authorization
Capture	Completes a previously authorized transaction	Needs the authorizing transaction's token – wire this via Manage Input Data Sources (see the checkpoint guide)
Verify	Validates a payment method without moving money	Has its own Gateway Token and SCA provider key fields
General Credit	Issues a credit not tied to a prior transaction	Has its own Gateway Token field
Void	Cancels a prior authorization or transaction before it settles, releasing the held funds	Needs the authorizing transaction's token – wire this via Manage Input Data Sources (see the checkpoint guide)
Credit	Issues a refund against a specific prior transaction	Requires the prior transaction's token – wire this via Manage Input Data Sources (see the checkpoint guide)
Get Transaction Info	Read-only lookup that pulls the full state of a previously run transaction (outcome, gateway transaction ID, AVS/CVV codes, processor response, card metadata) onto the canvas	Only needs the transaction token

Fields common across steps

Gateway Token – set per step; when set, any transaction.gatewayToken in the request payload is ignored
environmentKey – overrides your org's default environment for that transaction (see Transaction processing)
scaProviderKey – identifies the 3DS provider to authenticate against, on steps that support SCA
retainOnSuccess – retains the payment method after a successful verification

For the full input list any given checkpoint needs, use Copy Schema as JSON from the Trigger node's Expected Data panel – see Building a transaction processing checkpoint.