About paysafecard

General information about paysafecard

Paysafecard is a prepaid card that consumers buy in shops in order to subsequently shop online. Since this is a prepaid means of payment, this system is free from chargebacks. In addition it offers merchants a payment guarantee.

Paysafecard is widespread in the gaming, gambling and adult content sectors. The previous Wallie-card has now been adopted into the paysafecard system. You can tap into additional target groups with this prepaid system:

• customers who do not want to disclose personal data such as bank account or credit card number
• young people who are denied access to classic payment systems such as credit cards
• customers who do not obtain a credit card from their bank
• as well as customers who prefer to pay with paysafecard

The prepaid system is international: the paysafecard Group operates in 27 countries in Europe as well as in North and Latin America and processes around 20 million prepaid payments annually.

Further information can be found on the webpage of paysafecard (www.paysafecard.com).

Connections to paysafecard

You can link paysafecard payment methods either directly or via PPRO. If via PPRO, all transactions are posted as sales without further posting. However cancellation and batch processing is not possible. In this case the additional PPRO parameters are required.

With direct connection via the 

Process flow chart

paysafecard process flow

Multiexcerpt include
SpaceWithExcerpt EN MultiExcerptName Platform-Kurz PageWithExcerpt Wording

 interface

Payment with paysafecard via form interface

To make a payment with paysafecard over a

Parameters for payments with paysafecard

Return parameters for URLSuccess, URLFailure and URLNotify with paysafecard

Capture of a payment with paysafecard

Captures are possible via a Server-to-Server connection. Captures are possible only if you have a direct connection to paysafecard and if this is configured for the merchant at

Parameters for captures of paysafecard via socket connections

Response parameters for captures of paysafecard via socket connections

Reversal

Reversals are possible via a Server-to-Server connection. Reversals are possible only if you have a direct connection to paysafecard and if this is configured for the merchant at

To carry out a reversal with a reference transaction, please use the following URL:

Parameters for reversal of payments with paysafecard via socket connection

Response parameters for reversals of paysafecard via socket connections

Batch processing via the interface

This section describes the parameters which must be transferred within the data set (Record) for executing of payments / reversal for paysafecard and which information can be found within the response file about the payment status. Batch processing is possible only if you have a direct connection to paysafecard and if this is configured for the merchant at

Following table gives an overview of all batch versions that are possible for a specific action and their specialities:

Description of the possible batch versions

The structure for a paysafecard payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>
Paysafecard,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
Paysafecard,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

HEAD,[Master]MerchantID,Date,2.x
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
FOOT,CountRecords,SumAmount

Description of fields within the record for Batch files

The record area within the response file for Batch transactions looks the following way:

HEAD,<MerchantID>,<Date>,<Version>
Paysafecard,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>, <Code>
Paysafecard,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>, <Code>
FOOT,<CountRecords>,<SumAmount>

Description of result parameters within the record for Batch files