SafeCharge has announced a new set of features to support UK operators facing the upcoming credit card ban.

The UK Gambling Commission (UKGC) recently announced a ban on the use of credit cards for gambling activities within the UK. The ban, which comes into effect on April 14, 2020, will mean that all gambling merchants will have to make changes to both their online and offline payments to ensure they do not fall foul of the new legislation.

In response, SafeCharge, a Nuvei company, has announced features to ensure its igaming clients remain compliant while retaining high conversions.

How will SafeCharge help block UK credit cards?

The company has announced it has developed a solution that blocks attempted credit card transactions on all levels. By implementing this solution, operators will be able to block credit card transactions by user country, transaction type (for example, deposit or withdrawal), credit card solution (Apple Pay, for example) and card issuer country. These blocking solutions will apply across all of SafeCharge’s integration types, including the Hosted payment page (Cashier), REST API, Gateway and Risk level.

How will the solution work?

Those within the igaming industry will be keen to understand exactly how these parameters can be set within their websites. Below is a breakdown of how the solution will work across each product.

Hosted payment page (Cashier): SafeCharge’s Cashier will prevent credit card deposits by returning an error message as soon as a customer attempts to enter credit information. The error message will read: “Credit cards are not allowed on this site. Please use a different card type.” Thus, preventing credit card use yet still providing players with the option to use another method, thus not losing the deposit.

REST API: For those merchants using SafeCharge’s REST API, the following prevention techniques will be put in place: those using the “cardTokenization” API method will be able to asses each attempted payment for its card type by evaluating each “cardTokenization” response which will also provide issuing bank information; those using card registration via “Authorisation Zero” will gain responses with card type and issuing bank information; for existing cards, the “getusersUPOs” API method will also provide the same details for existing cards on file.

Gateway: The SafeCharge Gateway will block credit cards before processing a transaction by performing a check. Once merchants have set up rules pertaining to the UK jurisdiction, these transactions will be blocked.

Risk level: For merchants making use of SafeCharge’s Risk level software, they can set up risk filters based on the general blocking parameters laid out above, with the addition of being able to set up a filter on existing credit cards. The control is in the hands of the operator.

Protection from workarounds: In the case of Apple Pay, merchants can use the Apple Pay API to set up blocks on that side of the transaction through the “merchantCapabilites” field. SafeCharge’s Cashier and Gateway products will block credit card payments attempted through Apple Pay once configured on the merchant side.

SafeCharge is working closely with eWallet providers such as PayPal, Neteller and Skrill, who have all confirmed that they will provide solutions from their side. Finally, new cards issued will not penetrate SafeCharge systems as their BIN list is updated daily, meaning their system will recognise even brand-new cards.

How far does the new legislation extend?

It’s useful to remember that this new regulation only applies to cardholders residing in the UK, or to cards issued by UK banks. This does not apply to players based overseas, or with credit cards issued by overseas banks.

If you’re an iGaming merchant concerned about how the new legislation will affect your business, SafeCharge has created an FAQ to provide operators with answers to frequently asked questions. SafeCharge has pledged to offer free consultations for UK operators in need of updating their payments technology.

Information is available on the FAQ page.