EasySafePay (Web/WAP) | EasySafePay | Alipay Docs (2024)

This article introduces the integration solution to support accepting payments from a desktop browser or mobile browser. After integration, you can access various payment methods like digital wallets, bank cards, and bank transfers.

The following screenshots show the user experience of wallet and bank transfer. During the first-time payments, buyers can enable password-free payment for subsequent payments. The entire payment process for subsequent payments will be performed on your website or application.

Wallet

With the entire payment process remaining within your website or application, buyers are allowed to pay and enable password-free payments during their first-time payments and make subsequent payments without the need to enter the payment password.

Bank transfer

For bank transfer payment methods, the following graphics show the user experience for the first-time and subsequent payments.

Start your integration by taking the following steps:

1. Create a payment session
2. Invoke the SDK
3. Obtain authorization or payment result

Step 1: Create a payment session Server-side

When a buyer selects a payment method provided by Antom, you need to collect essential information including the payment request ID, order amount, payment method, order description, payment redirect page URL, and payment result notification URL. Susequently, call the createPaymentSession API to create a payment session by completing these steps:

1. Install an API library
2. Initialize the request instance
3. Call the createPaymentSession API

Note: Antom provides server-side API libraries for multiple languages. The following codes use Java as an example. You need to install Java 6 or higher.

Install an API library

You can find the latest version on GitHub.

<dependency> <groupId>com.alipay.global.sdk</groupId> <artifactId>global-open-sdk-java</artifactId> <version>2.0.21</version></dependency>

Initialize the request instance

Create a singleton resource to make a request to Antom.

import com.alipay.global.api.AlipayClient;import com.alipay.global.api.DefaultAlipayClient;String merchantPrivateKey = "YOUR PRIVATE KEY";String alipayPublicKey = "ALIPAY PUBLIC KEY";AlipayClient defaultAlipayClient = new DefaultAlipayClient(EndPointConstants.SG, merchantPrivateKey, alipayPublicKey);

Call the createPaymentSession API

AlipayPaymentSessionRequest alipayPaymentSessionRequest = new AlipayPaymentSessionRequest();alipayPaymentSessionRequest.setClientId(clientId);alipayPaymentSessionRequest.setPath("/ams/sandbox/api/v1/payments/createPaymentSession");alipayPaymentSessionRequest.setProductCode(ProductCodeType.AGREEMENT_PAYMENT);alipayPaymentSessionRequest.setProductScene(ProductSceneConstants.EASY_PAY);// replace to your paymentRequestIdalipayPaymentSessionRequest.setPaymentRequestId("paymentRequestId001");Amount amount = new Amount();// set amountamount.setCurrency("CNY");amount.setValue("100");alipayPaymentSessionRequest.setPaymentAmount(amount);//set settlement currencySettlementStrategy settlementStrategy = new SettlementStrategy();settlementStrategy.setSettlementCurrency("USD");alipayPaymentSessionRequest.setSettlementStrategy(settlementStrategy);// set agreementInfoAgreementInfo agreementInfo = new AgreementInfo();agreementInfo.setAuthState("authState001");agreementInfo.setUserLoginId("userLoginId001");alipayPaymentSessionRequest.setAgreementInfo(agreementInfo);// set paymentMethodPaymentMethod paymentMethod = new PaymentMethod();paymentMethod.setPaymentMethodType("ALIPAY_CN");// set order InfoOrder order = new Order();order.setReferenceOrderId("referenceOrderId001");order.setOrderDescription("orderDescription001");order.setOrderAmount(amount);Buyer buyer = new Buyer();buyer.setReferenceBuyerId("referenceBuyerId001");order.setBuyer(buyer);order.setOrderAmount(amount);alipayPaymentSessionRequest.setOrder(order);// replace to your redirect urlalipayPaymentSessionRequest.setPaymentNotifyUrl("https://www.yourNotifyUrl");alipayPaymentSessionRequest.setPaymentRedirectUrl("https://www.yourMerchantWeb.com");AlipayPaymentSessionResponse alipayPaymentSessionResponse = defaultAlipayClient .execute(alipayPaymentSessionRequest);

{ "settlementStrategy": { "settlementCurrency": "USD" }, "productCode": "AGREEMENT_PAYMENT", "productScene": "EASY_PAY", "paymentNotifyUrl": "https://www.yourNotifyUrl", "paymentRequestId": "paymentRequestId001", "paymentRedirectUrl": "https://www.yourMerchantWeb.com", "paymentMethod": { "paymentMethodType": "ALIPAY_CN" }, "agreementInfo": { "authState": "authState001", "userLoginId":"userLoginId001" }, "paymentAmount": { "currency": "CNY", "value": "100" }, "order": { "orderAmount": { "currency": "CNY", "value": "100" }, "referenceOrderId": "referenceOrderId001", "orderDescription": "orderDescription001", "buyer":{ "referenceBuyerId":"referenceBuyerId001" } }}

{ "paymentSessionData": "UNvjVWnWPXJA4BgW+vfjsQj7PbOraafHY19X+6EqMz6Kvvmsdk+akdLvoShW5avHX8e8J15P8uNVEf/PcCMyXg==&&SG&&111", "paymentSessionExpiryTime": "2023-04-06T03:28:49+08:00", "paymentSessionId": "UNvjVWnWPXJA4BgW+vfjsQj7PbOraafHY19X+6EqMz6Ikyj9FPVUOpv+DjiIZqMe", "result": { "resultCode": "SUCCESS", "resultMessage": "success.", "resultStatus": "S" }}

Common questions

Q: Can I use Chinese characters in the value of the request parameters?

A: To avoid incompatibility of a certain payment method, do not use Chinese characters for fields in the request.

Q: How to set the URL to receive the payment notification?

A: Specify paymentNotifyUrl in the createPaymentSession API to receive the asynchronous notification about the payment result (notifyPayment), or configure the receiving URL in Antom Dashboard. If the URL is specified in both the request and Antom Dashboard, the value specified in the request takes precedence.

Step 2: Invoke the SDK Client-side

Install

Before beginning the integration, ensure that you have completed the following environment preparations:

• Properly handle compatibility issues: Provide corresponding polyfills for Internet Explorer and other old browser versions. We recommend that you use babel-preset-env to address browser compatibility issues when you build a project.
• Use the following recommended browser versions:

• For mobile browsers:

• iOS 11 and later.
• Android 5.0 and later.

• For computer browsers, use the following recommended versions:

Integrate the SDK resource package via CDN or npm.

Via CDN resources: Use the <script> tag in the HTML file.

<script src="https://sdk.marmot-cloud.com/package/ams-checkout/1.13.0/dist/umd/ams-checkout.min.js"></script>

Via npm: Input the install command in the command line.

npm install @alipay/ams-checkout

Instantiate the SDK

Create the SDK instance by using AMSEasyPayand specify basic configurations. Configuration object includes the following parameters:

The following sample code shows how to obtain the browser language:

let language = navigator.language || navigator.userLanguage;language = language.replace("-", "_"); // Replace "-" with "_"

The following sample code shows how to instantiate the SDK by using npm:

import { AMSEasyPay } from '@alipay/ams-checkout' // Manage the packageconst checkoutApp = new AMSEasyPay({ environment: "sandbox", locale: "en_US", analytics: { enabled: true }, onLog: ({code, message})=>{}, onClose:()=>{ // Close the half-screen popup }, onEventCallback: ({code, message})=>{},});

The following sample code shows how to instantiate the SDK by using CDN:

const checkoutApp = new window.AMSEasyPay({ environment: "sandbox", locale: "en_US", analytics: { enabled: true }, onLog: ({code, message})=>{}, onClose:()=>{ // Close the half-screen popup }, onEventCallback: ({code, message})=>{},});

Invoke the SDK

Use createComponent in the instance object to create a payment component:

The following sample code shows how to render the component:

async function create(sessionData) { await checkoutApp.createComponent({ sessionData: sessionData, appearance:{ showLoading: true, // Set as true by default to enable the default loading pattern. } });}

Call unmount to free SDK component resources in the following situations:

• When the buyer switches views to exit the checkout page, free the component resources created in the createPaymentSession API.
• When the buyer initiates multiple payments, free the component resources created in the previous createPaymentSession API.

// Free SDK component resourcescheckoutApp.unmount();

Common questions

Q: What can I do when I receive the SDK_CREATEPAYMENT_PARAMETER_ERROR?

A: When you receive this event code, check if the sessionData passed in is correct and complete.

Q: What can I do when I receive the SDK_PAYMENT_ERROR or a rendering view error occurred?

A: Check the network request for any exceptions during interface initialization, such as network timeouts. Ensure that the environment for creating payment session request is consistent with the environment used for SDK instantiation. Check whether the parameters in the createPaymentSession API are passed correctly. If the interface exceptions persist, feel free to contact us for further troubleshooting.

Step 3: Obtain authorization or payment result Server-side

For the first-time payment, you can obtain both the authorization and payment results, while for subsequent payments, only the payment result is available.

You can obtain the authorization or payment result by one of the following methods:

• Receive the asynchronous notification
• Inquire about the result

Receive the asynchronous notification

{ "accessToken": "281012345678901234567890123456****", "authState": "AUTHSTATE_SAMPLE_1234567890", "authorizationNotifyType": "TOKEN_CREATED", "userLoginId": "852-52***184", "result": { "resultCode": "SUCCESS", "resultMessage": "success.", "resultStatus": "S" }}

Common questions

Q: When will the payment result notification be sent?

A: It depends on whether the payment is completed:

• If the payment is successfully completed, Antom will usually send you an asynchronous notification within 3 to 5 seconds. For some payment methods like OTC, the notification might take a bit longer.
• If the payment is not completed, Antom needs to close the order first before sending an asynchronous notification. The time it takes for different payment methods to close the order varies, usually defaulting to 14 minutes.

Q: Will the asynchronous notification be re-sent?

A: Yes, the asynchronous notification will be re-sent automatically within 24 hours for the following cases:

• If you didn't receive the asynchronous notification due to network reasons.
• If you receive an asynchronous notification fromAntom, but you didn't make a response to the notification in thesample codeformat of Process the notification.

The notification can be resent up to 8 times or until a correct response is received to terminate delivery. The sending intervals are as follows: 0 minutes, 2 minutes, 10 minutes, 10 minutes, 1 hour, 2 hours, 6 hours, and 15 hours.

Q: When responding to asynchronous notification, do I need to add a digital signature?

A: If you receive an asynchronous notification from Antom, you are required to return the response in the sample codeformat of Process the notification, but you do not need to countersign the response.

Q: What are the key parameters in the payment result notification that I need to use?

A: Pay attention to the following key parameters:

• result: indicates the payment result of the order.
• paymentRequestId: indicates the payment request number you generated for consult, cancel, and reconciliation.
• paymentId: indicates the payment order number generated byAntom used for refund and reconciliation.
• paymentAmount: indicates the payment amount.

Q: What are the key parameters in the authorization result notification that I need to use?

A: Pay attention to the following key parameters:

• result: represents the payment result of the order.
• authState: the vaulting request ID generated by the merchant.
• accessToken: the auto debit ID generated by Antom used for subsequent payment.
• userLoginId: the user's desensitized account number.

Inquire about the payment result

You can call the inquiryPayment API to initiate a query on the result of an order.

The parameter is not a full set of parameters, please refer to the inquiryPayment API for full set of parameters and additional requirements for certain payment methods.

The following sample code shows how to call the inquiryPayment API:

AlipayClient defaultAlipayClient = new DefaultAlipayClient(EndPointConstants.SG, merchantPrivateKey, alipayPublicKey);AlipayPayQueryRequest alipayPayQueryRequest = new AlipayPayQueryRequest();alipayPayQueryRequest.setClientId(CLIENT_ID);alipayPayQueryRequest.setPath("/ams/sandbox/api/v1/payments/inquiryPayment");AlipayPayQueryResponse alipayPayQueryResponse; try { alipayPayQueryResponse = defaultAlipayClient.execute(alipayPayQueryRequest); } catch (AlipayApiException e) { String errorMsg = e.getMessage(); // handle error condition }

The following code shows a sample of the request message:

{ "paymentRequestId": "2019060811401080010018882020035****"}

The following code shows a sample of the response message:

{ "result": { "resultCode": "SUCCESS", "resultStatus": "S", "resultMessage": "Success" }, "paymentStatus": "SUCCESS", "paymentRequestId": "pay_1089760038715669_10277574507****", "paymentId": "2019060811401080010018882020035****", "paymentAmount": { "value": "4200", "currency": "SGD" }, "paymentCreateTime": "2019-06-01T12:01:01+08:30", "paymentTime": "2019-06-01T12:01:01+08:30", "transactions": null}

Common questions

Q: How often should I call the inquiryPayment API?

A: Call the inquiryPayment API constantly with an interval of 2 seconds until the final payment result is obtained or an asynchronous payment result notification is received.

Q: What are the key parameters in the notification that I need to use?

A: Pay attention to these key parameters:

• result: represents the result of thisinquiryPayment API call, the result of the order needs to be judged according to paymentStatus:

• SUCCESS and FAIL represent the final result.
• PROCESSING represents the processing.

• paymentAmount: indicates the payment amount.

Complete sample code for using the client SDK:

// Step 1: Instantiate the SDKconst checkoutApp = new window.AMSCashierPayment({ environment: "sandbox", locale: "en_US", onLog: ({code, message}) => {}, onEventCallback: ({code, message}) => {},});// Handle payment button events.document .querySelector("#your form id") .addEventListener("submit", handleSubmit);async function handleSubmit() { // Step 2: The server calls createPaymentSession API to obtain paymentSessionData. async function getPaymentSessionData() { const url = "Fill in the server address"; const config = { // Fill in the request configuration. }; const response = await fetch(url, config); // Obtain the value of the paymentSessionData parameter in the response. const { paymentSessionData } = await response.json(); return paymentSessionData; } const paymentSessionData = await getPaymentSessionData(); // Step 3: Create rendering components. await checkoutApp.createComponent({ sessionData: paymentSessionData, appearance:{ showLoading: true, // Default is true to allow the configuration whether to display a loading animation. }, });}

Sample codes for customized loading animation

The card payment scenario supports configuration of custom loading animations:

1. Configure showLoading to false when rendering the component.
2. Render a customized loading animation on the current page when the createComponent function is called.
3. Listen to the onEventCallback event.

1. Show your custom loading animation when you receive the SDK_START_OF_LOADING event code.
2. End your custom loading animation when you receive the SDK_END_OF_LOADING event code.

async function create(sessionData) { await checkoutApp.createComponent({ sessionData: sessionData, appearance:{ showLoading: false, // Default is true to allow the configuration whether to display a loading animation. }, });}

You might see two types of event codes:

• Status codes: Returned by onEventCallback during the component's runtime lifecycle.
• Error codes: Returned by onEventCallback or onError during the component initialization phase.