Performs a payment authorization using raw payment method details (e.g., card number, expiration date, CVV, or bank account info), without capturing the funds immediately. This is typically used when you want to place a hold on the customer’s account — for example, to confirm availability of funds before fulfillment or booking.
You must provide the full payment data along with invoice details. The payment is validated with the processor, and if successful, an authorization is created and stored for later capture or reversal.
This endpoint is intended for PCI-compliant merchants, as it involves transmitting sensitive payment data directly.
The authorization can later be captured using the Capture endpoint or voided via Reverse Authorization.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The amount information for the payment.
Payment method information for this payment.
Supported payment methods:
Only one payment method type should be provided with a transaction. *Supported only for specific processors.
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 Allows 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.
3-D Secure is an additional authentication protocol for online card payments that allows the issuing bank to verify that the transaction is initiated by the legitimate cardholder.
Processors supporting this feature: WorldPay
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.
Unique identifier for a previously pre-authorized payment method.
The payment method information for the payment.
The name of the processor by which the transaction was processed.
The merchant account ID (MID) of the processor by which the transaction was processed.
The processor response message.
The processor response code.
Conditional. 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.
The message returned directly from payment processor or a special message provided by system.