Payment Methods

Fortumo’s platform provides merchants with access to two different payment methods:

Carrier billing: payments are deducted from the user’s SIM card balance or added to their next monthly phone bill

Mobile wallets: payments are deducted from the user’s mobile wallet account balance

Continue reading to find out which connections are supported for both payment methods.

Carrier billing

Carrier billing payments can be collected by integrating one of the following Fortumo products: Unified SDK, Payments API & Web SDK.

The checkout flow for carrier billing payments is hosted end-to-end by Fortumo and uses one of three possible payment authorisation types:

  • Header Enrichment: the user’s phone number is detected through their mobile data connection and the user clicks “Confirm”, after which the payment is confirmed

  • PIN confirmation: the user is sent an SMS with a PIN code which they have to enter into the checkout window, after which the payment is confirmed

  • Premium SMS: the user sends a pre-defined SMS to a short code (4 or 5 digit phone number) during the checkout, after which the payment is confirmed

Integrating any of Fortumo’s products for carrier billing payments gives global access to collecting payments from customers of all mobile operators connected to our platform:

Mobile wallets

Mobile wallet payments can be collected by integrating Fortumo’s Unified SDK.

The checkout flow for mobile wallet payments is partially hosted by Fortumo, for the payment confirmation the user is directed to their wallet account.

In order to confirm their purchase, mobile wallets provide their user with one of the following flows:

  • QR code confirmation: user is redirected to the page on the desktop that shows QR code that is needed to be scanned in the mobile wallet app. As soon as payment is confirmed in the wallet app by pressing the “Confirm” button, the user is redirected back to the merchant
  • Web-based confirmation: user is redirected to the web view of the digital wallet where the user logs in to the wallet account and confirms the payment. After a successful confirmation, the user is redirected back to the merchant
  • In-app confirmation: on mobile devices, the user is redirected to the mobile wallet app either through a deep link or by clicking a notification sent by the app. After a successful confirmation, the user is redirected back to the merchant

Unified SDK handles the different payment flows used by each wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to a specific wallet.

Learn more about the USDK integration for wallet payment methods here.

Overview of mobile wallet capabilities

Definition explanations:

  • Subscriptions: the wallet user can start a recurring payment which is deducted at specified intervals without having to confirm repeat purchases separately
  • Authorisation type: the authorisation method used by Unified SDK to authorise the end-user with the wallet. Merchants do not need to add the authorisation type manually as Unified SDK detects it automatically. The authorisation types used by wallets are: remote authorisation (remote_auth), redirect authorization (redirect_auth), redirect auth on payment (redirect_auth_on_payment).
  • Refund API: refunds can be done automatically to the user through the Refund API; in case the wallet does not support Refund API, refunds have to be done manually
  • Desktop QR code payment: payment flow where the user scans a QR code with their wallet application to authorize a payment done on a desktop device
Wallet Subscriptions Authorisation type Refund API Desktop QR code payment
OVO no remote_auth no no
ShopeePay yes redirect_auth, redirect_auth_on_payment no (one time payments) yes (subscription payments) yes
Dana yes redirect_auth, redirect_auth_on_payment yes no
GoPay yes redirect_auth, redirect_auth_on_payment yes no
PayMaya Yes redirect_auth, redirect_auth_on_payment yes yes
GCash Yes redirect_auth, redirect_auth_on_payment yes yes
TrueMoney Yes redirect_auth, redirect_auth_on_payment yes yes

Bellow you can find additional details on the mobile wallets that are available by integrating Unified SDK:

OVO (Indonesia)

OVO is a mobile wallet in Indonesia with approximately 115 million registered accounts. The wallet was launched in 2017. For more information, visit https://www.ovo.id/.

Unified SDK handles the payment flow used by OVO wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the OVO wallet.

  • Subscriptions supported: no
  • Refund API: no

Payment flow:

Ovo

  1. user chooses to pay with OVO
  2. user enters phone number
  3. user receives OVO app notification and clicks on it to open OVO app
  4. user reviews the details of the payment
  5. user confirms the payment
  6. user is redirected back to the merchant

Dana (Indonesia)

Dana is a mobile wallet in Indonesia with approximately 30 million registered accounts. The wallet was launched in 2018. For more information, visit https://www.dana.id/.

Unified SDK handles the payment flow used by Dana wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the Dana wallet.

  • Subscriptions supported: yes
  • Refund API: yes

Payment flow for subscriptions and one-time payments:

Dana Dana

  1. user chooses to pay with Dana
  2. user is redirected to DANA website
  3. user logs in to the wallet by entering phone number and password
  4. user reviews the details of the payment
  5. user confirms the payment
  6. user is redirected back to the merchant

GoPay (Indonesia)

GoPay is a wallet in Indonesia with approximately 25 million registered accounts. The wallet was launched in 2016. For more information, visit https://www.gojek.com/gopay/.

Unified SDK handles the payment flow used by GoPay wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the GoPay wallet.

  • Subscriptions supported: yes
  • Refund API: yes

Payment flow for subscriptions and one-time payments (on mobile devices):

Gopay

  1. user chooses to pay with GoPay
  2. user enters phone number
  3. user is redirected to GoJek (GoPay) application
  4. user checks payment details
  5. user enters PIN for verification and authorisation of the payment that was sent to the mobile of the user
  6. user is redirected back to the merchant

Payment flow for subscriptions and one-time payments (on desktop):

Gopay1

  1. users chooses to pay with GoPay
  2. user enters phone number
  3. user is redirected to the QR code scanning page
  4. user is scanning QR code with the wallet application
  5. user reviews the details of the payment
  6. user confirms the payment
  7. user is redirected back to the merchant

ShopeePay (Indonesia)

ShopeePay is a mobile wallet in Indonesia with approximately 56 million registered accounts. The wallet was launched in 2015. For more information, visit https://shopeepay.co.id.

Unified SDK handles the payment flow used by ShopeePay wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the ShopeePay wallet.

  • Subscriptions supported: no
  • Refund API: yes

Payment flow for one-time payments (on mobile devices):

ShopeePay

  1. user chooses to pay with ShopeePay
  2. user inputs phone number
  3. user is redirected to ShopeePay application
  4. user reviews the details of the payment
  5. user enters PIN for verification and authorisation of the payment
  6. user is redirected back to the merchant

Payment flow for one-time payments (on desktop):

ShopeePay1

  1. users chooses to pay with ShopeePay
  2. user inputs phone number
  3. user is redirected to the QR code scanning page
  4. user is scanning QR code with the wallet application
  5. user checks payment details
  6. user confirms the payment
  7. user is redirected back to merchant

PayMaya (Philippines)

PayMaya is a mobile wallet in the Philippines with approximately 12 million registered accounts. The wallet was launched in 2016. For more information, visit https://www.paymaya.com/.

Unified SDK handles the payment flow used by PayMaya wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the PayMaya wallet.

  • Payment types supported: one time payment and subscription
  • Refund API: yes

Payment flow for subscriptions and one-time payments (on mobile devices): PayMaya

  1. user chooses to pay with PayMaya
  2. user is redirected to PayMaya page
  3. user logs in to the wallet by entering phone number and pin
  4. user reviews the details of the payment
  5. user confirms the payment
  6. user is redirected back to the merchant

Payment flow for subscriptions and one-time payments (on desktop): PayMaya1

  1. users chooses to pay with PayMaya
  2. user is redirected to the QR code scanning page
  3. user is scanning QR code with the wallet application
  4. user reviews the details of the payment
  5. user confirms the payment
  6. user is redirected back to the merchant

GCash (Philippines)

GCash is a mobile wallet in the Philippines with approximately 20 million registered accounts. The wallet was launched in 2004. For more information, visit https://www.gcash.com/.

Unified SDK handles the payment flow used by GCash wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the GCash wallet.

  • Subscriptions supported: yes
  • Refund API: yes

Payment flow for subscriptions and one-time payments (on mobile devices): Gcash

  1. user chooses to pay with GCash
  2. user inputs phone number
  3. user is redirected to GCash application
  4. user reviews details of the payment
  5. user confirms the payment by entering PIN received by SMS
  6. user is redirected back to the merchant

Payment flow for subscriptions and one-time payments (on desktop): Gcash1

  1. users chooses to pay with GCash
  2. user inputs phone number
  3. user is redirected to the QR code scanning page
  4. user scans QR code with the wallet application
  5. user reviews the details of the payment
  6. user confirms the payment
  7. user is redirected back to the merchant

TrueMoney (Thailand)

TrueMoney is a mobile wallet in Thailand with approximately 14 million registered accounts. The wallet was launched in 2015. For more information, visit https://www.truemoney.com.

Unified SDK handles the payment flow used by TrueMoney wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the TrueMoney wallet.

  • Subscriptions supported: yes
  • Refund API: yes

Payment flow for subscriptions and one-time payments (on mobile devices):

truemoney

  1. user chooses to pay with TrueMoney
  2. user inputs phone number
  3. user is redirected to TrueMoney application
  4. user reviews the details of the payment
  5. user confirms and authorises payment
  6. user is redirected back to the merchant

Payment flow for subscriptions and one-time payments (on desktop): truemoney1

  1. user chooses to pay with TrueMoney
  2. user inputs phone number
  3. user is redirected to the QR code scanning page
  4. user is scanning QR code with the wallet application
  5. user reviews the details of the payment
  6. user confirms the payment
  7. user is redirected back to the merchant

Rabbit Line Pay (Thailand)

Rabbit LINE Pay is a mobile wallet in Thailand with approximately 8 million users. The wallet was launched in 2016. For more information, visit https://line.me/en/pay

Unified SDK handles the payment flow used by Rabbit Line Pay wallet on behalf of the merchant. Only the “channel_code” payload parameter needs to be changed in the checkout window to direct the user to the Rabbit Line Pay wallet.

  • Subscriptions supported: yes
  • Refund API: yes
  • Desktop QR code payment: yes

Payment flow for subscriptions and one-time payments (on mobile devices): PayMaya

  1. user chooses to pay with Rabbit Line Pay
  2. user is redirected to Rabbit Line Pay page
  3. user logs in to the wallet by entering PIN code
  4. user reviews the details of the payment
  5. user confirms the payment
  6. user is redirected back to the merchant

Payment flow for subscriptions and one-time payments (on desktop): truemoney1

  1. user chooses to pay with Rabbit Line Pay
  2. user inputs login or scans QR
  3. user is scanning QR code with the wallet application or enters login credentials
  4. user is redirected to mobile app
  5. user reviews the details of the payment
  6. user confirms the payment
  7. user is redirected back to the merchant
Help us improve our Merchants Portal. Was this article helpful?