Resume a payment
Resume a payment’s workflow execution from a paused state. This is usually required when a Workflow was paused in order to get further information from the customer, or when waiting for an asynchronous response from a third party connection.
Path parameters
id
ID of payment to resume.
Headers
X-API-KEY
Request
This endpoint expects an object.
resumeToken
A token containing any information that is sent back from the checkout to complete a blocked payment flow.
Response
Successful Response
id
The unique payment ID.
You can use this ID to retrieve the payment details, or perform downstream
operations.
date
The date and time at which the payment was created in UTC format.
dateUpdated
The date and time of the last payment update in UTC format.
cardTokenType
The type of card token used for the payment.
Only applies for card payments.
Allowed values:
orderId
Your reference for the payment.
amount
The amount you charged the customer, in minor units.
order
More information associated with the order.
customerId
The unique identifier for your customer.
customer
More information associated with the customer.
metadata
Additional data to be used throughout the payment lifecycle.
paymentMethod
The payment method options provided in the request, as well as the token used to process the payment.
processor
More information associated with the payment processor, including the processor name.
requiredAction
Required action to perform in order to resume the payment workflow. This can be requiring a 3DS check from the customer for instance.
statusReason
Check this field for more information regarding the payment’s status. This is especially useful when the status is DECLINED
or FAILED
.
transactions
A list summarizing the transactions that occurred while processing the payment.
Note: a refund is a separate transaction and so will appear in this transactions
list if a refund was performed.
riskData
Risk data associated with this payment.