Overview
A solution represents the payment configuration assigned to a store. Solution creation is handled entirely within the Hub.
Note: The Pricing policy section is only displayed for Acquiring & Acceptance and Acquiring Only companies. It is not shown for Acceptance Only merchants.
Access the Solution Creation Form
You can access the solution creation form in two ways:
- From the confirmation page displayed after completing store creation, click Add solutions.
- From the Submissions page, click Add solution at the top of the page, or click + Add solutions in the Solutions column next to the relevant store.
Fill In the Solution Details
Start by selection the Solution you'd like to add to the Store.
General Information
The exact list of fields depends on the selection Solution. Here's what you'll get for Payment Terminals solution.
| Field | Required | Notes |
|---|---|---|
| Solution type | Yes | e.g. Terminal, Payment Service |
| Service type | Yes | e.g. Integrated |
| Terminal serial numbers | Yes | Multiple values accepted |
| Merchant Category Code (MCC) | Yes | Pre-filled from the company's Activity Code where available |
| Processor | Conditional | Only displayed when the offer is Acceptance only. Search and select the merchant's bank from the list. Required when displayed. |
| Profile ID | No | |
| External store code | No | Optional identifier, max 20 characters |
Note: Terminals' serial numbers can be added one by one or in mass by pasting serial numbers separated by commas.
Optional Features
Some features can be enabled at the solution level. Their availability depends on the solution type.
| Feature | Payment Terminals | Online Payments | Tap to Pay | Notes |
|---|---|---|---|---|
| Enable Pre-Authorization | ✓ | — | — | |
| Enable Tips | ✓ | — | — | Payment Terminals only |
| Store and Forward | ✓ | — | — | Payment Terminals only |
| Enable DCC | ✓ | — | — | Pay Onsite & Paywish solutions only |
| EV Charging (Charge points A & B) | ✓ | — | — | Payment Terminals only |
| 3DS MID | — | ✓ | — | Only available when 3DS is enabled on the account |
| External TID + Activation Code | ✓ | — | — | Payment Terminals only |
| BAX ID | ✓ | — | — | NETS processor only; replaces Visa MID |
Payment Methods
The payment methods displayed in the form depend on the offer type, solution type, and country of the account. Select all methods that apply to the merchant.
Some payment methods require a Merchant ID (MID) to be entered manually. These are indicated in the tables below.
International Card Networks
| Payment method | Online Payments | Payment Terminals | Tap to Pay | MID required | Notes |
|---|---|---|---|---|---|
| Visa / Mastercard | ✓ | ✓ | ✓ | Acceptance Only only | Selected by default |
| American Express | ✓ | ✓ | ✓ | Yes (7–15 digits) | For Amex PayFac accounts, MID is optional |
| Maestro | ✓ | ✓ | ✓ | — | |
| JCB | ✓ | ✓ | — | — | |
| Union Pay | ✓ | ✓ | — | — | |
| Diners | ✓ | — | — | — | |
| Discover | ✓ | — | — | — |
Domestic Card Schemes
| Payment method | Online Payments | Payment Terminals | Tap to Pay | MID required | Country |
|---|---|---|---|---|---|
| CB | ✓ | ✓ | ✓ | — | France only |
| Bancontact | ✓ | ✓ | ✓ | — | |
| PagoBANCOMAT | — | ✓ | ✓ | — | Acquiring & Acceptance only |
| Dankort | — | ✓ | ✓ | Yes | Denmark only |
| Bankaxept | — | ✓ | ✓ | Yes (7 digits) | Norway only |
A2A & Bank Transfers
| Payment method | Online Payments | Payment Terminals | Tap to Pay | Notes |
|---|---|---|---|---|
| iDEAL | ✓ | — | — | Acquiring & Acceptance only |
| Bizum | ✓ | — | — | Acquiring & Acceptance only |
| Satispay | ✓ | — | — | Acquiring & Acceptance only |
| Payconiq | ✓ | — | — | Acquiring & Acceptance only |
| MyBank | ✓ | — | — | Acquiring & Acceptance only |
| BancomatPay | ✓ | — | — | Acquiring & Acceptance only |
| Blik | — | ✓ | — | Poland only |
| OP Online (A2A) | ✓ | — | — | Finland only |
Digital & Mobile Wallets
| Payment method | Online Payments | Payment Terminals | Tap to Pay | Notes |
|---|---|---|---|---|
| Apple Pay | ✓ | — | — | |
| Google Pay | ✓ | — | — | |
| PayPal | ✓ | — | — | |
| Alipay | ✓ | — | — | Acquiring & Acceptance only |
| WeChat Pay | ✓ | — | — | Acquiring & Acceptance only |
| Click to Pay | ✓ | — | — | |
| Venmo | ✓ | — | — | |
| Spenn | — | ✓ | — | REMA accounts only |
BNPL (Buy Now Pay Later)
| Payment method | Online Payments | Payment Terminals | Tap to Pay | Notes |
|---|---|---|---|---|
| Walley | ✓ | — | — | MID required |
| Floa | ✓ | — | — | |
| OP Lasku | ✓ | — | — | Finland only; MID required |
Vouchers & Gift Cards
| Payment method | Online Payments | Payment Terminals | Tap to Pay | Country | Notes |
|---|---|---|---|---|---|
| e-ANCV | ✓ | — | — | France only | MID required (8 digits) |
| Conecs | ✓ | ✓ | ✓ | France only | MID required (7 digits) |
| Sodexo | — | ✓ | — | Belgium, Luxembourg | MID required (8 digits) |
| Monizze | — | ✓ | — | Belgium, Luxembourg | MID required (10 digits) |
| Edenred | — | ✓ | — | Belgium, Luxembourg | MID required (13 digits) |
| Pluxee | — | ✓ | — | Italy only | MID required |
| Day | — | ✓ | — | Italy only | MID required |
| Valassis | — | ✓ | — | Italy only | MID required |
| Wincor | — | ✓ | — | Italy only | MID required |
| SIA | — | ✓ | — | Italy only | MID required |
| Amilon | — | ✓ | — | Italy only | MID required |
| Lunch GM | — | ✓ | — | Italy only | MID required |
| Pellegrini | — | ✓ | — | Italy only | MID required |
| Yes!Ticket | — | ✓ | — | Italy only | MID required |
| Toduba | — | ✓ | — | Italy only | MID required |
| BluBe | — | ✓ | — | Italy only | MID required |
| Repas | — | ✓ | — | Italy only | MID required |
| PASS (ES) | ✓ | ✓ | — | Spain only | MID required |
| PASS (FR) | ✓ | ✓ | — | France only | MID required |
| KGift | ✓ | ✓ | — | — | Kesko accounts only; MID required |
| Plussa Money | ✓ | ✓ | — | — | Kesko accounts only |
Pricing Policy
The Pricing policy section is only displayed for Acquiring & Acceptance and Acquiring Only companies.
You can configure either a single default pricing policy that applies to all card brands, or multiple pricing policies each applying to one or several specific brands. Thresholds can also be added to apply different rates depending on transaction volume or amount.
Step 1 — Set up thresholds (optional)
Click Add thresholds to define volume-based pricing tiers. In the threshold setup dialog, select the threshold type and define the ranges:
| Field | Description |
|---|---|
| Type | Amount (total transaction value in €), Volume (number of transactions), or Unit Amount (individual transaction value in €) |
| Threshold 1 | Define the upper limit of the first pricing tier (lower limit is always €0) |
| Threshold 2 | Automatically starts where Threshold 1 ends; upper limit defaults to infinity |
Click + Add more thresholds to add additional tiers, then click Add thresholds to confirm.
If no thresholds are needed, skip this step and proceed directly to configuring Pricing policy 1.
Step 2 — Configure pricing policies
Click "Pricing policy 1 to expand the configuration panel.
The policy grid displays rates organised by card type (Credit / Debit), card origin (National / EU / Extra EU), and card holder type (Business / Consumer). Click the edit icon in any cell to set the rates for that combination.
For each cell, a Pricing setup dialog opens with the following fields:
| Field | Description |
|---|---|
| Import rates from | Optional. Copy rates from an existing configuration to avoid re-entering values manually. |
| Method | Select Blended (a single combined rate) or IC++. |
| Rate (in %) | The percentage fee applied to the transaction amount. |
| Fixed fees (in €) | A flat fee applied per transaction. |
| Processing fees (in €) | Additional per-transaction processing cost. |
| Duplicate these rates to | Optional. Apply the same rates to one or more other card type/origin combinations in one action. |
Click Save to confirm the rates for that cell.
Step 3 — Assign the pricing policy perimeter
Once rates are configured, scroll down to the Pricing policy perimeter section. Select the card brands this policy applies to. Available brands include: Visa, Mastercard, Maestro, V Pay, Bancomat, Bancontact, and others depending on the payment methods selected earlier.
Click Apply to save the policy perimeter.
Repeat Steps 2 and 3 to add additional pricing policies if needed.
Signing responsible(s)
Depending on your account setup, a Signing responsible section may appear within the Pricing policy step. If it does, enter the first name, last name, email, and role (Signer or Viewer) of each person who needs to sign the contract — up to 5. Submitting this step will trigger the contract to be generated and sent automatically.
If you don't see this section, your account uses a different contract process — see Managing Merchant Contracts for what to do instead.
Submitting each step
Solution creation happens in sequential steps — General information, Payment methods, and Pricing policy (when applicable) — each submitted on its own as you go, rather than reviewed together at the end.
Click Submit at the bottom of each step to save it and move to the next one. If a step fails, you'll stay on that step with your entries intact so you can fix and resubmit.
Note: For Acceptance Only companies, there's no Pricing policy step, so you'll only see two steps.
Once the last step is submitted, the solution appears as Completed in the Submissions page. When all three onboarding steps show Completed, the merchant is fully active and ready to accept payments.