One of the steps in the integration checklist is to set up your test standalone terminals. This involves making your test terminals ready for standalone use, optionally configuring tipping, and optionally configuring a refund passcode. There are two ways to do these tasks:
- From your Customer Area
- Using API calls
Requirements
Before you begin, take into account the following requirements and preparations.
| Requirement | Description |
|---|---|
| Integration type | Standalone . |
| API credentials | To set up your terminal using API calls, you must have an API credential with an API key and the following roles:
If in addition to a standalone solution, you also have a Terminal API integration with cloud-based communications, you can use the existing API key that you use for Terminal API requests. |
| Customer Area roles | To set up your terminal from the Customer Area, you need the following roles:
|
| Limitations | Note the following:
|
| Hardware | A standalone payment terminal. |
| Setup steps | When going live, you need to set up your live standalone terminals in the same way as you did for your test terminals. |
When new settings take effect
When you use the Customer Area or API calls to configure settings that turn a terminal into a standalone terminal or that enable a feature, take into account that these settings do not take effect immediately.
The terminal downloads configuration changes when it makes a maintenance call to our systems. This happens automatically every 180 minutes. The configuration changes then take effect when the terminal reboots. This happens automatically at the restart hour, which is usually set to 6:00 AM.
To switch to new settings immediately, manually start a configuration update:
-
On the terminal, go to Settings > Configuration, enter your Admin & Settings passcode and select Update.
-
On a non-Android terminal that uses the old menu structure: go to the Admin menu and select Config > Update.
The terminal downloads the updated configuration and then restarts.
Set up standalone
Using your Customer Area or the Management API, you can set up the standalone feature for all terminals under your company account, merchant account, or store. You can also set up standalone use for individual terminals, for example if you need to use standalone as a fallback on specific terminals at your store.
Configure tipping
To ask for a tip, you can let the payment terminal show a prompt to enter a tip plus an option for not giving a tip. To give a tip, the customer enters the amount and confirms.
If you want to make tipping easier for your customers, you can let the terminal show predefined tipping options that the customer can select. The options can be any combination of percentages, calculated amounts, and a custom amount. You can configure the option buttons to show only the percentage, only the calculated tip amount, or the percentage and the amount together.
Tipping without options:  |
Tipping with percentage options:  |
Percentage and calculated tip amounts:  |
You can configure tipping using your Customer Area or the Management API.
Configure compliant tipping in Quebec, Canada
A regulation in Quebec, Canada requires tips to be calculated on pre-tax amounts. To facilitate compliance with this regulation, we recommend choosing one of the following tipping options:
- The terminal asks the shopper to enter the tip manually.
- The terminal shows predefined tipping options for specific CAD amounts and the option to enter a custom tip amount.
To configure tipping option to facilitate compliance with regulations in Quebec, Canada:
- Decide what method you want to use: let the shopper enter a tip, or show predefined fixed amounts.
- Set up tipping in the same way as described under configure tipping, but:
- At Enable standalone tipping, turn on the toggle.
- Select Save.
Configure a refund passcode
Because making refunds on standalone payment terminals is risky, you can enable a 6-digit passcode needed to initiate refunds. You set up the Refunds passcode in addition to the Transactions passcode, which means that you need to enter both to initiate a refund.
You can configure this in your Customer Area or using an API call.
Payment facilitators
If you are a payment facilitator, card schemes require you to provide certain data about your sub-merchant with each transaction. That is because your sub-merchant is considered the Merchant of Record when you facilitate a transaction.
Adyen automatically adds certain sub-merchant data to transactions that you facilitate. To supply the remaining data, you must add that data to the configuration of the sub-merchant's store.
Testing
For information on how you can make test payments and refunds, see testing your integration.
Any test transactions you make, will appear in your Customer Area, under Payments > Payment list.