Checkout generates a secure, Finmo-hosted payment page that facilitates the collection of payments via local methods such as bank transfers, cards, direct debit, and wallets swiftly. It functions seamlessly across devices, potentially boosting your conversion rates.

Checkout simplifies the process of creating an optimal payment experience:

• Designed to minimize friction

• Mobile-ready

• Supports multiple global payment methods

• White Label – Customize by adding logo, support details, and payment instructions specific to the payment method

• Customizable buttons and background color

Optimizing the Checkout Experience

Step 1: Determine the time frame for the customers to complete the payment and set an expiration date-time. Typically, if the payment method supports expiration, it will share the same date-time. For example, PayID in Australia usually expires within 24 hours.

Step 2: Decide on offering specific payment methods, an entire set, or just a category to the customer. This can be managed using include & exclude options. Categories refer to types of payment methods like Bank, E-Wallet, Card, etc.

Step 3: Choose how the Checkout completion should work, i.e., if the user be redirected to a single URL or multiple URLs. The field called REDIRECT_URL stands for a common redirect URL. The status message can be handled based on the parameters provided in the REDIRECT_URL.

Alternatively, four different or identical URLs can also be provided under ADVANCED_REDIRECT_URL, allowing the capability to display the appropriate status message based on events on the checkout page.

Step 4: Customers can be notified about the checkout link via email or SMS. Finmo will send them the link to pay the invoice amount through the checkout link.

Checkout Status & Webhook Notifications

Finmo will notify about any status updates of the Checkout object via webhooks. Static webhook listener URL can also be configured via the dashboard or a dynamic webhook URL can be sent in the Create Checkout request.

• CHECKOUT_CREATED: Triggered when a Checkout page is created. The Checkout status will be CREATED.

• PAYIN_CREATED: Triggered once the customer selects the payment method on the Checkout page and submits. This webhook includes the CHECKOUT_ID to link the payment to the customer. The Checkout status remains CREATED, while the payment status updates to PENDING.

• CHECKOUT_COMPLETED and PAYIN_COMPLETED: Triggered once the consumer makes the payment. Both the Checkout and Payment status updates to COMPLETED.

• CHECKOUT_EXPIRED and PAYIN_EXPIRED: Triggered if the Checkout page expires. Both the Checkout and payment status updates to EXPIRED.

• CHECKOUT_CANCELLED: Triggered if the consumer cancels the Checkout page. If the payment method is_cancellable = true, the payment will also be cancelled. Both the Checkout and payment status updates to CANCELLED.

Creating a Checkout Page

Create a checkout page that builds a Payin. This method can be used without requiring PCI certification.