airwallex-payment-elements
Advanced tools
airwallex-payment-elements - npm Package Compare versions
Comparing version 0.0.60 to 0.0.61
@@ -1,4 +0,4 @@ | ||
| /* Airwallex Checkout Component Version [0.0.60] */ | ||
| /* Airwallex Checkout Component Version [0.0.61] */ | ||
| "use strict";Object.defineProperty(exports,"__esModule",{value:!0});const e="https://checkout.airwallex.com/assets/bundle.min.js",r=Promise.resolve().then(()=>{if("undefined"==typeof window)return null;if(window.Airwallex)return window.Airwallex;const r=document.querySelector(`script[src="${e}"], script[src="${e}/"]`)||(()=>{const r=document.createElement("script");r.src=e;const t=document.head||document.body;if(!t)throw new Error("Expected document.body not to be null. Airwallex.js requires a <head> or <body> element.");return t.appendChild(r),r})();return new Promise((e,t)=>{r.addEventListener("load",()=>{window.Airwallex?e():t(new Error("Failed to load Airwallex.js"))}),r.addEventListener("error",()=>{t(new Error("Failed to load Airwallex.js"))})})});exports.loadAirwallex=()=>r; | ||
| /* Airwallex @Charlie.Lang */ | ||
| //# sourceMappingURL=airwallex.cjs.js.map |
@@ -1,4 +0,4 @@ | ||
| /* Airwallex Checkout Component Version [0.0.60] */ | ||
| /* Airwallex Checkout Component Version [0.0.61] */ | ||
| const e="https://checkout.airwallex.com/assets/bundle.min.js",r=Promise.resolve().then(()=>{if("undefined"==typeof window)return null;if(window.Airwallex)return window.Airwallex;const r=document.querySelector(`script[src="${e}"], script[src="${e}/"]`)||(()=>{const r=document.createElement("script");r.src=e;const o=document.head||document.body;if(!o)throw new Error("Expected document.body not to be null. Airwallex.js requires a <head> or <body> element.");return o.appendChild(r),r})();return new Promise((e,o)=>{r.addEventListener("load",()=>{window.Airwallex?e():o(new Error("Failed to load Airwallex.js"))}),r.addEventListener("error",()=>{o(new Error("Failed to load Airwallex.js"))})})}),o=()=>r;export{o as loadAirwallex}; | ||
| /* Airwallex @Charlie.Lang */ | ||
| //# sourceMappingURL=airwallex.es.js.map |
@@ -1,4 +0,4 @@ | ||
| /* Airwallex Checkout Component Version [0.0.60] */ | ||
| /* Airwallex Checkout Component Version [0.0.61] */ | ||
| var Airwallex=function(e){"use strict";const r="https://checkout.airwallex.com/assets/bundle.min.js",t=Promise.resolve().then(()=>{if("undefined"==typeof window)return null;if(window.Airwallex)return window.Airwallex;const e=document.querySelector(`script[src="${r}"], script[src="${r}/"]`)||(()=>{const e=document.createElement("script");e.src=r;const t=document.head||document.body;if(!t)throw new Error("Expected document.body not to be null. Airwallex.js requires a <head> or <body> element.");return t.appendChild(e),e})();return new Promise((r,t)=>{e.addEventListener("load",()=>{window.Airwallex?r():t(new Error("Failed to load Airwallex.js"))}),e.addEventListener("error",()=>{t(new Error("Failed to load Airwallex.js"))})})});return e.loadAirwallex=()=>t,e}({}); | ||
| /* Airwallex @Charlie.Lang */ | ||
| //# sourceMappingURL=airwallex.iife.js.map |
| { | ||
| "name": "airwallex-payment-elements", | ||
| "version": "0.0.60", | ||
| "version": "0.0.61", | ||
| "module": "lib/airwallex.es.js", | ||
@@ -10,2 +10,13 @@ "types": "types/index.d.ts", | ||
| "license": "MIT", | ||
| "keywords": [ | ||
| "Airwallex", | ||
| "Payments", | ||
| "Acquiring", | ||
| "Checkout", | ||
| "Payment request API", | ||
| "PCI", | ||
| "HPP", | ||
| "Drop-in", | ||
| "Elements" | ||
| ], | ||
| "scripts": { | ||
@@ -12,0 +23,0 @@ "build-polyfill": "rollup -c --environment INCLUDE_DEPS && tsc", |
| # airwallex-payment-elements | ||
| This universal library is a lightweight javascript SDK, which allow merchant site to integrate with airwallex checkout flow with convenient | ||
| This universal library is a lightweight javascript SDK, which allow merchant site to convenient integrate with airwallex checkout flow | ||
| From the merchant perspective, The (Hosted Payment Page)HPP / Drop-in / Elements integration happen after shopper decide to checkout an order, Airwallex javascript SDK help merchant accept payments on merchant website, the whole user experience include create an [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro) entity to tacking the payment request which link to merchant’s order information, Airwallex using a payment attempt entity to collect payment methods details from a shopper, and the PaymentIntent entity tracking the [payment attempts](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Attempts/Intro) and state change all the way through user interactions, you can checkout the [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro) section for more details | ||
| From the merchant perspective, The Hosted Payment Page(HPP) / Drop-in / Elements integration happen after shopper decide to checkout an order on merchant's website, Airwallex javascript SDK help merchant accept payments on merchant website, the whole user experience include create an [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro) entity to tacking the payment request, which link to merchant’s order entity, Airwallex using a [paymentAttempt](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Attempts/Intro) entity to collect payment methods details from a shopper, and link back to the PaymentIntent entity, which tracking the state change all the way through user interactions, you can checkout the [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro) section for more details | ||
| With the API integration from merchant server, after PaymentIntent is successfully created, the response of the API call will also return a unique ID for the PaymentIntent, and a client_secret which act as a single source of truth cross over the shopping experience, each time user's interaction trigger a service call Airwallex client API will validate against the client_secret to secure the payment flow | ||
| With the API integration from merchant server, after PaymentIntent is successfully created, the response of the API call will return a unique ID for the PaymentIntent, and a client_secret which act as a single source of truth cross over the shopping experience, each time user's interaction trigger a service call Airwallex client API will validate against the client_secret to secure the whole payment flow | ||
@@ -41,4 +41,3 @@ So long story short, the merchant website checkout start with PaymentIntent and client_secret | ||
| ```client_secret``` | ||
| Can find it from response when create [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/_api_v1_pa_payment_intents_create/post) | ||
| ```client_secret``` - [REQUIRED], can find it from response when create [PaymentIntent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/_api_v1_pa_payment_intents_create/post) | ||
@@ -119,3 +118,3 @@ ```gateway_url``` - [REQUIRED], is the domain url to loading airwallex checkout assets (html, javascript, css, fonts), it's also the server url for user interaction like submit checkout form. | ||
| With Drop-in integration, those prebuilt UI components has been composed into a payment form with all available payment methods, you can put it directly into you html page, and integrate with the rest your own components to render your checkout page. | ||
| With Drop-in integration, those prebuilt UI components has been composed into a payment form with all available payment methods, you can put it directly into you html page, and integrate with the rest of your own components to render your checkout page. | ||
@@ -126,7 +125,7 @@ With *cardNumber* | *expiry* | *cvc* | *paymentRequestButton* | *wechat* elements, they are just building blocks: | ||
| > Show and hide any one of them at any moment you want | ||
| > Show and hide anyone of them at any moment you want | ||
| > Customize the looks and feel with your wishes, and most importantly | ||
| > Customize the look and feels as you want | ||
| > You own component can even interact with shoppers when they click or typing in those elements by listen on the events | ||
| > Listen on the events and interact with shoppers when they click or typing in those elements | ||
@@ -251,3 +250,3 @@ #### Create element interface | ||
| ```ts | ||
| window.addEventListener('onSuccess', (event: ElementBaseEvent) => { | ||
| window.addEventListener('onChange', (event: ElementBaseEvent) => { | ||
| /* | ||
@@ -254,0 +253,0 @@ ... Handle event |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.52%
27210
Worsened metrics
- Number of lines in readme file
- decreased by-0.38%
263
No dependency changes