Manually authorize a payment using a provided processor. This is useful if you want to authorize a payment without a workflow action. The processor merchant ID must be provided which can be found on the Integrations page. The processor name is optional but it must be provided if your account has multiple processors configured which share the same merchant IDs.
ID of the payment to authorize.
Optional key to make the request idempotent. Enables a safe retry of a request without risking the user being charged or refunded multiple times. The idempotency key must be generated by the client and needs to be unique for every new request.
The payment processor to use for this payment.
Successful Response
The unique payment ID.
You can use this ID to retrieve the payment details, or perform downstream operations.
The date and time at which the payment was created in UTC format.
The date and time of the last payment update in UTC format.
The type of card token used for the payment.
Only applies for card payments.
<=256 charactersYour reference for the payment.
The amount you charged the customer, in minor units.
More information associated with the order.
<=256 charactersThe unique identifier for your customer.
More information associated with the customer.
Additional data to be used throughout the payment lifecycle.
The payment method options provided in the request, as well as the token used to process the payment.
More information associated with the payment processor, including the processor name.
Required action to perform in order to resume the payment workflow. This can be requiring a 3DS check from the customer for instance.
Check this field for more information regarding the payment’s status. This is especially useful when the status is DECLINED or FAILED.
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.
Risk data associated with this payment.