Accepting paysafecard as a merchant

paysafecard is a prepaid voucher: the customer buys a code with cash at a retail outlet and redeems it online. It serves people without cards or bank accounts, people who do not want to enter card details, and, importantly for the merchant, people who want a hard spending limit.

Reach

The commercial case is reach, not price

Prepaid voucher acceptance typically prices above card acceptance. You are not buying cheap processing; you are buying access to a customer who could not otherwise complete the purchase. That makes it a reach decision, and reach decisions should be judged on incremental orders rather than on total conversion, exactly as with deferred payment methods.

Prefunded means no chargebacks, and no recourse either

The value is already loaded, so there is no card-style chargeback and no failed collection. For merchants in categories with high dispute rates that is a genuine advantage. The other side is that refunds are outbound and the customer relationship is thinner: an anonymous or semi-anonymous payer is harder to support, harder to verify and harder to re-market to.

Category and regulatory sensitivity

Prepaid vouchers are concentrated in gaming, digital goods and online services, categories that attract regulatory attention and stricter provider risk appetite. If your business sits in or near those categories, availability and terms will vary between providers far more than they do for cards, and the terms you are offered say as much about your risk classification as about the method.

Identity

A thin customer relationship has downstream costs

The section above notes that an anonymous or semi-anonymous payer is harder to support, verify and re-market to. Each of those has a concrete cost, and the third is the one nobody counts.

Support. A customer who cannot be identified from the payment cannot be found in your order system the usual way, so your support process needs a different lookup, agreed in advance. Without one, every routine query about a voucher order becomes an escalation, and escalations are the most expensive minutes in a support operation. Refunds. An outbound refund to a prepaid instrument needs a route, and the route is not always the one the money arrived on, so the refund policy for this method has to be written for this method rather than inherited from cards, including what happens when the original instrument no longer exists.

Analytics. A payment carrying no reusable customer identifier breaks the link between an order and a customer record. Repeat purchase on this method is therefore systematically understated in your own reporting, and a segment that is genuinely loyal can look like a stream of strangers. If you are judging the method on customer value, you are judging it on a number your own system is suppressing.

Which payment provider supports paysafecard?

Computop, Datatrans, Nexi and Mollie all document paysafecard, along with many other European gateways. The useful questions are the fee as a percentage of order value against your card rate, what share of paysafecard orders would have converted on another method, and how refunds are handled operationally.

Classification

The fee is not the only price

Start with the visible half. Take 3 million euros of revenue with paysafecard carrying 4 per cent, so 120,000 euros. At an illustrative 4.5 per cent against a card at 1.4 per cent, that is 5,400 euros against 1,680, so 3,720 euros of extra fee. At a 40 per cent gross margin, 3,720 euros of fee is paid for by 9,300 euros of revenue that would not otherwise have existed. So the break-even is that at least 7.75 per cent of your paysafecard volume has to be genuinely incremental. Below that, the customers who would have paid another way are subsidising the ones who could not.

Now the half that never appears on the method’s own line. The section above says the terms you are offered say as much about your risk classification as about the method. That works in both directions, and it is worth testing rather than assuming. Ask your provider what your card rate, your settlement delay and your reserve requirement would look like without this part of your business in the mix. If nothing moves, the method costs what its own line says. If something moves, it is carrying a cost spread across everything else you accept, and the break-even above is optimistic.

Neither question is confrontational and both are answerable in a sentence. The reason to ask them together is that a method judged only on its own rate is being judged on the smaller of the two numbers.

Reviewing what this costs you

What you pay is set in your agreement, not by the scheme. Start by establishing whether you are overpaying your PSP, or look at how a structured payment RFP settles market coverage before you sign rather than after.

Relevant markets: Europe, global