npm - @paydock/client-sdk - Versions diffs - 1.94.22 → 1.100.0 - Mend

@paydock/client-sdk 1.94.22 → 1.100.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (27) hide show

package/.nvmrc +1 -0
package/README.md +189 -73
package/bundles/widget.umd.js +8847 -7218
package/bundles/widget.umd.min.js +1 -1
package/lib/components/param.d.ts +5 -0
package/lib/components/param.js +2 -0
package/lib/components/param.js.map +1 -1
package/lib/configs/env/env.d.ts +0 -1
package/lib/configs/env/env.js +0 -3
package/lib/configs/env/env.js.map +1 -1
package/lib/configs/sdk.js +1 -1
package/lib/wallet-buttons/flypay-v2.wallet-service.d.ts +20 -0
package/lib/wallet-buttons/flypay-v2.wallet-service.js +185 -0
package/lib/wallet-buttons/flypay-v2.wallet-service.js.map +1 -0
package/lib/wallet-buttons/google.wallet-service.js +11 -8
package/lib/wallet-buttons/google.wallet-service.js.map +1 -1
package/lib/wallet-buttons/interfaces.d.ts +10 -10
package/lib/wallet-buttons/paypal.wallet-service.d.ts +3 -0
package/lib/wallet-buttons/paypal.wallet-service.js +82 -41
package/lib/wallet-buttons/paypal.wallet-service.js.map +1 -1
package/lib/wallet-buttons/wallet-buttons.d.ts +10 -7
package/lib/wallet-buttons/wallet-buttons.js +14 -7
package/lib/wallet-buttons/wallet-buttons.js.map +1 -1
package/package.json +20 -19
package/slate.md +180 -65
package/typings/globals/@auspayplus/open-payments-checkout/index.d.ts +41 -0
package/typings/index.d.ts +1 -0

package/.nvmrc ADDED Viewed

	@@ -0,0 +1 @@
1	+ 18

package/README.md CHANGED Viewed

@@ -2636,7 +2636,7 @@ List of available triggers
 You can find description of all methods and parameters [here](https://www.npmjs.com/package/@paydock/client-sdk#payment-sources-simple-example)
 This widget provides a list of previously added (saved) payment-sources by customer_id or reference.
-The widget provides an opportunity to use events to track the process of selecting payment-sources and provide meta information about the payment-sources.
+The widget provides an opportunity to use events to track the process of selecting payment-sources and provide meta information about the payment-sources.
 Payment-source requires a query_token that represents a pre-generated and secure token for limiting the list
 payment-sources, for a specific user or reference.
@@ -2665,7 +2665,7 @@ list.load();
 // ES2015 | TypeScript
 import { HtmlPaymentSourceWidget } from '@paydock/client-sdk/payment-source-widget';
 var list = new HtmlPaymentSourceWidget('#list', 'publicKey', 'queryToken');
 list.load();
 ```
@@ -2673,7 +2673,7 @@ list.load();
 Then write only need 2 lines of code in js to initialize widget
-### Full example
+### Full example
 ```html
 <!DOCTYPE html>
@@ -2685,7 +2685,7 @@ Then write only need 2 lines of code in js to initialize widget
 </head>
 <body>
     <div id="list"></div>
-    <script src="https://widget.paydock.com/sdk/latest/widget.umd.js" ></script>
+    <script src="https://widget.paydock.com/sdk/latest/widget.umd.min.js" ></script>
     <script>
         var list = new paydock.HtmlPaymentSourceWidget('#list', 'publicKey', 'queryToken');
         list.load();
@@ -2725,9 +2725,9 @@ list.on('select', function(data) {
 });
 ```
-This example shows how you can use a lot of other methods to settings your form
+This example shows how you can use a lot of other methods to settings your form
-### Full example
+### Full example
 ```html
 <!DOCTYPE html>
@@ -2740,7 +2740,7 @@ This example shows how you can use a lot of other methods to settings your form
 <body>
     <div id="list"></div>
     <input type="text" name="ps_id" />
-    <script src="https://widget.paydock.com/sdk/latest/widget.umd.js" ></script>
+    <script src="https://widget.paydock.com/sdk/latest/widget.umd.min.js" ></script>
     <script>
         var list = new paydock.HtmlPaymentSourceWidget('#list', 'publicKey', 'queryToken');
         list.filterByTypes(['card', 'checkout']);
@@ -2750,9 +2750,9 @@ This example shows how you can use a lot of other methods to settings your form
         list.setStyles({
             icon_size: 'small'
         });
         list.load();
         list.onSelectInsert('input[name="ps_id"]', 'payment_source_id');
         list.on('select', function(data) {
             console.log(data);
@@ -5018,7 +5018,7 @@ The final method to beginning, the load process of widget to html
 You can find description of all methods and parameters [here](https://www.npmjs.com/package/@paydock/client-sdk#wallet-buttons-simple-example)
 Wallet Buttons allow you to easily integrate different E-Wallets into your checkout.
-Currently supports ApplePay, Google Pay, Google Pay and Apple Pay via Stripe, Flypay checkout, Paypal Smart Buttons Checkout and Afterpay.
+Currently supports ApplePay, Google Pay, Google Pay and Apple Pay via Stripe, Flypay and Flypay V2 checkout, Paypal Smart Buttons Checkout and Afterpay.
 If available in your client environment, you will display a simple button that upon clicking it the user will follow the standard flow for the appropriate Wallet. If not available an event will be raised and no button will be displayed.
@@ -5063,7 +5063,7 @@ var button = new WalletButtons(
 button.load();
 ```
-Flypay and Paypal wallets do not require any meta sent to the wallet, so the following is enough for initialization:
+Flypay, Flypay V2 and Paypal wallets do not require any meta sent to the wallet, so the following is enough for initialization:
 ```javascript
 let button = new paydock.WalletButtons(
     "#widget",
@@ -5168,7 +5168,7 @@ button.close();
 ### Performing actions when shipping info is updated
-In Flypay, Paypal and ApplePay via MPGS integrations after each shipping info update the `onUpdate(data)` will be called with the selected shipping address information (plus selected shipping method for Paypal). Merchants should handle this callback, recalculate shipping costs in their server by analyzing the new data, and submit a backend to backend request to `POST charges/:id` with the new total amount and shipping amount (you can find the documentation of this call in the PayDock API documentation).
+In Flypay, Paypal, ApplePay via MPGS and GooglePay via MPGS integrations after each shipping info update the `onUpdate(data)` will be called with the selected shipping address information, plus selected shipping method when applicable for Paypal, ApplePay and GooglePay. Merchants should handle this callback, recalculate shipping costs in their server by analyzing the new data, and submit a backend to backend request to `POST charges/:id` with the new total amount and shipping amount (you can find the documentation of this call in the PayDock API documentation).
 For Paypal integration specifically, if shipping is enabled for the wallet button and different shipping methods were provided in the create wallet charge call, Merchants must ensure that the posted `shipping.amount` to `POST charges/:id` matches the selected shipping option amount (value sent in when initializing the wallet charge). In other words, when providing shipping methods the shipping amount is bound to being one of the provided shipping method amount necessarily. Bear in mind that the total charge amount must include the `shipping.amount`, since it represents the full amount to be charged to the customer.
@@ -5177,18 +5177,18 @@ After analyzing the new shipping information, and making the post with the updat
 ```javascript
 button.onUpdate((data) => {
     console.log("Updating amount via a backend to backend call to POST charges/:id");
-	// call `POST charges/:id` to modify charge
-	button.update({ success: true });
+     // call `POST charges/:id` to modify charge
+     button.update({ success: true });
 });
 ```
-For ApplePay via MPGS integration specifically, you must return the new `amount` and new `shipping_options` If new options are needed based on the updated shipping data. Before the user authorizes the transaction with Touch ID, Face ID, or passcode, you receive redacted address information (address_country, address_city, address_state, address_postcode), this data can be used to recalculate the amount and new shipping options. (https://developer.apple.com/documentation/apple_pay_on_the_web/applepaypayment/1916097-shippingcontact)
+For ApplePay via MPGS and GooglePay via MPGS integrations, you can also return a new `amount` and new `shipping_options` in case new options are needed based on the updated shipping data. Before the user authorizes the transaction, you receive redacted address information (address_country, address_city, address_state, address_postcode), and this data can be used to recalculate the new amount and new shipping options.
 ```javascript
 button.onUpdate((data) => {
     console.log("Updating amount via a backend to backend call to POST charges/:id");
-	// call `POST charges/:id` to modify charge
-	button.update({
+     // call `POST charges/:id` to modify charge
+     button.update({
         success: true,
         body: {
             amount: 15,
@@ -5200,7 +5200,7 @@ button.onUpdate((data) => {
                     amount: "0.00"
                 },
                 {
-                    id: "NEW - FastShip",
+                    id: "NEW-FastShip",
                     label: "NEW - Fast Shipping",
                     detail: "Arrives in less than 1 day",
                     amount: "10.00"
@@ -5242,7 +5242,7 @@ button.on(EVENT.PAYMENT_ERROR, (data) => console.log("The payment was not succes
 This example shows how to use these functions for **Apple and Google Pay via Stripe**:
 _(Required `meta` fields: `amount_label`, `country`. Optional `meta` fields: `wallets`)_
-### Full example
+### Apple and Google Pay via Stripe Full example
 ```html
 <!DOCTYPE html>
@@ -5277,8 +5277,8 @@ _(Required `meta` fields: `amount_label`, `country`. Optional `meta` fields: `wa
 ```
 This example shows how to use these functions for **Paypal Smart Checkout Buttons**:
-_(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_later`, `style`)_
-### Full example
+_(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_later`, `standalone`, `style`)_
+### Paypal Smart Checkout Buttons Full example
 ```html
 <!DOCTYPE html>
 <html lang="en">
@@ -5293,26 +5293,27 @@ _(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_l
 <script src="https://widget.paydock.com/sdk/latest/widget.umd.min.js" ></script>
 <script>
     let button = new paydock.WalletButtons(
-		"#widget",
-		charge_token,
-		{
-			request_shipping: true,
-			pay_later: true,
-			style: {
-				layout: 'horizontal',
-				color: 'blue',
-				shape: 'rect',
-				label: 'paypal',
-			},
-		}
-	);
+          "#widget",
+          charge_token,
+          {
+               request_shipping: true,
+               pay_later: true,
+               standalone: false,
+               style: {
+                    layout: 'horizontal',
+                    color: 'blue',
+                    shape: 'rect',
+                    label: 'paypal',
+               },
+          }
+     );
     button.setEnv('sandbox');
     button.onUnavailable(() => console.log("No wallet buttons available"));
     button.onUpdate((data) => {
-		console.log("Updating amount via a backend to backend call to POST charges/:id");
-		// call `POST charges/:id` to modify charge
-		button.update({ success: true });
-	});
+          console.log("Updating amount via a backend to backend call to POST charges/:id");
+          // call `POST charges/:id` to modify charge
+          button.update({ success: true });
+     });
     button.onPaymentSuccessful((data) => console.log("The payment was successful"));
     button.onPaymentError((data) => console.log("The payment was not successful"));
     button.onPaymentInReview((data) => console.log("The payment is on fraud review"));
@@ -5321,8 +5322,46 @@ _(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_l
 </html>
 ```
-This example shows how to use these functions for **Flypay Checkout**.
+This example shows how to use these functions for **Flypay v1 Wallet**.
 _(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_later`, `style`)_
+### Flypay Full example
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <title>Title</title>
+</head>
+<body>
+    <h2>Payment using PayDock Wallet Button!</h2>
+    <div id="widget"></div>
+</body>
+<script src="https://widget.paydock.com/sdk/latest/widget.umd.min.js" ></script>
+<script>
+    let button = new paydock.WalletButtons(
+          "#widget",
+          charge_token,
+          {
+               request_shipping: true
+          }
+     );
+    button.setEnv('sandbox');
+    button.onUnavailable(() => console.log("No wallet buttons available"));
+    button.onUpdate((data) => {
+          console.log("Updating amount via a backend to backend call to POST charges/:id");
+          // call `POST charges/:id` to modify charge
+          button.update({ success: true });
+     });
+    button.onPaymentSuccessful((data) => console.log("The payment was successful"));
+    button.onPaymentError((data) => console.log("The payment was not successful"));
+    button.onPaymentInReview((data) => console.log("The payment is on fraud review"));
+    button.load();
+</script>
+</html>
+```
+This example shows how to use these functions for **Flypay v2 Wallet**.
+_(Required `meta` fields: - . Optional `meta` fields: -)_
 ### Full example
 ```html
 <!DOCTYPE html>
@@ -5340,28 +5379,21 @@ _(Required `meta` fields: - . Optional `meta` fields: `request_shipping`, `pay_l
     let button = new paydock.WalletButtons(
 		"#widget",
 		charge_token,
-		{
-			request_shipping: true
-		}
+		{},
 	);
     button.setEnv('sandbox');
     button.onUnavailable(() => console.log("No wallet buttons available"));
-    button.onUpdate((data) => {
-		console.log("Updating amount via a backend to backend call to POST charges/:id");
-		// call `POST charges/:id` to modify charge
-		button.update({ success: true });
-	});
     button.onPaymentSuccessful((data) => console.log("The payment was successful"));
     button.onPaymentError((data) => console.log("The payment was not successful"));
-    button.onPaymentInReview((data) => console.log("The payment is on fraud review"));
     button.load();
 </script>
 </html>
 ```
-This example shows how to use these functions for **ApplePay via MPGS**:
+This example shows how to use these functions for **ApplePay via MPGS** and **GooglePay via MPGS**:
 _(Required `meta` fields: `amount_label`, `country`. Optional `meta` fields: `raw_data_initialization`, `request_shipping`, `style.button_type`)_
-### Full example
+### ApplePay and GooglePay via MPGS Full example
 ```html
 <!DOCTYPE html>
@@ -5383,8 +5415,16 @@ _(Required `meta` fields: `amount_label`, `country`. Optional `meta` fields: `ra
             amount_label: "Total",
             country: 'DE',
             request_shipping: true,
+            show_billing_address: true,
             style: {
-                button_type: 'buy',
+                google: {
+                    button_type: 'buy',
+                    button_size_mode: 'static',
+                    button_color: 'white',
+                },
+                apple: {
+                    button_type: 'buy',
+                },
             },
             shipping_options: [
                 {
@@ -5406,14 +5446,40 @@ _(Required `meta` fields: `amount_label`, `country`. Optional `meta` fields: `ra
     button.onUnavailable(() => console.log("No wallet buttons available"));
     button.onPaymentSuccessful((data) => console.log("The payment was successful"));
     button.onPaymentError((data) => console.log("The payment was not successful"));
+    button.onUpdate((data) => {
+        console.log("Updating amount via a backend to backend call to POST charges/:id");
+        // call `POST charges/:id` to modify charge
+        button.update({
+            success: true,
+            body: {
+                amount: 15,
+                shipping_options: [
+                    {
+                        id: "NEW-FreeShip",
+                        label: "NEW - Free Shipping",
+                        detail: "Arrives in 3 to 5 days",
+                        amount: "0.00"
+                    },
+                    {
+                        id: "NEW-FastShip",
+                        label: "NEW - Fast Shipping",
+                        detail: "Arrives in less than 1 day",
+                        amount: "10.00"
+                    }
+                ]
+            }
+        });
+    });
     button.load();
 </script>
 </html>
 ```
-Also, for **ApplePay via MPGS** you can initialize the `ApplePayPaymentRequest` with your own values instead of using the default ones. Below you can see an example on how to initialize the `ApplePayPaymentRequest` with the `raw_data_initialization` meta field:
+Also, for **ApplePay via MPGS** you can initialize the `ApplePayPaymentRequest` with your own values instead of using the default ones. Below you can see an example on how to initialize the `ApplePayPaymentRequest` with the `raw_data_initialization` meta field.
+Similarly, for **GooglePay via MPGS** you can initialize the `PaymentMethodSpecification` with your own values instead of using the default ones. Below you can see an example on how to initialize the `PaymentMethodSpecification` with the `raw_data_initialization` meta field.
-### Raw data initialization example
+### ApplePay and GooglePay via MPGS Raw data initialization example
 ```html
 <!DOCTYPE html>
@@ -5433,23 +5499,48 @@ Also, for **ApplePay via MPGS** you can initialize the `ApplePayPaymentRequest`
         charge_token,
         {
             raw_data_initialization: {
-                countryCode: "AU",
-                currencyCode: "AUD",
-                merchantCapabilities: ["supports3DS","supportsCredit","supportsDebit"],
-                supportedNetworks: ["visa","masterCard","amex","discover"],
-                requiredBillingContactFields: ["name","postalAddress"],
-                requiredShippingContactFields:["postalAddress","name","phone","email" ],
-                total: {
-                    label: "Total",
-                    amount: "10",
-                    type: "final",
-                }
+                apple: {
+                    countryCode: "AU",
+                    currencyCode: "AUD",
+                    merchantCapabilities: ["supports3DS","supportsCredit","supportsDebit"],
+                    supportedNetworks: ["visa","masterCard","amex","discover"],
+                    requiredBillingContactFields: ["name","postalAddress"],
+                    requiredShippingContactFields:["postalAddress","name","phone","email" ],
+                    total: {
+                        label: "Total",
+                        amount: "10",
+                        type: "final",
+                    }
+                },
+                google: {
+                    type: "CARD",
+                    parameters: {
+                        allowedAuthMethods: ["PAN_ONLY", "CRYPTOGRAM_3DS"],
+                        allowedCardNetworks: [
+                            "AMEX",
+                            "DISCOVER",
+                            "INTERAC",
+                            "JCB",
+                            "MASTERCARD",
+                            "VISA",
+                        ],
+                        billingAddressRequired: true,
+                    },
+                },
             },
             amount_label: "Total",
             country: 'DE',
             request_shipping: true,
+            show_billing_address: true,
             style: {
-                button_type: 'buy',
+                google: {
+                    button_type: 'buy',
+                    button_size_mode: 'static',
+                    button_color: 'white',
+                },
+                apple: {
+                    button_type: 'buy',
+                },
             },
             shipping_options: [
                 {
@@ -5471,6 +5562,30 @@ Also, for **ApplePay via MPGS** you can initialize the `ApplePayPaymentRequest`
     button.onUnavailable(() => console.log("No wallet buttons available"));
     button.onPaymentSuccessful((data) => console.log("The payment was successful"));
     button.onPaymentError((data) => console.log("The payment was not successful"));
+    button.onUpdate((data) => {
+        console.log("Updating amount via a backend to backend call to POST charges/:id");
+        // call `POST charges/:id` to modify charge
+        button.update({
+            success: true,
+            body: {
+                amount: 15,
+                shipping_options: [
+                    {
+                        id: "NEW-FreeShip",
+                        label: "NEW - Free Shipping",
+                        detail: "Arrives in 3 to 5 days",
+                        amount: "0.00"
+                    },
+                    {
+                        id: "NEW-FastShip",
+                        label: "NEW - Fast Shipping",
+                        detail: "Arrives in less than 1 day",
+                        amount: "10.00"
+                    }
+                ]
+            }
+        });
+    });
     button.load();
 </script>
 </html>
@@ -5480,7 +5595,7 @@ Also, for **ApplePay via MPGS** you can initialize the `ApplePayPaymentRequest`
 <dl>
 <dt><a href="#WalletButtons">WalletButtons</a></dt>
-<dd><p>Class WalletButtons to work with different E-Wallets within html (currently supports Apple Pay, Google Pay, Google Pay™ and Apple Pay via Stripe, Flypay, Paypal, Afterpay)</p>
+<dd><p>Class WalletButtons to work with different E-Wallets within html (currently supports Apple Pay, Google Pay, Google Pay™ and Apple Pay via Stripe, Flypay, Flypay V2, Paypal, Afterpay)</p>
 </dd>
 </dl>
@@ -5518,18 +5633,19 @@ Interface of data used by the wallet checkout and payment proccess.
 | Param | Type | Description |
 | --- | --- | --- |
-| [amount_label] | <code>string</code> | Label shown next to the total amount to be paid. Required for [Stripe, ApplePay, GooglePay]. N/A for [FlyPay, PayPal, Afterpay]. |
-| [country] | <code>string</code> | Country of the user. 2 letter ISO code format. Required for [Stripe, ApplePay, GooglePay, Afterpay]. N/A for [FlyPay, PayPal]. |
-| [pay_later] | <code>string</code> | Used to enable Pay Later feature in PayPal Smart Checkout WalletButton integration when available. Optional for [PayPal]. N/A for other wallets. |
+| [amount_label] | <code>string</code> | Label shown next to the total amount to be paid. Required for [Stripe, ApplePay, GooglePay]. N/A for [FlyPay, Flypay V2, PayPal, Afterpay]. |
+| [country] | <code>string</code> | Country of the user. 2 letter ISO code format. Required for [Stripe, ApplePay, GooglePay, Afterpay]. N/A for [FlyPay, Flypay V2, PayPal]. |
+| [pay_later] | <code>boolean</code> | Used to enable Pay Later feature in PayPal Smart Checkout WalletButton integration when available. Optional for [PayPal]. N/A for other wallets. |
+| [standalone] | <code>boolean</code> | Used to enable Standalone Buttons feature in PayPal Smart Checkout WalletButton integration. Used together with `pay_later`. Optional for [PayPal]. N/A for other wallets. |
 | [show_billing_address] | <code>boolean</code> | Used to hide/show the billing address on ApplePay and GooglePay popups. Default value is false. Optional for [ApplePay, GooglePay]. N/A for other wallets. |
 | [request_payer_name] | <code>boolean</code> | Used mainly for fraud purposes - recommended set to true. Optional for [Stripe]. N/A for other wallets. |
 | [request_payer_email] | <code>boolean</code> | Used mainly for fraud purposes - recommended set to true. Optional for [Stripe]. N/A for other wallets. |
 | [request_payer_phone] | <code>boolean</code> | Used mainly for fraud purposes - recommended set to true. Optional for [Stripe]. N/A for other wallets. |
-| [request_shipping] | <code>boolean</code> | Used to request or not shipping address in the Wallet checkout, being able to handle amount changes via the `update` event. Optional for [FlyPay, PayPal, ApplePay, GooglePay]. N/A for [Stripe, Afterpay]. |
+| [request_shipping] | <code>boolean</code> | Used to request or not shipping address in the Wallet checkout, being able to handle amount changes via the `update` event. Optional for [FlyPay, PayPal, ApplePay, GooglePay]. N/A for [Flypay V2, Stripe, Afterpay]. |
 | [shipping_options] | [<code>Array.&lt;IApplePayShippingOption&gt;</code>](#IApplePayShippingOption) \| [<code>Array.&lt;IPayPalShippingOption&gt;</code>](#IPayPalShippingOption) | Used to provide available shipping options.(To use shipping_options the request_shipping flag should be true). Optional for [ApplePay]. N/A for the other wallets. |
 | [merchant_name] | <code>string</code> | Merchant Name used for GooglePay integration via MPGS. Required for [GooglePay]. N/A for other wallets. |
 | [raw_data_initialization] | <code>object</code> | Used to provide values to initialize wallet with raw data. Optional for [ApplePay]. N/A for the other wallets. |
-| [style] | <code>object</code> | Used to style PayPal buttons, check possible values at https://developer.paypal.com/docs/business/checkout/reference/style-guide. Also used at ApplePay, GooglePay and Afterpay to select button type. Optional for [PayPal, ApplePay, GooglePay, Afterpay]. N/A for [Stripe, FlyPay]. |
+| [style] | <code>object</code> | For **Paypal**: used to style the buttons, check possible values in the [style guide](https://developer.paypal.com/docs/business/checkout/reference/style-guide). When `standalone` and `pay_later`, extra options can be provided in `style.messages` with the [messages style options](https://developer.paypal.com/docs/checkout/pay-later/us/integrate/reference/#stylelayout). Also used at **ApplePay**, **GooglePay** and **Afterpay** to select button type. Optional for [PayPal, ApplePay, GooglePay, Afterpay]. N/A for [Stripe, FlyPay, Flypay V2]. |
 | [style.button_type] | <code>object</code> | Used to select ApplePay button type (e.g: 'buy','donate', etc), check possible values at https://developer.apple.com/documentation/apple_pay_on_the_web/displaying_apple_pay_buttons_using_css. Also select button type for GooglePay (check GooglePayStyles) and Afterpay (check AfterpayStyles). Optional for [ApplePay, GooglePay, Afterpay]. N/A for other wallets. |
 | [style.height] | <code>object</code> | Used to select Afterpay button height. Optional for [Afterpay]. N/A for other wallets. |
 | [wallets] | <code>array</code> | By default if this is not sent or empty, we will try to show either Apple Pay or Google Pay buttons. This can be limited sending the following array in this field: ['apple','google]. Optional for [Stripe, ApplePay, GooglePay]. N/A for other wallets. |
@@ -5581,7 +5697,7 @@ Interface of Shipping Options for PayPal
 <a name="WalletButtons" id="WalletButtons" href="#WalletButtons">&nbsp;</a>
 ## WalletButtons
-Class WalletButtons to work with different E-Wallets within html (currently supports Apple Pay, Google Pay, Google Pay™ and Apple Pay via Stripe, Flypay, Paypal, Afterpay)
+Class WalletButtons to work with different E-Wallets within html (currently supports Apple Pay, Google Pay, Google Pay™ and Apple Pay via Stripe, Flypay, Flypay V2, Paypal, Afterpay)
 **Kind**: global class
@@ -6399,4 +6515,4 @@ List of available event's name in the SRC checkout lifecycle
 ## License
-Copyright (c) 2022 paydock
+Copyright (c) 2023 paydock