Saferpay Documentation
English
Ask or search…
K

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
If you are in any other country, please refer to the legacy licensing!
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.

Licenses and featuresets

Saferpay differentiates between four basic licenses, with the following available sets of features:
Features
QR Payment
Go
GoCard ePayments
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
3D Secure
Documentation and Guides
Support
⚠ - Upselling-option available. Please ask your contact at our sales.

What happens, if you do not have the right license?

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.

Query the License via API

Saferpay also offers the possibility to query your license-configuration via API. This may be useful, if you intend on offering your implementation to multiple users, or for marketplaces. It enables you to automatically configure the available features, without the merchant having to do this manually.

Example

This an example, of how a response may look like:
{
"Package": {
"Id": "SAFERPAY_FLEX",
"DisplayName": "Saferpay Flex"
},
"Features": [
{
"Id": "BATCH_PROCESSING",
"DisplayName": "Batch Processing"
},
{
"Id": "HOSTED_ENTRY_FORM",
"DisplayName": "Hosted Entry Form"
},
{
"Id": "HOSTED_REGISTER_FORM",
"DisplayName": "Hosted Register Form"
},
{
"Id": "OMNICHANNEL",
"DisplayName": "Omnichannel"
},
{
"Id": "SAFERPAY_FIELDS",
"DisplayName": "Saferpay Fields"
},
{
"Id": "SECURE_CARD_DATA",
"DisplayName": "Secure Card Data"
},
{
"Id": "PAYMENT_API",
"DisplayName": "Payment API"
},
{
"Id": "MANAGEMENT_API",
"DisplayName": "Management API"
},
{
"Id": "SECURE_PAY_GATE_SINGLE_USE_PAYMENT_LINKS",
"DisplayName": "Secure PayGate Single-Use Payment Links"
},
{
"Id": "SECURE_PAY_GATE_MULTI_USE_PAYMENT_LINKS",
"DisplayName": "Secure PayGate Multi-Use Payment Links"
}
]
}