Processes a direct sale transaction using full payment method details (e.g., card number, expiry, CVV, ACH info). This is a one-step charge operation — the payment is authorized and captured immediately.
You must provide customer and invoice details along with raw payment data. This method is typically used by PCI-compliant merchants who collect and transmit sensitive payment data from their own secure front end. Use this endpoint when a tokenized method is not yet available, or when the payment is initiated for a new customer.
⚠️ PCI DSS compliance is required to handle raw card or bank account data directly.
Quick Starts:
Related Links:
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Invoice information for this 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.
The unique identifier of the customer.
Determine whether to return raw processor data in the response.
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.
Network processing information.
Processors supporting this feature: Adyen, Nuvei, WorldPay, TSYS, BridgePay, Paymentech, PaymentLync.
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 unique identifier of the customer.
The unique identifier of the invoice.
Merchant's unique identifier for the invoice.
Merchant's unique identifier for the payment method.
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.
The current status of the invoice.
Possible values: Paid, Pending, Noncollectable, Failed, OneTimePaymentPending, RetryPending.
The status of the invoice attempt.
Possible values: Success, Fail, Pending, RetrySuccess, RetryFail, RetryPending.
The message returned directly from payment processor or a special message provided by system.
The amount information for the payment.
The unique identifier for the payment method information.
Specifies the type of payment method used for the transaction. Examples include CreditCard (1), Ach (2), GooglePay (3) and ApplePay (4).
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.
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 details of credit card payment method.
The processor response message.
The processor response code.