Deferred Online ODA Mode

The Deferred Online ODA solution enables offline data authentication upon tapping into a station and verification of an account status from the issuer at a later time. The solution fits transit scenarios with high ridership due to the extremely short authentication time.

introduction

Appalicability

Merchant side: Acquirers should have already obtained the POS acquiring license and support POS business.

Transit terminals should be certified on L2 & L3.


Scenarios

Public transit systems, such as buses, metros, ferries, BRT, etc.

Payment Flow

Single Fare Mode:

Deferred 1.png

Step 1: The cardholder taps their card upon entry into the station. The transit terminal performs a series of offline checks, and if all the checks are successful, the cardholder will be allowed to travel.

Step 2: The trip info is uploaded to the transit backend system.

Step 3-5: The transit backend system / acquirer submits a purchase / fixed-amount authorization request through UnionPay to the issuer.

Step 6-9: The issuer returns an authorization response. In the event of a decline response, the cardholder is added to the deny list.


Aggregated Fare Mode:

Deferred 2.png

Step 1: The cardholder taps their card upon entry into the station. The transit terminal performs a series of offline checks, and if all the checks are successful, the cardholder will be allowed to travel.

Step 2: The trip info is uploaded to the transit backend system.

Step 3-5: In the event of no active pre-auth in the system, the transit backend system / acquirer submits a pre-auth / estimated-amount authorization request through UnionPay to the issuer.

Step 6-9: The issuer returns an authorization response. In the event of a decline response, the cardholder is added to the deny list.

Deferred 3.png



Step 1: The cardholder taps their card upon entry into the station. The transit terminal performs a series of offline checks, and if all the checks are successful, the cardholder will be allowed to travel.

Step 2: The trip info is uploaded to the transit backend system.

Step 3-5: The transit backend system judges whether the presentment threshold is reached. If so, a pre-auth completion advisement / fixed-amount authorization request will be submitted.


Use Case

1 . Bus

2 . Metro

Features

 Ideal for the following scenarios:

 1.Instable internet connection

 2.Average or low fare (e.g. metros)

 3.High ridership


  • Contact Us
  • If you have any further questions, please register and submit order in your user center.