Do you have questions about PaysafeCard?

PaysafeCard, part of Paysafe, is one of the global market leaders in online prepaid payment solutions. It enables anyone to pay online, as simple and safe as using cash. PaysafeCard is the perfect online payment solution for customers who value their data security, wish to limit their spending or simply don't have a bank account or credit card.

PaysafeCard is available in more than 50 countries at more than 650.000 points of sale and can be used at thousands of online shops.

Discover more about the business opportunities available to you by contacting us via the contact form.

Please complete our online form. Upon submitting the form, you will be logged in to the PaysafeCard Service Center, where you can immediately begin integrating PaysafeCard as a payment method in your online shop. As a regulated payment service provider, we are required to collect details about your company, its ownership and power of representation. You can upload the required documents via the Service Center.

The Scale-based Standard model: The very transparent sliding scale is based on a monthly transaction volume price model. The model starts from 15% for low transaction volumes down to 9.5 % for merchants with more than 350.000 € transaction volume. Different pricing may apply for selected industries and Payment Services Providers (PSPs).

PaysafeCard does not charge merchants any setup fees, monthly subscription or any other hidden fees.

If you have any special pricing requests or any other question to our standard pricing models, our PaysafeCard sales team is happy to answer any questions. Contact us here.

Payments are usually transferred once a month with a due date of payment of 14 days or twice a month with a due date of payment of 21 days.

Our demo application allows you to easily complete a payment transaction with PaysafeCard online for testing purposes. This enables you to quickly try out the range of configurations on offer and find the best choice for your online shop. The only requirement for using the PaysafeCard demo application is a PaysafeCard prepaid code. This is available from any of our 650.000 sales outlets.

Once you have one, simply select any of the test configurations available in the PaysafeCard demo application. This allows you to experience firsthand how paying with PaysafeCard works and how the transaction process appears.

24-pay s.r.o.
abilipay GmbH
AccentPay Limited (integrator)
ACI Worldwide (Germany) GmbH
Adyen N.V.
Altruja GmbH
APCO Systems Limited
BD Multimedia SA
BetConstruct
Betware.com
BIG FISH Payment Services Kft.
BITkurier GmbH
C.V. Smart2Pay Global Services U.A.
Cardinal Commerce
CASHBILL SPOLKA AKCYJNA
CASHDASH UK LIMITED
Centrobill Limited
CM.COM N.V.
Coda Payments Pte. Ltd.
Compay GmbH
Computop Paygate GmbH
Comtrade programske resitve d.o.o.
Corvus Pay d.o.o.
CURO Payments B.V.
CYBERservices S.A.
DaoPay GmbH
datatrans Swiss Payment Competence
DEGICA Co. Ltd.
Deutsche Telekom AG
DevCode Payment AB
DialCom24 Sp. z o.o.
Diebold Nixdorf Deutschland GmbH
Digiprocessing Limited
Digitalpayment GmbH
DIMOCO Payment Services GmbH
Dotpay sp. z o.o.
ecardon payments GmbH
eMerchantPay Limited
EPG Financial Services Ltd.
EPG SUPPORT ESPANA SL
ePlatnosci sp. z o.o. sp. k.
euPago - Instituicao de Pagamento LDA
Euro Payment Group GmbH
finnplay.com
Gamanza Group AG
Gate2Payments ApS
GenerationWeb PTY LTD
Global Collect Services B.V.
GOPAY s.r.o.
HIPAY SAS
HydroPay B.V.
Icepay B.V.
Iforium Limited
inopla GmbH
Ipay See d.o.o.
Iruvey Corporation S.A.
Ixopay LLC
Limonetik
LogiQpay
Lyra Network SAS
MatrixPayment.AG
Maxpay Limited
Maxx-XS BV
Mercadonet
Metatheke - Software Ld.ª
METEOR Zahlungssysteme GmbH
Micropayment AG
Micropayment GmbH
Mistral Pay Ltd
Mobile Business Engine GmbH
MOBIYO SASU
ModusLink B.V.
Mollie B.V.
Monext SAS
MoneyMatrix Limited
MultiSafepay B.V.
mvneco GmbH
Myriad Payments Limited
Noire Technology Ltd.
NYX Interactive
optile GmbH
Oryx razvojne storitve d.o.o.
Paybox Services SAS
PayCific International AG
Paymenterio Spolka z ograniczona odpowiedzialnoscia
Paymentwall Inc.
Paymentworld Europe Ltd.
Payrexx AG
Payvision B.V.
Pil - Professionelle Internet Losninger ApS
Playtech Sofware Limited
PPRO Payment Services S.A.
PrimeiroPay S.a.r.l.
Processing Partners Inc.
Processing.NET Limited
produweb-gaming
PXP Financial Limited
Rootpay Sp. z o.o.
RPDP Robert Paszkowski
Safecharge Limited
SBTech
Schlund und Partner
ShopRenter.hu Kft.
SIA eComCharge Ltd.
Skrill Inc.
Skrill Ltd
SOCIETE FINANCIERE DU PORTE MONNAIE ELECTRONIQUE INTERBANCAIRE
SPRL INGENICO E-COMMERCE SOLUTIONS
START 2 PAY LIMITED
Suraway Ltd.
SweePay AG
SWITCH PAYMENTS RPRA LDA
Syspay Limited
Tamnet Services Inc.
TargetMedia B.V.
Tebex Limited
Tecnalis Solution Providers S.L.
TelePay S.L.
TICKETMASTER HELLAS SA
TinTel B.V.
Total Processing Ltd.
Tradologic
Trust Pay a.s.
Trust Payments (Malta) Limited
UAB "ZEN Global"
UAB Glocash Payment
Unas Online Kft.
Unzer Austria GmbH
Viveum Zahlungssysteme GmbH
WB Technical Services B.V.
WorldPay AP Ltd
Worldpay B.V.
Xsolla (USA) Inc.

The Customer ID/MerchantClientID(MCID) is a parameter that identifies your end customer. Transactions made by the same customer must have the same MCID. This parameter must not contain any personal information. In case of using personal information (i.e. email address) as a MCID you will have to encrypt it.

The most optimal MCID is a completely random value. A value that uniquely identifies the customer and is disconnected from any personal information. The MCID value has to be the same for all transactions of the customer.

If the MCID is not implemented correctly transactions may be blocked due to regulatory issues, impacting the customer experience.

For more details on the MCID you may refer to the following section of the respective API documentation:

REST: https://www.paysafecard.com/fileadmin/api/#/reference/importance-of-the-customer-id-parameter

SOPG: https://www.paysafecard.com/fileadmin/api/paysafecardsopg.html#/reference/importance-of-the-merchantclientid-parameter

The MID is a parameter that identifies you and the currency you are using in the transaction. It is number of 10 digits. You can find it in the MSC.

If you are interested to become an official PaysafeCard point of sale, please contact either one of our distribution partners, who can help you with the technical requirements, or just contact us directly.

The most frequent error codes are:

 

2001 | Transaction already exists

Make sure that the correlationId is a unique value per transaction.

3014 | Reporting criteria unavailable

Make sure that you are using a subId previously agreed with PaysafeCard.

3034 | Reporting criteria is inactive

Make sure that you are using a subId previously agreed with PaysafeCard.

3001 | MID is inactive

If the onboarding process is not finished yet, this is completely normal as your account remains inactive until the last integration tests are successful. If your account is live contact our technical support.

2029 | Amount must be greater than 0

Make sure that the transaction amount is greater than 0.

4003 | The amount exceeds the maximum permitted amount

Make sure that the amount of the transaction is not exceeding the maximum permitted (EUR 1,000 or equivalent in other currency).

3002 , 10014 | Currency invalid

The currency you are using is not activated for your account. Please contact your account manager.

2017 | Transaction in a wrong status for this action

Check the status of the transaction with retrieve Payment details and perform an action according to its result (please see the payment workflow).

3007 | Debit attempt after expiry of time window

The transaction was not closed within the disposition time window (between 1 and 10 minutes, defined by our Terms & Conditions) so it expired. The amount is returned to the customer’s PaysafeCard voucher or account.

2002 | Transaction doesn't exist

Make sure that the paymentId is a correct one.

10008 | Authentication failed

Make sure that you are using the correct API Key and endpoint. You can generate new API Keys in the MSC.

10007 | General technical error

Contact PaysafeCard immediately via integration@paysafecard.com if the account is not live. For live accounts, techsupport@paysafecard.com should be contacted.

3162 | my PaysafeCard account not found by provided credentials

Make sure the e-mail address entered in the payout request corresponds to the e-mail address registered in the my PaysafeCard account.

3195 | Customer account details do not match

Make sure that the name, family name and date of birth entered in the payout request match with the ones in the my PaysafeCard account.

Yes, if this is related to a certificate issued by a recognized certification authority, such as Thawte or Verisign.

For security reasons, our production system permits access to whitelisted IP addresses only. For this reason, we request that you provide all IP addresses which you wish to use to access our production system during the step “IP Whitelisting”.

In order to be able to access our system, you require access details. These are known as the API key. You can find your API Key in the MSC.

These access details serve a verification purpose on our REST API and must be entered in your system as a required step in the technical implementation of PaysafeCard.

Please note that you are obliged to keep this key confidential and to protect it from third parties. PaysafeCard assumes no liability for damages arising from the misuse of these access details.

Once the REST-API has been integrated in your test system, you will be requested to test its implementation. The MSC will supply you with a series of test cases which serve to ensure that the full range of functions of the PaysafeCard payments application is working.

These detailed test cases are to be completed in real time in the order specified by the MSC. The test results are then verified by the PaysafeCard test system. Directly afterwards you will receive a test report summarizing all the details of the test case and providing you with information on any adjustments which may need to be made.

The acceptance test is done to ensure that payments with PaysafeCard are working as expected. This test is performed manually by our staff. Apart from checking that payments with PaysafeCard follow the payment workflow (https://www.paysafecard.com/fileadmin/api/#/reference/payment-process) we also check that success/error messages are shown properly to the customer and verify the use of PaysafeCard logos.

The feature test is only carried out if you implemented Payout or Refund. Its purpose is to check that these services have been implemented correctly.

After completing the automated integration tests in the MSC you can request the feature test. This test is performed manually by our staff, to perform the test we will need access to your test environment.

In order to switch to the production environment, you will have to enter the production API key and change the endpoints to production. In the MSC you can find and create new API keys and will also find the endpoints.

Please notice that before you can see this production data you will have to complete the automated integration tests in the MSC (except if you are using a verified plugin or payment gateway), also the contract must be signed and some internal business steps must be completed in our side.

Sample codes for the PaysafeCard REST API are available from the download area on our website.

The MSC is a tool that guides you step by step during the integration of PaysafeCard into your online shop. Once you are live you can check the status of your transactions there.

Upon submitting the online form you will be logged in to the Service Center.

During the onboarding of PaysafeCard you can use the MSC to:

• Select how you wish to integrate PaysafeCard
• Upload the required documents
• Sign the partner contract
• Complete the technical integration of PaysafeCard
• Contact our support
   

Once integration is completed, the MSC will remain available for you to:

• Manage IP addresses
• Download reports
• Check the status of your transactions
• Contact our support/contact information in case of emergencies
   

If you are a Payment Gateway, you will only be able to use the Service Center for the technical integration of PaysafeCard.

You can integrate PaysafeCard directly or indirectly using a plugin, a payment gateway or a collecting/full service PSP.

Direct technical integration

• You enter into a contract directly with PaysafeCard
• Integration tests via the MSC
• Sample code available online from the download area
• Direct support from PaysafeCard
• Notifications directly from PaysafeCard

 

Indirect technical integration

• PSP –Payment Gateway
  • You enter into a contract directly with PaysafeCard
  • Technical integration completed by a PaysafeCard verified Payment Gateway
  • No technical work needs to be carried out by you.
  • Simplified integration tests - Direct support from PaysafeCard
  • Notifications directly from PaysafeCard
• PSP – Collecting/Full-Service PSP
  • Contract not with PaysafeCard but with the collecting/Full-service PSP
  • Transactions and billing also completed by the collecting/Full-service PSP
  • No technical work needs to be carried out by you
• Shop systems - verified PaysafeCard plugins
  • You enter into a contract directly with PaysafeCard
  • Less technical work needs to be carried out by you (only to set the shop system)
  • Simplified integration tests
  • Support from the shop system operator and PaysafeCard together
  • Notifications directly from PaysafeCard

It is the time you have to call “Capture Payment” after the customer authorizes the transaction.

The "Disposition Time Window" is a contract-defined period of time. The standard length is 10 minutes. Once a customer PIN or my PaysafeCard has been allocated, a transaction must be completed with an "Capture Payment" call within this period of time or the reserved amount on the customer PIN or my PaysafeCard will be released and returned to the customer.

Only if "Capture Payment" is successful the amount of the transaction is debited from the customer.

If “Capture Payment” is not called or not successful the amount of the transaction will be returned to the customer’s PaysafeCard voucher or account after the disposition time window.

The first “Capture Payment” will be successful, the following ones will fail with error code 2017.

Once the “Capture Payment” request is completed, the transaction status updates to “SUCCESS”, meaning that it has been successfully completed. If another “Capture Payment” request is made for the same transaction, the response [http400 and Error Code = 2017] is returned. In order to avoid this the status of the transaction must always be checked with “Retrieve Payment Details” and only call “Capture Payment” if the status is “AUTHORIZED”.

The customer has 30 minutes to authorize the payment.

Once a payment transaction has been created (Initiate Payment), the customer has 30 minutes to enter a PIN in the payment panel or to log in to his or her my PaysafeCard. Once 30 minutes have passed without a PIN or my PaysafeCard log-in details having been successfully entered, the transaction status will update from “REDIRECTED” to “EXPIRED”. Transactions with the status “EXPIRED” are unsuccessful and the customer must create a new payment transaction.

This refers to the PaysafeCard payment panel. After starting a transaction, you must redirect the customer to the payment panel so that she/he can enter a PaysafeCard PIN or her/his my PaysafeCard user information to authorize the transaction.

PaysafeCard transactions may have 7 different statuses

• INITIATED:
  The initial status of a transaction once it has been created.
• REDIRECTED:
  The customer has been successfully forwarded to the PaysafeCard payment panel to authorize the payment.
• AUTHORIZED:
  The customer successfully entered a PIN at the payment panel and clicked on pay.
• SUCCESS:
  The transaction has been successfully completed.
• CANCELLED_MERCHANT:
  You, as the contract partner, have cancelled the payment.
• CANCELLED_CUSTOMER:
  The customer has actively cancelled the payment in the payment panel.
• EXPIRED:
  The customer did not authorize the transaction within the necessary time period or you, as the contract partner, did not complete the payment with within the necessary time period.

The PaysafeCard payment application is based on a REST API. REST, Representational State Transfer, is an architectural style of the World Wide Web. REST uses the standard HTTP methods (GET, POST, PUT, DELETE, etc.).

During the technical integration of PaysafeCard as a payment method you are guided by our MSC through the following steps:

• Choose your integration type
  Choose if you are going to integrate PaysafeCard directly or indirectly through a plugin or a payment gateway.
• API key/MRT access details for the test system
  PaysafeCard provides you with the REST API keys for testing our REST API and Merchant Reporting Tool (MRT, only available for test system to check the status of your transactions). If you are integrating with a plugin or with a Payment Gateway this step will be skipped.
• Integration test
  A series of test cases are supplied in our MSC. These must be completed in the specified order in real time and checked against our system. If you are integrating with a plugin or with a Payment Gateway this step will be skipped. If you also implement one of our services, "Payout" or "Refund", once the integration test has been successfully completed, this feature is tested by our staff.
• IP whitelisting for the production system
  After successfully completing the integration test, we request your IP addresses for the production system, which must be authorized in our internal system.
• API key for the production system
  Once IP whitelisting has been completed, PaysafeCard will provide you with access details for the PaysafeCard production system. We then ask you to integrate PaysafeCard into your production system by entering the REST access details in your system.
• Acceptance test
  Once this step is completed by you, our staff will carry out a final test transaction and check that the PaysafeCard logos and copy text are up to date and meet our quality requirements.
• Go Live
  Once the acceptance test has been successfully completed by our staff, PaysafeCard will be authorized for use as a payment method for your online shop and you can start processing payments with PaysafeCard.

A transaction cannot be successfully completed without calling "Capture Payment". The transaction amount reserved on the customer PIN or my PaysafeCard will be released. In such a case after the disposition time window is completed, the transaction fails.

Our MSC will guide you through the necessary steps:

 

REST-API key/MRT access data for the test system

You will receive your REST-API key from us, with which you can start the integration of PaysafeCard in your test environment. In this step, you will also receive the registration data for the Merchant Reporting Tool (MRT), with which you can check the status of your transactions.

Integration test

After you have completed the integration of PaysafeCard, you need to test it in the MSC. You will find a set of test cases there which are carried out and checked in real time in the prescribed sequence.

Acceptance test

Please give our MSC your test registration data as soon as the integration test has been successfully concluded. Our team will then carry out the final tests. These include a check on the PaysafeCard logo and the associated text to ensure they are up to date and of sufficient quality. As soon as the tests have been successfully completed, your company will become an official PaysafeCard payment gateway.

In this case, you also administer the invoices for your customers. In order to be able to separate the business of your contractual partner for the purpose of invoicing correctly, you also need to integrate the so-called reporting criteria. These are assigned to each of your contract partners and serve to identify individual transactions.

In this case, the integration partner to whom you make the request will carry out the technical integration. Our MSC also guarantees when working with integration partners a verified and high-quality implementation of PaysafeCard as a method of payment.