Global Gateway Settings

Authorize.net

To signup for an Authorize.net account, please visit Authorize.net.

Authorize.Net works with merchant accounts in the US only, but can work with customers/consumers in the following areas:

  • All Countries
  • Product prices are in USD
  • Customers purchasing in other currencies will be charged in their local currency at the exchange rate in effect at the time of the transaction

API LOGIN ID AND TRANSACTION KEY

Chargify requires your API Login ID and Transaction Key in order to communicate with your Authorize.net account. Within your Authorize.net account, navigate to the following: Account –> Settings –> API Credentials & Keys –> API Login ID

Once you have obtained your credentials, please enter them into your Chargify site by navigating to Settings → Payment Gateway → Authorize.net.

REQUIREMENTS

You must possess an account from the domain of sandbox.authorize.net. Accounts based from the URL of account.authorize.net will not work with the Chargify integration and display authentication errors.
  1. Customer Information Manager (CIM) option must be turned on.

  2. You do NOT need the Automatic Recurring Billing (ARB) feature.

  3. You will also need a merchant account with a compatible bank. Authorize.Net works with most merchant accounts, such as Wells Fargo, Bank of America, etc. If you need an Authorize.Net account and a merchant account, please contact one of Chargify’s partners who will help get you setup with everything you need.

  4. Avoid making settings “required” under “Payment Form”. The default setting for most of these checkboxes is OFF, and they should remain on the defaults.

  5. Please do not change the Authorize.Net “Direct Response Delimiter” settings. By default, the Default Field Separator is a comma (,) and no Field Encapsulation Character is specified. Do not change it to pipe (|).

  6. DO NOT set “Card Code” to “Required” under Settings → Payment Form → Form Fields (setting this to Required here effectively rejects any transaction where the CVV is NOT provided, which will cause recurring transactions to fail!). Instead, mark the CVV as required in Chargify: Settings → Fields → Check the “Required?” box for “CVV”.

  7. Relax your AVS Settings in Authorize.net in Settings -> Address Verification Service -> Under General AVS Responses, uncheck G, U, and S. These settings must be unchecked if you wish to accept international payments.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

  • Authorize.net will export your data for $250/hour with a minimum of 4 hours.
  • They require a minimum of 300 subscribers to perform an export
  • Exports only occur 2 times per month, so please heed to this schedule constraint

Authorize.Net eCheck/ACH

For more information on Authorize.Net’s eCheck/ACH feature, please see our documentation here. The linked article provides a comprehensive overview of how eCheck/ACH functions within your Chargify and Authorize.Net accounts.

Authorize.Net Response Reason Codes

In most cases, when a transaction can’t be processed - Authorize.Net will respond with a number of fields that can help you diagnose the issue. The important fields to look at in the gateway output log, are response_code, response_reason_code and response_subcode. The first two (response_code and response_reason_code) are very useful at diagnosing an issue, as there is a publically accessable site that you can view here (Response Code Descriptions) which details the various combinations and the possible description of the issue. However, there are a number of combinations that don’t have any descriptive text at all, and those are:

Response Code Response Reason Code
1 1
2 2
2 3
2 4

Need to understand an Authorize.net response code? Here is a link to Authorize.net’s current response codes.

In these cases, the error is usually (not guaranteed) that the merchant isn’t “white listed” for that customers card. In this case, they will need to call their issuing provider and ask about the decline. In most cases, the issues can be resolved. In these cases, the customer will most likely have to call their issuing provider to solve the potential issue.

Authorize.Net AVS & Anti-Fraud Settings

Authorize.net has a comprehensive article that explains all of the AVS settings. It’s worth reviewing to familiarize yourself with the AVS codes. This is especially helpful when examining transaction responses from Authorize.net.

Authorize.Net Response Delimiter Setttings

Due to a recently discovered issue, Chargify currently requires that you not change the Authorize.Net Direct Response Delimiter Settings. If you do, some transactions that rely on AVS may fail. Additionally, if these settings are changed, some successful transactions may refuse to allow refunds, generating the error “The credit card number is invalid”.

You can restore your default settings by following this guide:

  1. Log In to your Authorize.Net control panel and click on “Settings”

  2. From the Settings screen, select “Direct Response”

  3. Make the following selections under Direct Response Delimiter. (Note: These are the defaults)

  • Delimited Response: Yes

  • Default Field Separator: , (comma)

  • Field Encapsulation Character: (none)

We will soon be fixing this problem so that your settings do not affect our ability to parse certain responses from Authorize.Net. If you have been affected by this problem, in particular if you receive the error “The credit card number is invalid” when attempting to issue a refund, contact us and we can usually help you fix the issue.

Authorize.Net Transactions failures

If your transactions fail with “The transaction was unsuccessful” or “{field} is required, you will have to investigate which settings are causing this to happen within the Authorize.Net interface.

One reason is that your Authorize.Net configuration might be “Requiring” certain fields that are a part of the Authorize.Net Payment Form settings. These settings actually affect API transactions as well, and all should be unchecked.


Bambora

Bambora was formerly Beanstream until May 2017. Bambora works with Merchant Accounts (and therefore, Chargify merchants) in these countries:

  • Canada
  • USA

Bambora works with customers/consumers in these countries:

  • All countries
  • Product prices in Canadian dollars or US dollars
  • Customers purchasing in other currencies will be charged in their local currency at the exchange rate in effect at the time of the transaction

To configure Chargify with a Bambora account, you will need:

MERCHANT ID, USER, PASSWORD, AND PAYMENT PROFILE API PASS CODE

You can locate your Merchant ID in the upper right corner of the Member Login screen after successfully signing in to your Bambora account.

The username and password are configured under:

Administration –> Account Settings –> Order Settings –> Use username/password validation against transaction.

You’ll need to check the checkbox and then create a username and password.

Payment Profile API Pass Code can be found under Configuration > Payment Profile configuration. You will need “Payment Profiles” enabled in your Bambora account in order to use this API key.

Sometimes, it’s a good idea to separate out the administrator from access that Chargify would use. To do that, follow these steps:

  • After you’ve logged into Bambora, click on Administration->User Manager
  • Click “Add user”, which brings up a dialog. Add the appropriate information, with a username like “chargify”
  • Make sure you records (somewhere) the username/password you’re going to use for this user - you’ll need to copy it back into your Chargify settings. When done, click “Add User” from within the dialog.
  • Change the permissions for the new user, by clicking the new user in the left list, to the following:

    • Recurring Billing = No Access
    • Payment Form = No Access
    • Web Terminal = No Access
    • Account Settings = No Access
    • Security = No Access
    • Language = English
    • Disabled = No
    • Secure Webspace = No Access
    • Payment Profile = Full Access
    • Company Info = Read Only
    • Credit Card Viewing = Masked Card
    • Reporting = Full Access
    • Administrator = No

When you have this configuration created, click the “Update” button.

REQUIREMENTS

  1. Please be sure you have Bambora’s card number storage service/option. We need that to store credit card numbers.

  2. You will need to configure your Bambora account to allow duplicate payment profile information. Here’s how:

    • Log in to your Bambora account and navigate to configuration –> payment profiles
    • Uncheck the boxes for “Do not allow profile to be created with card data duplicated from an existing profile.” and “Do not allow profile to be created with billing information duplicated from an existing profile.”
    • Click “Update” to save the changes.
  3. Using Bambora with the Chargify API: Bambora requires that every API request must include the customer’s name, address, state/province, zip/postal code, and country.

  4. Bambora only allows specific state/province and country codes to be used. Please review pages 64-67 of ‘Process_Transaction_API_Guide.pdf,’ available in the Bambora administration console under Documentation –> Processing –> Process Transaction API Guide.

  5. Bambora requires full address information to be submitted for every transaction, including billing phone number. If you are using Bambora, please set Chargify to require the full billing address (name, phone, street address, city, state/province, postal/zip, and country) on the hosted payment pages.

  6. When using Bambora, be sure to let Bambora know whether you intend to process transactions using US dollars or Canadian dollars. The currency setting in Chargify must match the currency set up by Bambora. Chargify is unable to detect if a there is a discrepancy in this setting.

  7. To use Chargify’s hosted pages with BBambora, you must enable billing address collection.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Bambora for more details

AMERICAN EXPRESS

Please note: American Express prevents Canadian merchants from accepting USD American Express unless you have an entity located within the United States.

Bambora and Chargify API Configuration

Bambora requires that every API request must include the customer’s name, address, state/province, zip/postal code, and country.

Bambora only allows specific state/province and country codes to be used. Please review pages 64-67 of ‘Process_Transaction_API_Guide.pdf,’ available in the Bambora administration console under Documentation –> Processing –> Process Transaction API Guide.

Bambora Troubleshooting

  1. If you get “Transaction Declined. Restricted transaction type.” then here’s what one of our very kind customers said about his experience…

Looks like the “Restricted transaction type” is due to Bambora setup. Here’s a helpful blurb for other Bambora users:

When setting up a Bambora account, you need to change the order settings for **Restrict Internet Transaction Processing Types** to allow both purchase and pre-auth transactions.

This setting can be found under **Administration** --> **Account Settings** -> **Order Settings**--> and by selecting the radiobutton for both types and hitting 'Update'
  1. The following very complete list of steps was graciously provided by Chargify customer:
  • Get a Bambora account or test account

  • Email Bambora support and ask for payment profiles to be enabled (may add extra cost)

  • In Bambora go to Configuration->Payment Profile Configuration in the Secure Payment Profile section click on “Generate New Code” for API Access Passcode and then hit “Update” at the bottom.

  • In Bambora go to Administration –> Account Settings –> Order Settings and under Transaction Validation options make sure “Restrict Internet Transaction Processing Types” is off - alternately make sure “Purchase or Pre-Authorization only “ is on. Turn use username/password validation against transaction on and enter a username and password.

  • In Chargify go to your product and under Settings->Payment Gateway configure Bambora using your merchant id, the username/password from #4 and the Payment Profile API Pass Code from #3.

  • You can only use each Bambora test card once for a customer. You must clear the information to use it again under Processing->Payment Profile in Bambora.


BPOINT

Chargify requires your Username, Password, Merchant Number, Pre-auth Facility Username, Pre-auth Facility Password and Pre-auth Facility Merchant Number in order to communicate with your BPOINT account.

To begin using the BPOINT API, you will need a BPOINT Checkout or Enterprise facility. An Administrator or Manager (T1) user will need to create an API user by following the steps below:

  • Login to the Merchant Back Office
  • Navigate to Admin » User Management
  • Click on Add New User
  • Enter the User Name and Email Address
  • Select the User Permission “API”
  • Enter your (Administrator/Manager(T1) user’s) password
  • Click on Create User

USERNAME, PASSWORD, MERCHANT NUMBER, Etc.

BPOINT requires separate “facilities” for normal purchase transactions and pre-auth transactions. Since Chargify uses both, you will need to have both configured for your account by BPOINT.

You will then need to generate API user credentials for both facilities and plug them in accordingly.

REQUIREMENTS

None

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact BPOINT for more details


Braintree

Chargify supports Braintree Blue (v2).

We support Braintree’s older “Orange” API/platform, which they no longer use for new accounts. Existing Chargify customers using Braintree Orange will continue to be supported indefinitely. New signups will automatically use Blue (v2).

Chargify supports all currencies listed here.Please verify that your currency is supported before proceeding.

MERCHANT ID, PUBLIC KEY, PRIVATE KEY, AND MERCHANT ACCOUNT ID (v2)

Your Merchant ID, Public Key and Private Key can be found under Account –> My User –> API Keys.

Your Merchant Account ID can be found under SettingsProcessing –> Merchant Account ID. Chargify will use your default Braintree merchant account for transactions if you do not provide a merchant account id.

LOGIN AND PASSWORD (v1) REQUIREMENTS

For PayPal: Signup for Paypal in Braintree account. Chargify will add a PayPal tab in “Settings”. Must select checkbox. Will appear on Hosted Signup Page “credit” or “paypal”

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

https://developers.braintreepayments.com/reference/general/currencies

BRAINTREE & MULTI-CURRENCY

Chargify will use your default Braintree merchant account for transactions if you do not provide a merchant account id. Therefore, Chargify will transact ONLY in the currency of your default Braintree merchant account, REGARDLESS of the Chargify currency setting. Please be sure that your currency is set to the currency of your default merchant account if not using a merchant account id, or currency of the merchant account id provided. Otherwise your customers will be shown the incorrect currency within Chargify.

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.

DATA PORTABILITY POLICY

Braintree’s Data Portability Policy can be found here.

Customer ID is the field used for vault_token when importing.

Note: Chargify does not support 3D Secure with Braintree at this time.

Braintree provides the ability for your customers to signup using their PayPal account. Most likey, you will be using the Braintree V2 gateway during configuration.

When enabled, a PayPal button will appear on the Public Signup Page. Customers will then have the option to pay by credit card or PayPal.

PayPal signups are limited to the Public Signup Page and Chargify Direct. You will not be able to sign up a Subscriber to pay with PayPal via the Chargify Admin UI.

Braintree Advanced Fraud Protection

For more information on configuring Braintree’s Advanced Fraud Protection, please view our Braintree-specific documentation here.

Braintree & Paypal

For more information on configuring your Chargify Site to use Braintree & Paypal, please view our Braintree-Paypal-specific documentation here.

Braintree and Chargify Direct

PayPal payments can also be used with Chargify Direct.


Chase Paymentech (Orbital)

LOGIN, PASSWORD, MERCHANT ID, TERMINAL ID

Login to your Chase dashboard and copy the Merchant ID and Terminal ID located at the top of your page under “Merchant DBA:

Your login and password will need to be created by the Chase helpdesk. The username and password will be a “connection user/pass” and not the login used to get into Chase.

REQUIREMENTS

“Failed with 412 Precondition Failed” = Get connection user/pass

Chase issues a specific ‘connection’ username and password that differs from the credentials used to access the login area of Chase Paymentech. It is specifically generated by their helpdesk. This credential set does not exist by default.

If the merchant is not approved, they may see an error message such as Profile: Merchant-Bin [xxxxxxxxxxxx]:[000002 is not active where xxxxx is their merchant number. In the event this is ever an issue contact gatewaysupport@chasepaymentech.com. At this time Chargify is certified to issue a username/passwords to the merchant.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Chase Paymentech for more information.


CyberSource

To configure the CyberSource gateway you’ll need your Merchant ID / account username and a Transaction Security Key for the SOAP Toolkit API.

MERCHANT ID AND SIMPLE ORDER API TRANSACTION SECURITY KEY

To get a Transaction Security Key, do the following:

  1. Log into your CyberSource business gateway

  2. Navigate to Account Management–> Transaction Security Keys–> Security Keys for the SOAP Toolkit API.

  3. Click on Generate Key.

  4. Copy the new key into the password field of your Payment Gateway configuration in Chargify.

REQUIREMENTS

Both Payment Tokenization and Recurring Billing must be enabled for your account in order to successfully process transactions with Chargify. Please request this through Cybersource Support if you are receiveing “General Failure”.

Additionally Billing address required by gateway.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Cybersource for more information.


Elavon “VirtualMerchant”

Chargify requires your merchant ID, PIN and User ID in order to communicate with your Elavon “Virtual Merchant”.

MERCHANT ID, PIN AND USER ID

Please contact Elevon for more information.

REQUIREMENTS

Tokenization must be enabled for card storage. Please contact Elavon to enable this feature. Tokenization is a paid add on through Elevon and, upon enabling, takes up to 72 hours to fully propagate.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Pleaes contact Elavon for more information.


Elavon “Fusebox”

Fusebox is Elavon’s new and enhanced hosted payment gateway. For more information, please visit their main website here.

MERCHANT ID, PIN AND USER ID

Please contact Elavon for more information.

REQUIREMENTS

N/A

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Pleaes contact Elavon for more information.


eWAY

Chargify requires your Customer ID, Username & Password in order to communicate with your eWay account.

CUSTOMER ID, USERNAME AND PASSWORD

Username and Password are the values you use to sign in to your eWAY Business Centre on the web. Customer ID is located at the bottom of your eWAY Business Centre.

REQUIREMENTS

In order to function properly, the eWAY gateway requires you to submit a billing address with every signup, so you should set the billing address as “required” in your Chargify Product setup.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact eWAY for more information.


eWAY Rapid 3.1

Chargify requires your API key and password in order to communicate with your eWay Rapid 3.1 account.

LOGIN AND PASSWORD

Go to My Account –> User Security –> Create User and complete the form.

Click on ‘Actions’ next to the new user and ‘View API Key’. This is your new API key and password for accessing Rapid API.

(Note: In many Rapid 3.0 transparent redirect API modules and sample code the API Key field is named as ‘Username’. You must use your API Key, not your Email address for Rapid API.)

REQUIREMENTS

In order to function properly, this gateway requires you to submit a billing address with every signup, so you should set the billing address as required in your Chargify Product setup. In order to enable refunds please enable “Rapid API Refunds” inside of MYeWAY.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact eWAY for more information.

CREATING AN API KEY

  1. Log in to your partner portal account using the link below for your country

https://www.eway.com.au/PartnerPortal https://www.eway.co.uk/PartnerPortal https://www.eway.co.nz/PartnerPortal

(Skip 2 and 3 for live accounts)

  1. Navigate to Resources > Sandbox/Testing and click on ‘Request Sandbox’ Note: Skip this step if you already have a Sandbox account

  2. Navigate to the Sandbox using the link below for your country

https://sandbox.myeway.com.au https://sandbox.myeway.co.uk https://sandbox.myeway.co.nz

Go to My Account –> User Security –> Create User and complete the form. Note: You can use the same email address and password as your main Sandbox account.

Click on ‘Actions’ next to the new user and ‘View API Key’. This is your new API key and password for accessing Rapid API.

Note: In many Rapid 3.0 transparent redirect API modules and sample code the API Key field is named as ‘Username’. You must use your API Key, not your Email address for Rapid API.

In order to enable refunds please enable “Rapid API Refunds” inside of MYeWAY.


First Data “Global Gateway e4”

Chargify requires your ECOMM Terminal Gateway ID in order to communicate with your First Data account.

Chargify supports the Payeezy gateway, (formerly First Data Global Gateway e4,) for USD and CAD transactions.

For more information, see First Data’s information here.

LOGIN AND PASSWORD

  1. Log in to your FirstData account

  2. Click the ‘Terminals’ Link on the right side of the page

  3. Select your ‘ECOMM’ Terminal

  4. On the Details page you will see:

  • Gateway ID: This is your login
  • Password: You will need to click the ‘create’ password to generate a new one.
  • Scroll to bottom of page and click ‘update’.

Note: prior to clicking ‘update’, the password field will still appear filled in. You must click ‘update’ in order for First Data to save the password!

REQUIREMENTS

  1. Gateway has to approve subscription transactions/recurring payments (TransArmor). Must contact merchant services to enable. Will take 24-48 hours to take effect once it is added to the account.

  2. If testing transactions in a “test” First Data account, help page that described how to enter a 4 digit code (like “1234”) into my demo gateway account: “When testing using your demo account follow the steps as outlined above, but rather 3. than requesting a token from your merchant services provider simply use any four digit value, such as ‘1234’ to enable tokenization.”

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Incapable/unwilling to export customer credit card data.


Vantiv (Litle & Co.)

Chargify requires your User, Password and MerchantID order to communicate with your Vantiv account.

USER, PASSWORD, MERCHANT ID

Vantiv will email the user, password and merchant id in an email to the merchant.

REQUIREMENTS

Merchant must certify for access to Vantiv gateway. Merchant should mention they are using Chargify, which will speed up the process.

Merchant must provide a list of Chargify’s IP addresses to be whitelisted by the gateway.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Vantiv for more information.


Moneris (CAD only)

You will need to provide the Store ID and API Token in order to configure the gateway with Chargify.

USERNAME AND PASSWORD

  1. Log into your Moneris Merchant Resource Center for Canadian merchants here

  2. Go to Admin > store settings > API Token (20-digits)

REQUIREMENTS

Vault may need to be enabled? See Moneris US.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Pleaes contact Moneris for more information.


Moneris US (USD only)

USERNAME AND PASSWORD

  1. Log into your Moneris Merchant Resource Center for US merchants here.

  2. Go to Admin > store settings > API Token (20-digits)

REQUIREMENTS

eSelect Plus Vault must be enabled. Please see Moneris’ article here.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Moneris for more information.


NMI Gateway

USERNAME AND PASSWORD

To use the NMI gateway within your Chargify account, simply use your NMI username and password to access the gateway within your Site.

REQUIREMENTS

  1. The Customer Vault service must be activated.

  2. DO NOT set “Card ID Verification” to “Is NOT Processed or CVV was not Provided” under Settings → Card ID Verification. This will cause the gateway to reject any transaction where the CVV is NOT sent causing all recurring billing transactions to fail.

  3. The following settings must be as configured below in order to successfully process cards within the NMI gateway.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact NMI directly for more information on their data portability policy.


Payment Express “PX Post”

Chargify requires you use PaymentExpress's PxPost product to successfully integrate with this gateway. If you do not have credentials for the PxPost product, please contact Payment Express before proceeding with the instructions below.

Chargify supports Payment Express (also called “DPS” in some places), a Payment Gateway in Australia. Customers purchasing in other currencies will be charged in their local currency at the exchange rate in effect at the time of the transaction

Chargify utilizes the Token Billing feature of Payment Express accounts.

This means that we store the card number securely in the Payment Express vault, and when we do, a “Validate” transaction is invoked which attempts a $1.00 authorization transaction to ensure card validity.

According to PaymentExpress, Validate transactions are not enabled by default, so you must make a support request with DPS to have the Validate transaction type enabled.

Chargify requires your username and password in order to communicate with your Payment Express account.

USERNAME AND PASSWORD

The PxPost username is issued to you directly via email from the PaymentExpress support team once your account is activated. You will be prompted to call the PaymentExpress support line for the issue of the PxPost password as this is sensitive to your account. The credentials required for the integration are for PxPost, as opposed to the web portal or PxPay API FYI.

REQUIREMENTS

  1. Chargify utilizes the Token Billing feature of Payment Express accounts. This means that we store the card number securely in the Payment Express vault, and when we do, a “Validate” transaction is invoked which attempts a $1.00 authorization transaction to ensure card validity.

  2. According to PaymentExpress, Validate transactions are not enabled by default, so you must make a support request with DPS to have the Validate transaction type enabled.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Payment Express does not currently support data portability. Our token billing vault is designed with a one way data flow to prevent any data breaches.

However, Payment Express can accept customers moving from another gateway. They would arrange an sFTP batch for transfer of existing card numbers that need to be tokenized in the Payment Express System.

Payment Express Currency Settings

When using Payment Express, be sure to let them know what currency you want to use for transactions. The currency setting in Chargify must match the currency setting used by Payment Express, as well as by your Merchant Account.

Chargify is unable to detect if a there is a discrepancy in this setting.


Paymill

Paymill requires that you have a Public Key and Private Key to authenticate with Chargify.

To obtain these, please go to Development –> API Keys.

REQUIREMENTS

N/A

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

In case of export Paymill will need the following informations, and additionally, 500€ for each migration before they start the migration process.

Necessary information:

  • Name of the new PSP
  • Contact person and mail address of the new psp
  • Mobile phone number at the new PSP where the password for the encrypted file will be send to
  • PCI certificate of the new PSP
  • Public pgp key of the new PSP

Informations about the process for the new PSP can be found at here..


PayPal Website Payments Pro “Legacy Edition”

This gateway is no longer available for use within Chargify. To access PayPal, please use the Braintree Gateway.

Chargify 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.

API USERNAME, API PASSWORD AND SIGNATURE

In order to obtain your API Username, API Password and Signature, you must enable API Access with PayPal.

To obtain your API Username, API Password and Signature:

  • Login to Paypal –> Profile –> Request API credentials –> Option 1 (Paypal API) –> Setup Paypal Api credentials and permissions → Option 2 (Request API credentials to create your own API username and password) → View API signature

REQUIREMENTS

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 handled by Chargify.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

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, Chargify will verify your credentials. If Chargify 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 Chargify.

Important Note: By default, Chargify requires the CSC (also known as CVV) to start a new subscription or transaction. Due to PCI requirements, Chargify cannot store the CSC. Therefore, Chargify submits recurring transactions without the CSC, and your PayPal account must be configured to not require this value.

CONFIGURING CHARGIFY TO USE PAYPAL

Chargify 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:

  1. Log in to your PayPal account at paypal.com

  2. On the My Account tab, click on the Profile sub-tab.

  3. Click on API access or Request API credentials, depending on your PayPal account type.

  4. 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.

  5. If you have already requested an API Signature, you will now see your API credentials.

  6. The final page will display your API username, password and signature. All three pieces are required to connect Chargify to your PayPal Website Payments Pro account.

PEM versus Signature

Chargify 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.

ADDRESS REQUIREMENTS

PayPal Website Payments Pro requires full address information to be submitted for every transaction. If you are using PayPal WPP, please set Chargify to require the full billing address (name, phone, street address, city, state/province, postal/zip, and country).

DATA PORTABILITY POLICY

As of the time of this publication, PayPal Website Payments Pro (Payflow) allows exporting to another Level 1 PCI compliant entity. For up to the minute portablity information, please contact PayPal directly.


PayPal Website Payments Pro US-CA-UK “Legacy Edition”

This gateway is no longer available for use within Chargify. To access PayPal, please use the Braintree Gateway.

In order to configure PayPal Website Payments Pro for use with Chargify, you will need to provide Chargify with your API Username, API Password, and Signature.

If you have not enabled API Access on your PayPal account, you may do this by logging in to your PayPal account and doing the following:

  • In the “My Account” tab, click on the “Profile” submenu
  • Under the “Account Information” section, follow the “API Access” link
  • Follow the link for “Request API Credendtials” (under Option 2)
  • Select “Request API signature” (not “Request API certificate”) and click “Agree and Submit”

Important Notes & Error Conditions

  • On the Chargify gateway configuration screen, where we request your API Username and API Password, you will need to provide us with the Username and Password specific to your API Access - this is not the same as the username and password you use to log in to PayPal
  • Chargify sites in test mode will only work with the API credentials for a PayPal developer’s sandbox account (not a live PayPal gateway account)
  • Chargify sites in production mode will only work with the API credentials for a PayPal live account (not a developer’s sandbox account)

LESSONS FROM OTHER CHARGIFY MERCHANTS

  1. The error message “Security Header is Invalid” indicates a mismatch between Live/Test in Chargify and Live/Sandbox in PayPal. If it’s REALLY not that problem, then you need to contact PayPal and complain. Usually, things start working again within 24 hours, even though they will tell you that nothing was wrong on their end.

  2. The error message “Credit Card is Invalid” can be very misleading. We get this message when the real problem is that we have used the wrong API credentials or we have a mismatch between Chargify and PayPal Live/Test modes.

DATA PORTABILITY POLICY

As of the time of this publication, PayPal Website Payments Pro (Payflow) allows exporting to another Level 1 PCI compliant entity. For up to the minute portablity information, please contact PayPal directly.


Pin Payments

Chargify requires your API Secret Key in order to communicate with your Pin Payment account.

Accept credit card payments with Australia’s first all-in-one online payment system. To sign up for an account, please visit Pin Payments here.

API SECRET KEY

Please contact Pin Payments for more information.

REQUIREMENTS

Please check “Require Billing Address” in the product setup settings, as Pin normally requires all customers to supply an address.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Released 2/9/2016

If you choose to move from Pin Payments to another PCI compliant payment provider they’ll happily assist with migrating your customer card data.

if you’re moving to Pin Payments from another provider and they support data portability (like any good provider should) they can work with them to bring your customer card data across to Pin Payments.

For more information, please read the article from Pin Payments here.


Quickpay

Chargify requires your Merchant ID and MD5 in order to communicate with your Quickpay account.

MERCHANT ID AND MD5

To obtain your Quickpay Merchant ID, login to Quickpay, navigate to Settings –> Merchant –> and copy the QuickpayID. The Merchant ID is also on the front page of your account.

To obtain your MD5 Secret, login to Quickpay, navigate to Settings –> MD5 Secret –> and copy the MD5 secret.

Once you have obtained your credentials, please enter them into your Chargify site by navigating to Settings –> Payment Gateway –> Quickpay.

REQUIREMENTS

  1. In order for Quickpay to process recurring payments through Chargify, you must enable Subscription Payments. Login to your QuickPay account, navigate to Settings –> Acquirers and select “enable subscription payments” (requires a separate agreement with Nets).

  2. You must enter Chargify’s IP addresses in your QuickPay account. Login to your QuickPay account, navigate to Settings → API Access → and enter the following IP addresses into the “Allowed API IP addresses” section: https://chargify.zendesk.com/entries/20559136-Chargify-IP-Addresses

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact Quickpay for more information.


Stripe

Chargify requires you to “Connect with Stripe” in order for us to communicate with your Stripe account.

REQUIREMENTS

When prompted, allow access by clicking “Connect my Stripe account”. The Chargify application will have access to your Stripe data, and can create payments and customers on your behalf.

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

SWITCHING TO LIVE MODE

Stripe’s documentation on how to switch to live mode.

DATA PORTABILITY POLICY

Please see Stripe’s article on Data Portability here.


TrustCommerce

Chargify requires your CustID and Password in order to communicate with your TrustCommerce account.

CUSTID AND PASSWORD

Please contact TrustCommerce for more information.

REQUIREMENTS

None

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Please contact TrustCommerce for more information.


Wirecard

Chargify requires your Username, Password and Business Case Signature in order to communicate with your Wirecard account.

USERNAME, PASSWORD AND BUSINESS CASE SIGNATURE

Please contact Wirecard for more information.

REQUIREMENTS

None

CURRENCIES & MERCHANT LOCATION

For full information on currency and merchant location support, please view our payment gateway overview page.

DATA PORTABILITY POLICY

Note: Chargify does not support 3D Secure with Wirecard at this time.