curl --request POST \
--url https://api.revolv3.com/api/Payments/authorization/{paymentMethodId} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json-patch+json' \
--data '
{
"networkProcessing": {
"processingType": "InitialRecurring",
"originalNetworkTransactionId": null
},
"amount": {
"currency": "USD",
"value": 30.99
},
"orderProcessingChannel": null,
"dynamicDescriptor": null,
"includeRawProcessorResponse": false
}
'{
"networkTransactionId": "8bfc333a-a71f-4021-9590-f1bdd2b3d28f",
"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": null,
"paymentMethodAchDetails": null,
"paymentMethodCreditCardDetails": null
},
"paymentProcessor": null,
"processorMerchantId": null,
"responseMessage": "Approved",
"responseCode": "000",
"rawResponse": null,
"message": null
}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.
curl --request POST \
--url https://api.revolv3.com/api/Payments/authorization/{paymentMethodId} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json-patch+json' \
--data '
{
"networkProcessing": {
"processingType": "InitialRecurring",
"originalNetworkTransactionId": null
},
"amount": {
"currency": "USD",
"value": 30.99
},
"orderProcessingChannel": null,
"dynamicDescriptor": null,
"includeRawProcessorResponse": false
}
'{
"networkTransactionId": "8bfc333a-a71f-4021-9590-f1bdd2b3d28f",
"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": null,
"paymentMethodAchDetails": null,
"paymentMethodCreditCardDetails": null
},
"paymentProcessor": null,
"processorMerchantId": null,
"responseMessage": "Approved",
"responseCode": "000",
"rawResponse": null,
"message": null
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Show child attributes
The amount information for the payment. Must NOT be less than zero.
USD, AED, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BMD, BND, BOB, BRL, BSD, BWP, BYN, BZD, CAD, CHF, CLP, CNH, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HTG, HUF, IDR, ILS, INR, IQD, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LYD, MAD, MDL, MKD, MMK, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SEK, SGD, SHP, SLE, SOS, SRD, STN, SVC, SZL, THB, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, UYU, UZS, VEF, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW, AFN, KPW, LRD, LSL, STD, SYP, TJS, ZMK, ZWD, SLL, MGA, HRK, CDF, BTN, BIF Show child attributes
Processing type is used to define the initial or subsequent transaction in a recurring or installment stream.
If no value is supplied, a transaction is considered a one-time payment and will not be linked to the initial one.
InitialRecurring, Recurring, InitialInstallment, Installment Element defines the networkTransactionId returned in the response messages for Visa, Mastercard, and Discover Auth/Sale transactions. You must include this element and the original value returned for subsequent (after the initial) recurring/installment payments.
Ecommerce, Moto Show child attributes
The internal merchant's ID, which is sent to the relevant card scheme.
The merchant name, as is displayed for the transaction on the consumer’s card statement. For payment facilitator only, might consist of the following structure: [Prefix]*[Sub Merchant Name] - where:
Recommended! An alternative method to define a prefix is by configuring it through the Revolv3 Portal.
Nuvei processor: the maximum length of the parameter is 22. Possible prefix length 3 or 5 or 7 or 12 characters. WorldPay processor: if the value is specified, it must be between 4 and 25 characters. Possible prefix length 3 or 7 or 12 characters. Field accepts numbers, letters and special characters as follows: ampersand, asterisk (zero or one), comma, dash, period, space, or pound sign. BridgePay processor: the maximum length of the parameter is 46.
The merchant (sub-merchant for payment facilitators) contact information, as is displayed for the transaction on the consumer’s card statement.
Nuvei processor: the maximum length of the parameter is 13. It can also be an email address. WorldPay processor: the maximum length of the parameter is 13. Field accepts only numbers. BridgePay processor: the maximum length of the parameter is 13.
The payment facilitator's sub-merchant's 2-letter ISO country code.
City.
OK
Show child attributes
Show child attributes
Show child attributes