Setting up Airwallex Checkout isn't just about getting the payment page to load. Customers should clearly understand what they're purchasing, the amount and currency involved, whether it's a one-time or recurring charge—before paying—and after payment, they should know how their order will be confirmed, when delivery will occur, and how to access support. This guide outlines a customer-focused checklist based on your actual products or services, without guaranteeing payment success, platform approval, or business outcomes.
First, select the Checkout mode that matches your actual billing method.
Airwallex officially describes Checkout as the final step in the customer purchase process, where customers confirm their purchase, select a billing method, and submit payment information. Before beginning configuration, clarify internally whether this transaction is a one-time payment, a subscription, or simply storing payment details for future use; the actual business billing model should align with the page display, order descriptions, and subsequent notifications.
Do not present one-time services as auto-renewing, nor use vague product names to conceal recurring charges. If the service includes trials, appointments, installment plans, or subscriptions, the conditions for billing, billing cycles, cancellation options, and customer notifications must be jointly confirmed by business, customer service, and technical teams, then implemented according to the current account features and official guidelines.
Products, prices, currencies, and quantities should be clearly understandable at a glance for customers.
Each checkout link or session should correspond to a genuine, deliverable product or service. Names should avoid internal codes, and prices should align with those on the official website or quotation sheet. Currency, quantity, taxes, shipping fees, or any potential recurring charges must be clearly disclosed before the customer pays. Presenting only an amount without explaining what it includes makes it difficult for customers to determine whether they have made the right choice.
When the same service offers different packages, regional versions, or service durations simultaneously, establish clear product descriptions and pricing logic for each, and assign a responsible person to maintain updates. Before launch, have someone not involved in development review the customer journey: can they clearly state what they are purchasing, how much they will pay, and when they will receive the service? If not, clarify the information before enabling payment.
Choose between hosted pages, embedded components, or custom integration based on technical capabilities
Airwallex currently offers integration options including Hosted Billing Checkout, embedded Elements, native APIs, and mobile SDKs. Hosted pages are typically hosted by Airwallex—after the server creates a Checkout object, customers are redirected to a dedicated link. In contrast, embedded components or custom interfaces require the team to handle more work related to page development, testing, and maintenance. The choice should be based on the team's actual engineering capabilities and ongoing maintenance responsibilities.
Regardless of the access method used, merchants must not delegate customer information display and after-sales responsibilities to the technical infrastructure itself. It should be clearly defined who is responsible for maintaining product descriptions, policy links, customer service emails, and error notifications. After any page redirection, embedding, or return link changes, both mobile and desktop versions must be rechecked to prevent customers from landing on expired pages or being unable to contact the business entity after completing a payment.
Write delivery, refund, and cancellation policies as actionable commitments
Physical products, digital content, appointment-based services, and subscriptions each face different delivery expectations. Physical goods should clearly state shipping availability and estimated timelines; digital services should explain activation or delivery methods; appointments should specify rescheduling and cancellation windows; and subscriptions must make customers understand the billing frequency and how to stop future charges. All timeframes and conditions should stem from processes that the team can genuinely execute.
Refund or cancellation policies can be placed on a separate page, but customers should be able to find them before checkout, and they must not conflict with product pages, checkout pages, confirmation emails, or customer service responses. Avoid copying generic clauses from other industries, and do not present the processing times that payment channels may allow as guaranteed deposit dates by your company. Instead, it's more helpful to clearly state when your business processes requests, what order information customers need to provide, and how they can follow up.
The payment success page must inform the customer what will happen next.
Payment completion is not the end of the customer journey. The success page or follow-up notification should clearly state where the order confirmation will be sent, how delivery or activation is expected to occur, whether customers can update their information, and which support channel to contact if issues arise. If additional steps are required—such as registration, document upload, or scheduling—these should be explained with clear purposes, access points, and deadlines, rather than simply displaying a generic "payment successful" message.
The notification content after payment should match the actual backend status. Avoid stating "shipped" or "service activated" before fulfillment is complete, and do not show customers non-existent order numbers due to internal automation failures. Teams may retain records of orders, customer communications, and actual delivery for normal customer service and troubleshooting purposes, rather than fabricating false explanations afterward.
Collect only the information necessary for performance and protect customer data
When designing the purchase process, carefully evaluate each form field to ensure it genuinely supports delivery, taxation, or customer support. Data such as customer name, contact information, or address should be collected through appropriate standard capabilities provided by the current product, and customers should be informed about how this data will be used. Do not collect privacy-related information unrelated to the order solely for internal filtering convenience.
Do not request customers to submit passwords, verification codes, complete bank card details, identity document images, or other sensitive information in product notes, custom instructions, or customer service chats. If your business genuinely requires handling regulated information, first obtain confirmation from compliance and security officers regarding legal basis, storage methods, access scope, and retention periods, and follow the current requirements specified within the account and official documentation.
Complete an end-to-end customer perspective review before going live
Before going live, sequentially verify the following using approved testing environments or procedures: whether links are accessible, whether product names and amounts are correct, whether currency is clearly indicated, whether policies are accessible, whether customer support is functional, and whether post-payment pages and notifications are accurate. During testing, use test data or authorized internal data; do not use customers' actual payment information for temporary experiments.
Record the date, link, responsible person, page version, and any issues found during this review. Going forward, whenever there are changes to pricing, packages, delivery methods, policies, support email, or technical integration, the same review process must be repeated. Clear checkout information cannot replace actual fulfillment and compliant operations, but it can help customers make informed decisions and reduce avoidable communication costs.
Official Information and Frequently Asked Questions
The final verification date of this document is September 2026. Platform rules, available regions, document requirements, fees, and review processes may be subject to change; please refer only to Airwallex Official Checkout Feature Description Please refer to the notifications within your account, and only submit genuine, valid documents that belong to your company.
Can Airwallex Checkout be used for one-time payments and subscriptions?
Airwallex's current official documentation lists payment, subscription, and setup as available modes. The applicable modes and specific configurations depend on the business account, region, and current product interface, and should align with actual billing methods and customer instructions.
After launching the hosted payment page, what else do merchants need to maintain?
Accurate product descriptions, pricing, currency, delivery and refund policies, customer support, and post-payment notifications must still be maintained. While hosted pages can reduce some development work, they do not replace the merchant's responsibility for sales content and after-sales service.
What information should be included on a successful payment page?
Customers should be informed at least about how the order is confirmed, the next steps for delivery or activation, expected timelines, and available support channels. The information provided must reflect the actual order status and cannot substitute unfulfilled commitments for real progress.
Can we directly test using the customer's bank card before going live?
It is not recommended to collect or use customers' actual payment information for temporary testing. Instead, prioritize using the platform's supported test environment, test data, or authorized internal processes, and complete testing in accordance with current official documentation.