curl --request POST \
--url https://api-sandbox.revolv3.com/api/Payments/authorization/{paymentMethodId} \
--header 'Content-Type: application/json-patch+json' \
--header 'x-revolv3-token: <api-key>' \
--data '
{
"onlinePaymentCryptogram": null,
"networkProcessing": null,
"amount": {
"currency": "USD",
"value": 30.99
},
"orderProcessingChannel": null,
"ecommercePlatformUrl": null,
"dynamicDescriptor": null,
"includeRawProcessorResponse": false,
"reportGroup": null,
"merchantInvoiceRefId": "1234-5678-9101"
}
'{
"networkTransactionId": "766bd6a3-8374-4183-afda-d6f6911fad61",
"paymentMethodAuthorizationId": 1,
"paymentMethod": {
"paymentMethodId": 1,
"billingAddressId": 1,
"billingAddress": {
"addressId": 1,
"addressLine1": "1 Default Street",
"addressLine2": null,
"city": "Los Angeles",
"state": "CA",
"postalCode": "90210",
"phoneNumber": null,
"email": null,
"country": "US"
},
"billingFirstName": "John",
"billingLastName": "Doe",
"merchantPaymentMethodRefId": "custom-payment-method-ref-id-001",
"paymentMethodAchDetails": null,
"paymentMethodCreditCardDetails": {
"binNumber": "411111",
"paymentLast4Digit": "1111",
"paymentExpirationDate": "0835",
"accountUpdateMessage": null,
"accountUpdateDateTime": null,
"accountUpdateCode": null,
"paymentAccountNumber": null
}
},
"paymentProcessor": "WorldPay",
"processorMerchantId": "10071676",
"responseMessage": "Approved",
"responseCode": "000",
"rawResponse": null,
"message": "Approved",
"processorResponseDateTime": null,
"authCode": null,
"processorTransactionId": null,
"revolv3ResponseCode": null,
"revolv3ResponseMessage": null,
"merchantInvoiceRefId": "1234-5678-9101"
}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:
curl --request POST \
--url https://api-sandbox.revolv3.com/api/Payments/authorization/{paymentMethodId} \
--header 'Content-Type: application/json-patch+json' \
--header 'x-revolv3-token: <api-key>' \
--data '
{
"onlinePaymentCryptogram": null,
"networkProcessing": null,
"amount": {
"currency": "USD",
"value": 30.99
},
"orderProcessingChannel": null,
"ecommercePlatformUrl": null,
"dynamicDescriptor": null,
"includeRawProcessorResponse": false,
"reportGroup": null,
"merchantInvoiceRefId": "1234-5678-9101"
}
'{
"networkTransactionId": "766bd6a3-8374-4183-afda-d6f6911fad61",
"paymentMethodAuthorizationId": 1,
"paymentMethod": {
"paymentMethodId": 1,
"billingAddressId": 1,
"billingAddress": {
"addressId": 1,
"addressLine1": "1 Default Street",
"addressLine2": null,
"city": "Los Angeles",
"state": "CA",
"postalCode": "90210",
"phoneNumber": null,
"email": null,
"country": "US"
},
"billingFirstName": "John",
"billingLastName": "Doe",
"merchantPaymentMethodRefId": "custom-payment-method-ref-id-001",
"paymentMethodAchDetails": null,
"paymentMethodCreditCardDetails": {
"binNumber": "411111",
"paymentLast4Digit": "1111",
"paymentExpirationDate": "0835",
"accountUpdateMessage": null,
"accountUpdateDateTime": null,
"accountUpdateCode": null,
"paymentAccountNumber": null
}
},
"paymentProcessor": "WorldPay",
"processorMerchantId": "10071676",
"responseMessage": "Approved",
"responseCode": "000",
"rawResponse": null,
"message": "Approved",
"processorResponseDateTime": null,
"authCode": null,
"processorTransactionId": null,
"revolv3ResponseCode": null,
"revolv3ResponseMessage": null,
"merchantInvoiceRefId": "1234-5678-9101"
}Headers
Optional identifier generated by the client to match its own logs with this request.
Allowed values: 1 to 128 characters, letters, digits and ., _, :, -.
Examples: order-12345, 3f2b8c1e-9d4a-4e7b-a1c5-6b0d2e8f7a91 (GUID), checkout:2026-11-02.17, retry_1.order-12345.
A valid value is returned in the Client-Request-Id response header and is stored with Revolv3 request logs, so it can be used when contacting support.
An invalid value is ignored and the request is processed normally. Do not send sensitive data in this header.
1 - 128^[A-Za-z0-9._:-]{1,128}$Path Parameters
Body
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.
100Response
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.
100Conditional. 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.
10000
