Recurly gateway support is dependent on your business location. Please see http://recurly.com/features/payment-gateway-support for gateways supported in your country.
Accepted Payment Types
Recurly supports credit/debit payments from most card type approved by your merchant bank account and payment gateway. However, both Maestro and Laser cards cannot be used for recurring transactions, so Recurly does not support these card types.
Recurly also supports PayPal payments on Hosted Payment Pages for approved merchants.
- Chase Paymentech Orbital
- Litle & Co.
- Merchant eSolutions
- PayPal Payflow Pro
- PayPal Website Payments Pro
For pricing and signup information for a new production Authorize.net account, please visit Authorize.net.
Address Verification Service (AVS)
If your company accepts payments from international customers, you need to be aware of some the AVS shortcomings. Currently, AVS fails to match zip codes if the zip code contains letters. US Zip Codes are numeric but many international postal codes will contain letters and will fail to match on the zip code. In order to use AVS with international credit cards, we recommend allowing the transaction to proceed if the street address OR zip code matches.
Card Code Verification (CCV)
When a subscription is first created or a credit card number is updated, Recurly will submit the card number and CCV to your payment gateway. PCI regulations do not allow anyone to store CCV values (regardless of encryption), so it can only be used for the first request. Submitting the CCV with the first request increases the likelihood that the transaction will be approved and will reduce fraud. Banks typically allow subsequent transactions to process if previous transactions have been processed by the same merchant without problem.
API Login ID and Transaction Key
Recurly needs your API Login ID and Transaction Key in order to communicate with your Authorize.net account. Within your Authorize.net account, navigate to Account → Settings → API Login ID and Transaction Key.
Once you have obtained your credentials, please enter them into Recurly’s Payment Gateway configuration.
To configure Recurly with a Beanstream account, you will need:
- API username, also known as a Merchant ID
The username and password are configured under Administration → Account Settings → Order Settings → Use username/password validation against transaction. You’ll need to check that checkbox and then create a username and password.
The API user for Recurly is different than the normal user accounts configured in the Beanstream User Manager.
Beanstream requires full address information to be submitted for every transaction, including billing phone number. If you are using Beanstream, please set Recurly to require the full billing address (name, phone, street address, city, state/province, postal/zip, and country).
Please note: American Express prevents Canadian merchants from accepting USD American Express unless you have an entity located within the United States.
Recurly supports both Braintree Orange (v1) and Blue (v2). Recurly does not support 3D Secure with Braintree. Merchants requiring 3D Secure can use Recurly’s Hosted Payment Pages with Wirecard or Sage Pay.
Braintree & Multi-currency
Merchants wishing to use Braintree and multi-currency must configure multiple Braintree gateways - one for each currency. Please use your Merchant ID, Merchant Account ID, public key and private key. The Merchant Account ID identifies the currency that is available.
Merchants can find their merchant account IDs by logging into the control panel, clicking “Account > Processing” (in the upper right-hand corner of the page), then scrolling to the bottom of the page. The merchant account IDs available will be found in the ‘Merchant Account ID’ column in that table.
Chase Paymentech Orbital
Recurly support the Chase Paymentech Orbital, Global Platform. Please contact support before setting up your gateway.
In order for Recurly to connect to your Orbital account, you must ask Chase to configure your Orbital gateway to allow connections from Recurly. At the moment, we only support the Global Platform.
The Tampa platform only supports US Dollars and Canadian Dollars.
The Salem platform supports many more currencies. Please contact Chase for more information.
To configure the CyberSource gateway you’ll need your account username and a Transaction Security Key for the SOAP Toolkit API.
To get a Transaction Security Key, do the following:
Navigate to Account Management → Transaction Security Keys → Security Keys for the SOAP Toolkit API.
Click on Generate Key.
Copy the new key into the password field of your Payment Gateway configuration in Recurly.
Litle & Co.
Recurly supports Litle and Co for US merchants. Before Recurly can connect to your Litle account, you must first ask Litle to allow Recurly to connect.
Recurly supports Merchant eSolutions (MeS) for US merchants. In order to connect to your Merchant eSolutions account, you will need to know your
Profile Key from MeS.
PayPal Payflow Pro
PayPal Payflow Pro is a payment gateway only product. Recurly supports Payflow Pro in the US, UK, Canada, and Australia.
PayPal Website Payments Pro
Recurly can use PayPal’s WebSite Payments Pro to process credit cards. The WebSite Payments Pro acts as a payment gateway and merchant account in one.
To get started with PayPal’s Website Payments Pro, you only need to sign up for their base account. You do not need their Recurring Payments feature—that’s completely handled by Recurly.WebSite Payments Pro only works for merchants located in the US, Canada, and UK. Due to PayPal restrictions, we cannot integrate with PayPal Website Payments Pro in any other country.
Card Security Code (CSC)
Some PayPal accounts are required to present the Card Security Code (CSC) for every transaction. After you setup your PayPal credentials, Recurly will verify your credentials. If Recurly determines your account requires CSC for every transaction, you will need to contact PayPal to disable this requirement before your account can be used with Recurly.
Important Note: By default, Recurly requires the CSC (also known as CVV) to start a new subscription or transaction. Due to PCI requirements, Recurly cannot store the CSC. Therefore, Recurly submits recurring transactions without the CSC, and your PayPal account must be configured to not require this value.
Configuring Recurly to use PayPal
Recurly requires the PayPal API Username, API Password, and Signature (preferred) or PEM Certificate to connect to your PayPal WebSite Payments Pro account. To retrieve your Signature from PayPal, follow these steps:
Log in to your PayPal account at paypal.com
On the My Account tab, click on the Profile sub-tab.
Click on API access or Request API credentials, depending on your PayPal account type.
PayPal will present two options: granting API permissions (Option 1) and requesting API credentials (Option 2). Select option 2. It may say View API Signature or View API Credentials.
If you have already requested an API Signature, you will now see your API credentials. Otherwise,
The final page will display your API username, password and signature. All three pieces are required to connect Recurly to your PayPal Website Payments Pro account.
PEM versus Signature
Recurly supports connecting to your PayPal account using the PEM or signature for credit card transactions. If in the future you wish to support payments via PayPal (in addition to credit cards), you must use the signature API credentials. If you have created a PEM certificate, you will need to delete the PEM certificate and walk through the process of choosing the signature credentials.
Canada and American Express
Please note, PayPal Website Payments Pro in Canada does not support American Express.
PayPal Website Payments Pro requires full address information to be submitted for every transaction. If you are using PayPal WPP, please set Recurly to require the full billing address (name, phone, street address, city, state/province, postal/zip, and country).
Recurly supports the Sage Pay gateway in the UK. A continuous authority merchant account number is required to work with Recurly and Sage Pay.
Sage Pay Setup
When configuring your Sage Pay setup, choose I want to use my own payment pages and leave the Form and Server product checkboxes unchecked.
Sage Pay requires a test transaction and refund against their test server to finalize your setup. Please contact Recurly support for assistance connecting to SagePay’s test server. SagePay’s instructions for processing these test transactions can be found at http://www.sagepay.com/help/faq/how_can_i_test_the_different_card_types.
Sage Pay requires a list of IP Addresses that will issue transactions on your behalf. The IP addresses that may issue transactions from Recurly:
Note: Merchants requiring 3D Secure with their Sage Pay account must use Recurly’s Hosted Payment Pages for customer checkout. Please contact support if you’d like notification when 3D Secure support is added to other integration methods.
Recurly supports Wirecard as a payment gateway.
Note: Merchants requiring 3D Secure with their Wirecard account must use Recurly’s Hosted Payment Pages for customer checkout. Please contact support if you’d like notification when 3D Secure support is added to other integration methods.