Paysafecard

Overview - Paysafecard

paysafecard, part of the Paysafe Group, is one of the global market leaders in online prepaid payment solutions. It provides its customers with a way to pay online, as safe as using cash.

Available in 49 countries at more than +650,000 points of sale it can be used at thousands of online shops.

The paysafecard is a prepaid card with 16-digit PIN and is the perfect online payment solution for customers who don't have a bank account or credit cards or just wish to limit their spending.

Customer Experience - Paysafecard

Step	Description	Image
1	Choose paysafecard
2	Click Pay
3	Redirect to my paysafecard
4	Proceed on the paysafecard page and enter the 16-digit code

PayEngine Details - Paysafecard

General

Name	Details
Product	paysafecard
Channels	ECOM
Currencies	AUD, CAD, CHF, EUR, GBP, NOK, PLN, RON, SEK, USD
Countries	AT, AU, BE, BG, CA, CH, CY, CZ, DE, DK, ES, FI, FR, GB, GE, GI, HR, HU, IE, IT, LI, LT, LU, MT, MX, NL, NO, NZ, PE, PL, PT, RO, SE, SI, SK, UY
Technical Flow	Asynchronous
Recurring	No
Chargebacks	No
B2B applicable	No

Supported Features and Services

Name	Details
Debit	Yes
Preauthorization	No
Cancelation	No
Capture	No
Refunds	No
Notifications	Yes (webhook and email)
Settlement Reporting	Yes - Unified Settlement Reporting

Integration Types

Name	Details
API	Yes
Widget	Yes
Bridge	No
Shop Plugin	No
Paylink	No

Integration via API - Paysafecard

Technical Flow

Webhook and email notifications

At the time of the redirect, it is still uncertain whether a transaction will be completed successfully or not. Therefore, Payengine awaits for the final asynchronous notification before the status of a DEBIT transaction is changed from PENDING to SUCCESS or FAILURE.

A merchant should register for Payengine's notifications to receive this final status update.

Alternatively, a GET request on the order or DEBIT transaction would also work, but it is not ensured that the final status will be available immediately after the redirect and a merchant might have to query the GET multiple times.

Therefore, it is strongly recommended that Payengine's asynchronous notifications are used instead.

Merchants could receive notifications via URL (webhook) or email.

The notifications could be subscribed:

via the payengine API (link to API documentation)
via the Payengine Merchant Center (link to Merchant Center notifications documentation)

Specifications - Paysafecard

Input Parameters for Authorizing Transactions

Parameter	Mandatory/Optional (M/O)	Description	Type	Example
async.cancelUrl	M	Redirect URL when payment is canceled	string	http://my.shop.com/cancel
async.failureUrl	M	Redirect URL for unsuccessful payment	string	http://my.shop.com/fail
async.successUrl	M	Redirect URL for successful payment	string	http://my.shop.com/success
payment.countryCode	M	Country code	string	DE
customer	M	Customer ID	string	Customer-21a8e31a-c477-4ce7-91b6-b2787c8fd0de
currency	M	The currency of the transaction Accepted values: AUD, CAD, CHF, EUR, GBP, NOK, PLN, RON, SEK, USD	string	EUR
payment.accountHolder	O	The paysafecard accountholder name	string	Dr. Hans-Peter Meier

Samples

Debit transaction

POST/{{publicApiUrl}}/v1/orders/debit

Create Debit Request

{
    "product": "paysafecard",
    "terms": 1468590412476,
    "privacy": 1468590412476,

Create Debit Response

{
    "createdAt": 1585834500589,
    "modifiedAt": 1585834500669,
    "merchantId": "Merchant-11111111-1111-1111-1111-111111111111",

Testing

paysafecard can be tested via the Payengine Simulator.

The testing amounts for the two scenarios can be found below:

Result	Description
Success	Any applicable amount (excluding failure amounts listed below). The transaction's status changes from OK to SUCCESS.
Failure	Each of the amounts listed below: 11111 (€111,11) 111 (€1,11) The transaction's status changes from "OK" to "FAILURE".