Authorize With Payment Method Id
Performs a payment authorization using a previously stored payment method, referenced by its unique ID. The funds are held on the customer’s account but not captured immediately.
This endpoint is typically used in multi-step checkout flows, bookings, or delayed fulfillment scenarios. It improves security and UX by leveraging saved payment methods, eliminating the need to re-enter payment data.
The authorization can later be captured using the Capture endpoint or voided via Reverse Authorization.
Related Links:
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The unique identifier for the payment method information
Body
The amount information for the payment.
Network processing information.
Processors supporting this feature: Adyen, Nuvei, WorldPay, TSYS, BridgePay, Paymentech, PaymentLync.
Specifies the sales channel through which the shopper provides their card details.
Ecommerce - Internet or electronic commerce transaction. Moto - Single mail or telephone order transaction.
Processors supporting this feature: WorldPay, BridgePay. For other processors, Ecommerce is used by default.
Ecommerce, Moto The merchant's storefront or e-commerce platform URL or domain from which the transaction originates. If provided, this value will be sent to the processor (TSYS only) as the Acceptor URL Address. If not provided, the value configured in Merchant Details (E-Commerce Platform URL) will be used. If neither is available, the request is sent to TSYS without the Acceptor URL Address.
100Allows the merchant to define a dynamic descriptor, which appears in the payment statement. For dynamic descriptor, special configuration is required.
Processors supporting this feature: Nuvei, WorldPay, BridgePay, EPX, Paymentech, PaymentLync.
Determine whether to return raw processor data in the response.
Response
OK
The identifier returned for Visa, Mastercard, and Discover transactions. Visa and Discover use this value to link subsequent payments in a recurring/installment stream back to the initial transaction. You must include this value in the request message (originalNetworkTransactionId element) for subsequent recurring payments.
100Unique identifier for a previously pre-authorized payment method.
1 <= x <= 1000000000The payment method information for the payment.
The name of the processor by which the transaction was processed.
100The merchant account ID (MID) of the processor by which the transaction was processed.
100The processor response message.
500The processor response code.
10Conditional. The value is returned if includeRawProcessorResponse = true. This field contains the raw data received from the processor after attempting to bill this payment. It does not contain any sensitive information. The field value is a string with the serialized response from the processor in JSON format.
10000The message returned directly from payment processor or a special message provided by system.
500UTC timestamp of the payment processor response (format: YYYY-MM-DDThh:mm:ss).
40Transaction authorization code.
20Payment Processor Transaction Id.
100Standardized internal response code indicating the outcome of the request.
10Message providing additional details about the response code.
500
