Licensing
Saferpay offers quite a few licenses and packages, that each offer different functionality.
The (un-)availability of certain features can be imperative to the merchant, thusly, the decision about what feature-package to use, should be made pretty early during integration, so the integrator also knows, what tools he/she has to his/her disposal.
The following chapters will give an overview about the licenses and their available feature set.
These feature-sets and licenses are only applicable for the following countries:
- Germany
- Switzerland
- Lichtenstein
- Austria
Also note, that, even if you are inside these countries, you may still have an old contract. Please contact your contract-manager, or our sales-team for more information.
In any case, if you have any questions about Saferpay licensing and/or pricing, please contact your account-manager, or our sales-team.
Saferpay differentiates between four basic licenses, with the following available sets of features:
Features | QR Payment | Go | Easy | Flex |
---|---|---|---|---|
MOTO Terminal | ❌ | ✅ | ✅ | ✅ |
✅ | ✅ | ✅ | ✅ | |
E-Commerce Terminal | ❌ | ❌ | ✅ | ✅ |
Additional Terminals | ![]() | ![]() | ![]() | 10 |
Payment means activation | ✅ | ✅ | ✅ | ✅ |
Connectors/Acquirers | ✅ | ✅ | ✅ | ✅ |
Self-Service Payment means | ✅ | ✅ | ✅ | ✅ |
✅ | ✅ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
Payment Page | ✅ | ✅ | ✅ | ✅ |
Hosted Entry Form | ❌ | ❌ | ✅ | ✅ |
Hosted Register Form | ❌ | ❌ | ![]() | ✅ |
❌ | ❌ | ❌ | ✅ | |
❌ | ❌ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
❌ | ❌ | ✅ | ✅ | |
❌ | ❌ | ✅ | ✅ | |
❌ | ![]() | ![]() | ✅ | |
❌ | ❌ | ❌ | ✅ | |
❌ | ✅ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
❌ | ❌ | ❌ | ✅ | |
Documentation and Guides | ✅ | ✅ | ✅ | ✅ |
❌ | ❌ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ | |
✅ | ✅ | ✅ | ✅ |
⚠ - Upselling-option available. Please ask your contact at our sales.
In case you are using Saferpay, e.g. the Payment API, without the corresponding license, the API will throw an error:
{
"ResponseHeader": {
"SpecVersion": "1.10",
"RequestId": "[your request id]"
},
"Behavior": "ABORT",
"ErrorName": "PERMISSION_DENIED",
"ErrorMessage": "Permission denied",
"ErrorDetail": [
"Invalid license"
]
}
In this case, you'll have three options to proceed:
Option 1: You can contact your sales contact and ask for a change to the correct license, so you have access to the needed functions.
Option 2: If you are not happy with option 1, another option would be to redo your integration/use the available features.
If you are using an official plug-in/integration from our partners, it may only be a configuration issue, where you accedentially turned on a feature, that is not available to you.
Last modified 8d ago