Last updated
Last updated
Here you can find some examples of advanced workflow customization for COPYandPAY. Each of the examples provided use the wpwlOptions
variable, the full reference for which can be found on our .
Please note that JavaScript examples from COPYandPAY can be used only when including jQuery.
You can add additional parameters to the payment form using the wpwlOptions
variable, prior to loading COPYandPAY. In the example above, we add a custom parameter to the payment form for recording the number of installments requested by the customer. The steps are listed below.
Prepare the checkout
Using the wpwlOptions API onLoad event, add the custom field HTML to the payment form
Set the name of the html input field to your API parameter e.g. recurring.numberOfInstallments
You can change a label in the payment form using the wpwlOptions
variable, prior to loading the COPYandPAY payment widget. In the following example, we'll change the credit card brand label in the payment form.
Prepare the order
Using the wpwlOptions API onLoad event, use a JQuery selector to set the desired value of the label
You can change the behavior of the payment page when there are multiple types of payment methods using the wpwlOptions
variable, prior to loading the COPYandPAY payment widget.
Prepare the checkout
Using the wpwlOptions API onLoad event, iterate through each .wpwl-container adding custom HTML before the container
Create a JQuery click handler to show the container on click.
You can change the behavior of the payment page when there are multiple types of payment methods using the wpwlOptions
variable, prior to loading the COPYandPAY payment widget.
Prepare the checkout
Using the wpwlOptions API onReady event and make some adaptions to the containers.
Create a JQuery click handler to show the container on click.
It is possible to use COPYandPAY to temporarily store the payment information after submission, rather than executing it straight away. This can be useful if you want to display an order summary page before committing the payment. This can be done using the wpwlOptions
variable, prior to loading the COPYandPAY.
To commit the payment after the summary page has been displayed, you can include the following form on the summary page. When the submit button is pressed, the payment will be executed.
There are two ways to store the payment details used during a checkout:
Set the createRegistration parameter to true during step 1 - prepare the checkout
Add a checkbox to the COPYandPAY form to let the customer decide whether or not to store the card details.
(Option 2 is demonstrated in the example below).
COPYandPAY allows you to modify the order of the fields in the payment form. As a result of this reordering, the order in which fields get tabbed will be adjusted accordingly. For details, please take a look at the JavaScript section in the following integration form.
It's possible to have the billing address fields available and even have them pre-filled. There are two options to do this:
To display the form, use the following option in wpwlOptions:
To display the form, use the following option in wpwlOptions:
Remark:
Use the mandatoryBillingFields options in order to control if some field will be validated (for empty value) or not.
It is possible to mask cvv on COPYandPAY, which can be done by setting "maskCvv" to true in wpwlOptions
variable, prior to loading the COPYandPAY payment widget.
To influence the brand detection behavior, use the following options in wpwlOptions
variable prior to loading the COPYandPAY payment widget.
Sometimes you might want to hide some brands when multiple brands are detected. This can guide the shopper to select your preferred brand. There are several options to implement this feature:
If you use your own brand images, implement onDetectBrand
. This method is called with a list of detected brands. With this information you can choose to show or hide your images.
Use COPYandPAY images the "logos" style. By default this style dynamically displays all detected brands as you type the card number. You can implement onChangeBrand
to change this behavior.
The following snippet gives an example how to implement Option 2. Except for the first detected brand, all other brands are hidden behind three dots (...). The hidden brands are shown only after the three dots are clicked.
Try for example the BIN 513678 from which multiple brands are detected.
In order to reload the widget, it's not enough to remove it from the page. You need to remove event bindings and stop the iframe communication, otherwise the previous widget will present unwanted error messages. To achieve that, use the wpwl.unload method and remove the static.min.js script.
After doing this, you can insert again the form with the brands and the paymentWidgets.js script in order to reload the widget.
The code below is an example of how to unload the widget.