API ReferenceSign In

eWallet Checkout Methods

Last updated 05/06/2021

Xendit supports various eWallet checkout methods from eWallets providers to suit our merchants’ use cases. This section explains the type of checkouts available and how each eWallet could differ from another in the methods they provide.

One time payments

One time payments refer to guest checkouts where end users are required to perform payment authorization (via OTPs or PINs) each time they intend to pay for their purchases. This is very commonly used for payment flows which allow end users to quickly complete their payment without requiring sign ups or providing personal information. There are 2 types of one time payment flows which are provided by eWallet providers - payment via redirection and payment without redirection.

Existing eWallet channels and available payment flows

ChannelIs redirect required?desktop_web_ checkout_urlmobile_web_ checkout_urlmobile_ deeplink_ checkout_urlqr_checkout_ string
OVO❌ (OVO uses app push notifications)

Tokenized payments

Tokenized payments refer to a checkout process designed to maximize payment success rates by reducing the number of required user authentication per transaction. First, end users will be redirected to perform a one time account linking authorization with PIN and OTP. This is followed by a payment step either via auto debit or redirection for PIN (without SMS OTP) to complete the transaction. Subsequent payments made by the same end user will only require the payment step as the account linking token can be reused, hence reducing the authentication to only PIN or no authentication at all.

There are 2 types of tokenized payment step which are provided by Xendit according to different eWallet providers we support - auto debit payments and payment via redirection for PIN.

Existing tokenized eWallet channels and available payment flows

Is redirect and PIN required?
Auto debit

Types of redirection urls available

eWallet providers supports redirection urls for different device types. To provide our merchants with full flexibility, we return in our API ewallet charge request with the following parameters.

It is recommended that merchants pick one of the follow for each device type based on what is available from each eWallet provider

  • Device with stand-alone screens : desktop_web_checkout_url OR qr_checkout_string
  • Mobile devices : mobile_web_checkout_url  OR mobile_deeplink_checkout_url

*If a redirection url works for both desktop and mobile devices, Xendit will duplicate the url in both desktop_web_checkout_url and mobile_web_checkout_url parameter.

TypeUse case
desktop_web_checkout_urleWallet issuer generated URL for web checkout on devices with a stand-alone screen
mobile_web_checkout_urleWallet issuer generated URL for web checkout on mobile devices
mobile_deeplink_checkout_urleWallet issuer generated URL for deeplink checkout on mobile devices (jumps directly into eWallet app for payment confirmation)
qr_checkout_stringeWallet issuer generated qr string for checkout usually on devices with a stand-alone screen