Last updated 6 months ago

Adding a payment gateway

Rebilly supports card payments and other payment methods, such as ACH, PayPal, and even Bitcoin. The first step to accepting payments using Rebilly is to get a payment gateway and a merchant account ready.

What is a merchant account?

A merchant account is a type of bank account that allows businesses to accept payments in multiple ways, typically debit or credit cards. To get one, you'll need to apply with a merchant account provider. There are many providers -- the one that's best for you will depend on your business. We'd be happy to consult with you and recommend one if needed.

What is a payment gateway?

A payment gateway is a service that lets you accept payments made by your customers to your merchant account. It’s the online equivalent of a point-of-sale terminal which is present in a brick and mortar store. Rebilly is gateway-agnostic, meaning that we allow our clients to bring together whatever combination of merchant accounts and gateway accounts that makes the best business sense for them.

Rebilly is integrated with 100+ payment gateways. If you don’t see your choice of gateways on the list, we can likely complete a new integration in 1-3 weeks at no cost. If you don’t have a gateway account yet, we will be happy to help you choose. Contact us.

(TIP: You can set up multiple gateways if you have them. There's no limit!)

How to add a payment gateway

When you have a payment gateway (and a merchant account, depending on which payment gateway you decide to use) in place, the next step would be configuring your payment gateway in Rebilly.

First, go to settings > gateway accounts > add gateway account

connect payment gateway

TIP: For the purpose of this tutorial, we’ll be using the sandbox environment and the TestProcessor. To be able to accept live transactions, you’ll need to connect your gateway in the live environment.

  1. In the left navigation, select settings > gateway accounts: You can type to search your gateway account by name, or scroll through the logo’d buttons to find your gateway.
  2. Select your payment gateway: Some of the required fields will vary based off of the gateway you select.
  3. Enter a unique alphanumeric value for the gateway account ID: We recommend you use any identifier which may be easily recognizable to you within reports. This value will be seen in other configuration screens including rules, reports, and is also how this account is referenced within the API.
  4. Enter your gateway account credentials: This is different for each gateway account. TestProcessor doesn’t require credentials as it’s fictitious, but your real gateway account will. If you’re not sure what your credentials are, please contact your gateway account provider for help.
  5. Select the payment method: For example, if it's a payment card, you would select the card brands accepted, such as Visa, MasterCard, American Express, and Discover.
  6. Configure advanced settings for your gateway account: these settings are optional and can be updated at any time by editing your gateway account.
  7. Click “Save gateway account” to complete the setup.
  8. For applicable gateways, you may test that your credentials have been entered correctly by using the 'Check credentials' button at the top of the screen. If you have entered incorrect credentials, you will receive an error message. Re-enter your credentials (tip: check for any hanging spaces) and then check your credentials again.

Instant payment notifications (IPNs)

Payment gateways use static or dynamic IPNs. Static IPNs must be configured within the gateway’s user interface or in some cases it may need to be set by your account manager. Dynamic IPNs are pre-configured and do not require any further action. If you are unsure whether your payment gateway uses static or dynamic IPNs, please contact your gateway account manager.

All static IPNs have the following structure:

https://hook.rebilly.com/ipns/{gatewayName}/{merchantId}

Testing the payment flow

Always test a gateway account after creation.

Common problems include:

  • Entering the wrong credentials.
  • Requires 3rd party enablement.

Test it using our "virtual terminal" with your own payment cards.

Tip: Use the additional filters in the advanced configuration settings to limit the gateway to one or a few test customer IDs and test real transactions in the live environment before opening the gateway to real customers.