Sometimes several businesses want to take payments on the same device. Examples are businesses sharing premises or a shared self-service point. This article explains what Softpay supports in these cases.
How Softpay is structured
In Softpay, the structure is: Merchant → Store(s) → Terminal(s).
A merchant has one set of Softpay login credentials. These credentials give access to all stores under the merchant.
Each store can have its own acquiring agreement (e.g. its own MID). The default acquirer is set at merchant level.
Each Softpay app installation acts as a terminal for one merchant. Once the app is logged in, it will not accept another merchant's credentials. The only way to change merchant is to wipe or reinstall the app, which creates a new terminal.
This means a device cannot switch between different Softpay merchants from one payment to the next.
Option 1: One device per business
Each business has its own Softpay merchant, its own credentials and its own device. This is the simplest setup: each business is paid directly by its acquirer, and only has access to its own setup.
Option 2: The businesses as stores under one Softpay merchant
Several businesses can be set up as stores under one Softpay merchant, each store with its own acquiring agreement. This is a common setup, for example for franchise chains where each store is its own legal entity. Payments made in a store settle to that store's agreement, so each business is paid directly.
Things to be aware of:
Access: The merchant credentials give access to all stores. If the businesses are separate legal entities, the credentials should only be held by the integrator and used through the POS app. They should not be shared with the businesses.
Acquirer: The default acquirer is set at merchant level and applies to all stores under the merchant.
Sharing one device between stores: A device can be configured for more than one store. The terminal has to be configured for the right store before the payment. With AppSwitch, this is done with the ConfigureSoftpay action, which takes longer than a normal payment. Each store has its own terminal IDs (TIDs), and the device keeps a terminal in every store it has been configured for. Switching back to a store the device has used before is faster.
Names on screen and receipts: The merchant name shown in the Softpay app stays the same across stores. Receipts show the name of the store the payment was made in.
Option 3: One merchant with a POS reference on each payment
One business holds the merchant agreement and receives all payments. The POS sets a POS reference number (posReferenceNumber) on each payment to identify the business or order. The merchant of record then matches the references against the payouts and pays the other businesses.
The POS reference number is sent to the acquirer. See the POS reference number documentation.
The allowed length and characters vary between payment processors, and whether the reference appears in settlement data depends on the acquirer. See how each payment processor handles it.
Your system must keep track of which reference belongs to which business, including refunds.
In this model, one business collects money on behalf of others. Please check with the acquirer, and if needed a legal advisor, that this is allowed.
What does not work
Logging in with a different merchant's credentials for each payment.
Using Cloud API credentials that cover several merchants to get around this. They give your backend access to several merchants, but each payment still runs on a terminal that belongs to one merchant.
Unattended use
Softpay does not support unattended payments. Setups must be semi-attended, meaning a person needs to be present in the general area of the device.