Fantap Hub (FantapHub)
The federation layer for the platform's independent installations. It identifies which installation each card belongs to, sends the purchase to that installation and coordinates settlement between members.
- Domain
- Federation and card payment routing
- Target customers
- Organizations that are members of the Fantap network (universities, partner companies) with their own independent installation
- Main capabilities
- registration of independent installations, card ownership detection and purchase routing, shared store catalog, nightly inter-installation settlement
Fantap Hub is a federation and routing layer rather than an ordinary multi-tenant system. Each organization under contract with Fantap (such as a university or an automaker) has a fully independent, separate installation of the entire platform on its own infrastructure, with its own database, accounting and cards. Fantap Hub does not merge any of these installations into a shared database. Instead, it registers each installation as a “Federated Instance” and is responsible for three tasks: making the stores that are members of the Fantap network available to all of these installations, identifying which installation each card belongs to and routing the purchase request to it, and coordinating financial settlement between Fantap and each member installation.
The problem this service solves is the following. When a student buys at a store in the Fantap network with their university card (issued in the university's installation), the purchase must be deducted from the balance of that university card, not from a central Fantap wallet. Fantap Hub takes the card number, determines which installation the card belongs to based on the card number range or its hashed fingerprint, sends the purchase request to that installation over a secure service-to-service connection, and returns the result. The debt arising from these purchases is totaled every night and settled between Fantap and that installation as an accounting voucher.
Key capabilities
Registration and management of member installations
Each installation (university, business partner) is registered with its own service address, active or inactive status and security credential
Card ownership detection and purchase routing
Matching the card number against the issuer range of each installation, and where needed the hashed fingerprint of the card, to send the purchase request to the installation that owns the card
Federated in-person purchase (POS)
Recording, final confirmation and status inquiry of a purchase at a Fantap store with a card issued in another installation
Fantap store catalog
A live list of the stores that are members of the Fantap network, which each installation can display to its own users, with nightly synchronization of the parent store and branch structure to each installation
Nightly settlement between Fantap and each installation
Automatic totaling of the debt from each night's purchases and posting of the settlement voucher in accounting, without daily manual intervention
Connection health and security control
Periodic monitoring of the availability of each installation, service-to-service authentication (OAuth2) and request signing to prevent forgery and replay
Federated online payment session (CPG)
The ability to complete an online purchase from a Fantap store with the card of a user defined in another installation
Business value
Fantap Hub allows Fantap to build a shared merchant network and share it among several organizational customers (universities, companies), without requiring those customers to combine their financial or user data in a shared database. Each organization remains the full owner of its own data, accounting and cards, and Fantap Hub only routes purchase traffic between these independent installations. This model removes the security and legal risk of merging data between organizations and, at the same time, gives everyone the advantage of a larger store network.
What sets it apart
- A true federation model in place of multi-tenancy: no organization's financial or user data is placed in a shared database
- Purchase routing based on actual card ownership, with no central intermediary wallet
- Automatic nightly settlement between several independent installations without a daily manual process
See this module on demo data
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.