Skip to content

Board a merchant

From a signed merchant to one that is ready to test: its permissions, users, test project and contracts, and the hand-over. In the Admin portal or with the Boarding API.

A new merchant has signed with you and needs to take payments. Boarding gets it ready: you record who it is and what it may do, give its staff a login, add its webshop or app, connect it to a processor and set up how it gets paid. You do each step in the Admin portal, or your developers automate it with the Boarding API.

When you're done, the merchant has a project in test mode, its staff can log in, and its developers have what they need to integrate. Then you test it.

Before you begin

  • You have access to the Admin portal, or an admin API key for the Boarding API.
  • Acquirers on Silverflow: your BIN key and the merchant's MID per card scheme.
  • PayFacs and ISOs: ask your processor to board the merchant now, as that can take a while. You need the merchant's credentials from your processor when it goes live.
  • You know how merchants, projects, users and roles relate: see Merchant hierarchy.

Acquirers on Silverflow: collect these details first

Ginger boards the merchant at Silverflow when you save the contract, and the boarding fails without: a website URL and a billing address on the merchant, an international phone number (such as +31201234567) of its general contact person or else of the merchant, and the merchant category code (MCC) of the project. See what boarding needs.

Board the merchant

Create the merchant and its permissions

  1. Go to Merchants and click Create Merchant.
  2. Enter the Company name, the Email and, optionally, an External ID: your own identifier of the merchant.
  3. Click Create Merchant. The merchant starts with status pending.
  4. Open the merchant, edit its permissions and give it the payment methods it may use. These base permissions are the boundary for the permissions of its projects, roles and users. Click Save permissions.

Create roles and users

Give the merchant an admin role with full access, and other roles as needed, such as support or finance. Then create the merchant's first user, its admin and primary contact, and give it the admin role. Each email address can be used by one user only.

A merchant created in the Admin portal already has four roles: Merchant Administrator, Merchant Support, Merchant Manager and Merchant Member. Use Merchant Administrator for the admin, or add your own roles:

  1. Go to Roles, click Create Role, enter a Name and Description, and save. Edit the Role permissions: they can't exceed the merchant's permissions.
  2. Go to Users, click Create User, enter the Name, the Email and a phone number in international format, such as +31201234567, and pick the Roles. Type a Password for the user, or click Generate new password, and pass it on to the user safely. The user's Status is active unless you choose another. Save.

Complete the details

  1. Open the merchant, go to Details and click Edit.
  2. Fill in the Website URL, Phone numbers, Addresses (with a Billing address), Locale, VAT number and Chamber of commerce number, and optionally tags. Select the user you created as the primary contact: Silverflow calls it the general contact person. Click Save changes.

Create the test project

A project is one webshop or app of the merchant, with its own API key, webhook URL and payment methods. A merchant has a test project and a live project for each. Create the test project now, with status active-testing: it takes test payments only. You create the live project when the merchant goes live. See Project statuses.

  1. Go to Projects and click Create Project.
  2. Enter the Trade Name (the name shoppers see), Description, Website URL, Webhook URL, Status and, optionally, the External Project ID.
  3. Click Create Project.
  4. On Silverflow: open the project, click Edit, add the MCC and save.

Add the contracts

Give the test project the contract of each processor or payment method it uses. The fields depend on the contract type: see Processor contracts and the connector pages.

The test credentials of your card processors are set on your platform: PayFacs and ISOs don't enter the merchant's credentials on a test project. Vipps MobilePay and Swish are the exception: see their pages. You enter those in the live project's contract when the merchant goes live.

  • Acquirers on Silverflow: you don't enter credentials either, but Ginger boards the merchant at Silverflow. Choose the boarding mode full-merchant, and per card scheme enter your BIN key and the merchant's MID. When you save, Ginger creates the merchant in the Silverflow sandbox. Check that the boarding status is "Boarding succeeded". See Add the Silverflow contract.
  • PayFacs and ISOs: switch on your processor's contract and set its currencies, card brands and capture mode. See the contract of Elavon, Rapyd, Shift4 or IPG.

If the merchant takes one-click or recurring card payments, switch them on in the merchant's card settings: they're off by default.

  1. Open the project and go to the Payment Method Contracts tab.
  2. Switch on the payment method to give the project permission for it.
  3. Click the contract, fill in the fields and click Save contract.

Set up 3-D Secure and fraud prevention

Optional. Ginger fraud rules always apply to every project. Add rules, or screen the project's payments with SEON or Cybersource too: see Fraud prevention. To decide when 3-D Secure runs, see Dynamic 3-D Secure rules.

Set up payouts and fees

Only when your platform pays out the merchant with Ginger Payout, for acquirers on Silverflow. Your Ginger contact switches Ginger Payout on for your platform on request. Add a payout configuration with a schedule, a bank account and a price plan. See Payouts and fees.

Activate the merchant

Set the merchant's status to active. Its test project still takes test payments only.

Open the merchant, go to Details, click Edit, set the Status to active and click Save changes.

Hand over to the merchant

Send the merchant what it needs to start:

  • Its login. The email address and password of its admin user, through a secure channel. Its staff log in to the Merchant portal.
  • Its API key. The project's API key is on the project's Integration tab, and in the merchant's own Merchant portal. Its developers use it with the Order API.
  • The payment acceptance docs. Send its developers to the payment acceptance docs and their go-live checklist.

Next steps