Widget FAQ

Payment Button FAQ

How long is the checkout.id valid for?

The checkout.id expires after 30 minutes.

What happens when a popup is closed?

Some methods of payment on Payment Button enable checkout in a popup/lightbox. When the popup is shown it is possible to checkout or to close it. In the case where the popup is closed, it is possible for the shopper to continue their checkout with another method of payment, e.g. to choose Masterpass, change their mind, close the popup and then checkout with, say, a credit card. Payment Button gracefully handles these multiple brands per checkout session.

Does Payment Button support 3D Secure?

Yes, the Payment Button payment forms has 3D Secure built in. To activate 3D Secure, the channel needs to be configured and an enrolled card entered. For testing you can use the following:

VISA 4200000000000000 (no 3D)
4012001037461114 (3D Secure enrolled / fail authentication)
MASTER 5454545454545454 (no 3D)
5212345678901234 (3D enrolled)
AMEX 377777777777770 (no 3D)
375987000000005 (3D enrolled)

What languages are supported on the payment form?

By default there are 25: en, de, fr, es, it, nl, dk, fi, se, tr, ja, sl, pt, pl, cz, hu, bg, ro, ru, cn, gr, no, sk, ar, ko. But it is possible to change the text value of the labels to anything you choose using the wpwlOptions API.

What is Active Payment Method Selection (APMS)?

Active Payment Method Selection allows you to dynamically offer different payment brands based on each individual shopper's risk profile. With this integration you can: -Offer the perfect mix of local payment methods
-Steer the payment selection actively and in real time during the checkout
-Optimize risk management to each shop‘s business requirements

What happens if a shopper closes their browser?

If a shopper closes their browser after selecting the payment method but before actually executing the payment, it can cause reconciliation issues as your platform would never receive the final status of the payment. For this reason we automatically call the shopperResultUrl if it has not been called after 29 minutes. This way your platform can request the final status, being notified that the payment was not processed. A notification will be sent from the gateway to the shop to trigger the get status before the checkout id times out, but only after "pay now" button is clicked in the payment widget.

Technically, if POST /checkouts/{id}/payment was called and GET /checkouts/{id}/payment was not called, OPP sends a GET request to the shopperResultUrl with a resourcePath parameter, suggesting the merchant to call GET /checkouts/{id}/payment. The same applies to /checkouts/{id}/registration.

IMPORTANT: The baseUrl must end in a "/", e.g. "https://test.emetec.pro/".

Does Payment Button support responsive Webdesign?

Yes, Payment Button on OPP is supporting responsive design

Which browsers are supported by Payment Button?

All current browsers are supported by Payment Button. We also take care that older browsers that are still in use are supported. The only browser where this means limitations are older versions of Internet Explorer. There we test the functionality for versions >= 11. Please include following meta tak in your html source.

<meta http-equiv="X-UA-Compatible" content="IE=edge">

Could Payment Button be used as a stand-alone widget?

Yes, and multiple clients are using it that way

Why should I use Payment Button and not my own forms?

-Payment Button was the first certified PCI 3 SAQ-A compliant payment form solution available in the market. Please find further information at /support-pci

-Payment Button offers a huge variety of versatile features. While being very easy to integrate on a webpage with only two code lines various use-cases are available and supported at the same time. Please find further information at Customization Guide and Advanced Options.

Payment Button looks nice and simple, but I've got my own shop designs. How can I adapt Payment Button to my design?

Just have a look at the Customization Guide. This features an interactive editor where you can try out any styles from the style reference on the same page.

How can I validate the cardholder's name?

This can be done using the below java script in Payment Button customization. The java script does the validation but it is not connected to any setup in BIP.

var wpwlOptions = { 
onBeforeSubmitCard: function(e){ 
var holder = $('.wpwl-control-cardHolder').val(); 
if (holder.trim().length < 2){ 
$('.wpwl-control-cardHolder').addClass('wpwl-has-error').after('<div class="wpwl-hint wpwl-hint-cardHolderError">Invalid card holder</div>'); 
return false; 
return true; 

My payment form needs additional information. How can I add my own text, messages and fields to Payment Button?

Just have a look at the Advanced Options Guide. This features an interactive editor where you can find examples of typical extensions of Payment Button. Use these as a starting point and extend it using the API Reference.