¶ Overview
A gateway must be created in order to process credit card payments in RevCent. You must have an existing merchant gateway account with a third party in order to create a RevCent gateway. If you do not have an existing merchant account, contact us and we can help you acquire one.
¶ Available Gateways
If you don't see a gateway you need, let us know and we can integrate it.
| Name | 3DS2 |
|---|---|
| Adyen | |
| Authorize.net | |
| Braintree | |
| Cardpointe | |
| Checkout.com | YES |
| Cybersource | |
| Elavon Converge | |
| Maverick | |
| NAB Transact | |
| NMI | YES |
| PSiGate | |
| PayJunction | |
| PaySafe | YES |
| Pinwheel | |
| Stripe* | |
| WorldPay |
¶ Important Information Regarding Stripe
If you are processing live transactions with Stripe, you need to enable the "Handle Card Information Directly" setting in your Stripe account.
Read how to enable this setting.
¶ Gateway
¶ View All Gateways
View all gateways by clicking the Payments > Credit Card > Gateways link on the sidebar or going to https://revcent.com/user/gateways
¶ Create A Gateway
Create a new gateway by clicking the Create New Gateway button when viewing all gateways or go to https://revcent.com/user/new-gateway
¶ Name
Enter a name for the gateway. Required and must be unique.
¶ Description
Enter a description for the gateway.
¶ Status
Set the status of the gateway.
¶ Discount Rate
The percentage charged by the gateway for each successful credit card charge.
¶ Success Transaction Fee
The flat fee, if applicable, that the gateway charges for each successful credit card charge.
¶ Failure Transaction Fee
The flat fee, if applicable, that the gateway charges for each unsuccessful credit card charge.
¶ Main Gateway
Select the main gateway you are using. Once selected, the gateway credentials box will appear.
¶ Gateway Credentials
Depending on the merchant gateway selected, you will need to enter specific credentials. Credentials different for each merchant gateway. However, details are provided on the credentials you need. In the credential box above, Stripe was selected as the main main gateway.
Important: Enter the appropriate credentials depending on whether you wish to run live or test transactions using your gateway. You must also use the appropriate RevCent API Account that coincides with either live or test transactions.
Live/Test Example:
- Live Transactions: Enter your payments gateways' live credentials and also use a RevCent API Account that is set to live mode. By using a live RevCent API Account, RevCent will send transactions to your gateway's live endpoint.
- Test Transactions: Enter your payments gateways' test credentials and also use a RevCent API Account that is set to test mode. By using a test RevCent API Account, RevCent will send transactions to your gateway's test endpoint.
¶ Edit A Gateway
Edit an existing gateway by clicking the edit button when viewing all gateways.
¶ Name
Enter a name for the gateway. Required and must be unique.
¶ Description
Enter a description for the gateway.
¶ Status
Set the status of the gateway.
¶ Discount Rate
The percentage charged by the gateway for each successful credit card charge.
¶ Success Transaction Fee
The flat fee, if applicable, that the gateway charges for each successful credit card charge.
¶ Failure Transaction Fee
The flat fee, if applicable, that the gateway charges for each unsuccessful credit card charge.
¶ Deny Product Group(s)
Useful when a gateway prevents the sale of a restricted product. Select specific product group(s) to deny, preventing using this gateway if a sale has any product contained in selected product group(s).
Important: In order to prevent a payment from not being processed at all, and to ensure backup gateways are available, product group denial only applies when all of the criteria below are met.
- Is an initial sale transaction, i.e. initial purchase. (Not a subscription renewal, salvage transaction or trial expiration)
- A Payment Profile Cascade is used.
¶ Credentials
If you wish to modify the existing credentials for the gateway, click the Modify button and the modify credentials box will appear
¶ Modify Credentials
Depending on the merchant gateway selected, you will need to enter specific credentials. Credentials different for each merchant gateway. However, details are provided on the credentials you need. In the credential box above, Authorize.net was selected as the main main gateway. Please note that you must select the Confirm checkbox if modifying credentials.
Important: Enter the appropriate credentials depending on whether you wish to run live or test transactions using your gateway. You must also use the appropriate RevCent API Account that coincides with either live or test transactions.
Live/Test Example:
- Live Transactions: Enter your payments gateways' live credentials and also use a RevCent API Account that is set to live mode. By using a live RevCent API Account, RevCent will send transactions to your gateway's live endpoint.
- Test Transactions: Enter your payments gateways' test credentials and also use a RevCent API Account that is set to test mode. By using a test RevCent API Account, RevCent will send transactions to your gateway's test endpoint.
¶ 3DS2 Authentication
Some gateways offer the ability to utilize 3DS2 authentication for payment transactions. You can implement 3DS2 and use the RevCent API to send the 3DS2 variables to an enabled gateway. Read more about 3D Secure 2
¶ How It Works
3DS2 works via JavaScript code on your shopping cart/checkout page. When a customer clicks submit to complete payment, you first submit a request to the 3DS2 endpoint to retrieve 3DS2 authentication values/instructions. These values are then passed to the RevCent API, via the “three_ds” object when ready to process payment. RevCent will pass non-empty and non-null null “three_ds” values to the payment gateway according to the specific gateways specification.
3DS2 is not a plug and play solution, and requires a developer or someone with knowledge on JavaScript in the browser. Only specific gateways are supported, and each gateway requires their own browser implementation.
¶ API Request
To send RevCent the 3DS2 values returned from the browser, do so using the “three_ds” object in the sale > create API call. Example: https://revcent.com/docs/api#sale-create-credit-card
Example Sale > Create request with 3DS2 values in the “three_ds” object. Not all values are required, only the values returned in the browser from the gateways' 3DS2 endpoint.
{
"request": {
"type": "sale",
"method": "create",
"three_ds": {
"enabled": true, // Required if sending 3DS2 values to RevCent.
"version": "2.1.0", // The 3DS2 version. Example: "2.1.0" or "2.2.0".
"eci": "05", // The eCommerce indicator. Indicates the result of the attempt to authenticate the cardholder.
"cavv": "Y2FyZGluYWxjb21tZXJjZWF1dGg", // Cardholder Authentication Verification Value
"xid": "YXV0aCB0eG4gaWRzIGFyZSBmdW4=", // The transaction identifier from authentication processing.
"directory_server_id": "3f6fb1f8-f719-46c9-905b-bab446f4de30", // A transaction identifier assigned by the directory server.
"authentication_response": "verified", // Describing if a customer was successfully verified or attempted. Example: "verified" or "attempted".
"acs_transaction_id": "d6f15aae-2c9d-4333-a920-954be07c0c76", // Access Control Server (ACS) transaction identifier.
"algorithm": "1", // 3DS algorithm used.
"directory_response": "Y", // 3DS directory server response.
"enrollment_response": "Y", // Verify enrollment response/status
"three_ds_server_transaction_id": "" // 3DS server transaction id.
}
.....
}
}
¶ Supported Gateways
Supported gateways and third parties, with field mapping and links to instructions, are listed below.
Note: Each gateway returns specific fields to the browser upon 3DS2 authentication. These fields are mapped to the RevCent field in the “three_ds” object. Therefore, when making the API call, the response fields from the browser 3DS2 authentication request need to match the fields in the RevCent API call three_ds object according to the mapping table for each gateway below.
¶ NMI
| Gateway Response Field | RevCent API Field | Example Value |
|---|---|---|
| eci | eci | 05 |
| cavv | cavv | Y2FyZGluYWxjb21tZXJjZWF1dGg |
| xid | xid | OU9rcTRCY1VJTFlDWTFESXFtTHU= |
| directoryServerId | directory_server_id | 3f6fb1f8-f719-46c9-905b-bab446f4de30 |
| cardHolderAuth | authentication_response | verified |
| threeDsVersion | version | 2.1.0 |
¶ Paysafe
| Gateway Response Field | RevCent API Field | Example Value |
|---|---|---|
| eci | eci | 05 |
| cavv | cavv | AAABCIEjYgAAAAAAlCNiENiWiV+= |
| xid | xid | OU9rcTRCY1VJTFlDWTFESXFtTHU= |
| directoryServerTransactionId | directory_server_id | a3a721f3-b6fa-4cb5-84ea-c7b5c39890a2 |
| threeDResult | directory_response | Y |
| threeDEnrollment | enrollment_response | Y |
| threeDSecureVersion | version | 2.1.0 |
¶ Checkout.com
| Gateway Response Field | RevCent API Field | Example Value |
|---|---|---|
| eci | eci | 06 |
| cryptogram | cavv | 123feb70-d16b-4da6-b07f-98c0 |
| xid | xid | 79f6205c-ff5c-4a4c-8fca-90f67f3a6470 |
| version | version | 2.1.0 |
¶ PAAY
PAAY is not a gateway, it is a third party service we recommend for easy 3DS integration.
| PAAY 3DS Response Field | RevCent API Field | Example Value |
|---|---|---|
| eci | eci | 05 |
| authenticationValue | cavv | Y2FyZGluYWxjb21tZXJjZWF1dGg |
| dsTransId | directory_server_id | 3f6fb1f8-f719-46c9-905b-bab446f4de30 |
| protocolVersion | version | 2.1.0 |
| acsTransId | acs_transaction_id | d6f15aae-2c9d-4333-a920-954be07c0c76 |