Enabling Card On an Existing Store of Value

A common use case for Eclipse is to use the card management functionality with auth-forward to a tenants own walleting system or account/store of value. This allows for a tenant to issue scheme cards to their customers and have any purchases or cash withdrawals on those cards strike the tenants store of value in real time. The exact implementation details depends on the capabilities of the tenants walleting system to expose Eclipse-defined API's or alternatively for Eclipse to do a specific wallet-type implementation to call existing API's on the tenants walleting system.

Tenants SoV Exposes Eclipse-Defined API's

This scenario can be catered for OOTB with configuration:

1. Set up Eclipse as a card provider for the tenant (details outside of the scope of this document). This allows the tenant to create wallets on Eclipse and Cards and utilise all of the card management APIS like PON set, status changes etc. The wallets provisioning on Eclipse would act as a placeholder for the Tenants actual wallet on their system.
2. Tenant creates a wallet on Eclipse to mirror their own customers wallet. E.g. they create wallet 1234 on Eclipse and on their own wallet, set a mapping indicating this is wallet 1234 on Eclipse.
3. Tenant provisions a virtual or physical card to that wallet and gives it to their customer
4. The wallet type on Eclipse has preDebitTenantAuthUrl and preReservationTenantAuthUrl set. These result in all reservations and transfers on the eclipse wallet to be forwarded to this URL on the tenant wallet system. The URL receives a POST of JSON data of all the details of the reservation/transfer (in a defined Eclipse format) when card transactions take place. Assuming the tenant responds with a 200 OK, Eclipse authorises the card transaction. Any other response code and the reservation/transfer is denied. Error details can also be included in the response payload
5. All settlement and other processes happen as per usual. Typically the tenant will keep a float in the bin sponsor banks card settlement account for inter bank and scheme settlement.

Eclipse Integrates to Tenants SoV

This scenario can be catered for OOTB development of a wallet-type implementation on Eclipse and then with configuration:

1. Set up Eclipse as a card provider for the tenant (details outside of the scope of this document). This allows the tenant to create wallets on Eclipse and Cards and utilise all of the card management APIS like PON set, status changes etc. The wallets provisioning on Eclipse would act as a placeholder for the Tenants actual wallet on their system.
2. Tenant creates a wallet on Eclipse to mirror their own customers wallet. E.g. they create wallet 1234 on Eclipse and on their own wallet, set a mapping indicating this is wallet 1234 on Eclipse.
3. Tenant provisions a virtual or physical card to that wallet and gives it to their customer
4. The wallet type on Eclipse is a custom implementation that calls SoV defined API's for reservations and transfers. This is an integration task so thet the Eclipse wallet type delegates to an external SoV to do the actual balance checks and ledger movements so that the tenants SoV is the master. Only if the transaction succeeds on the tenants SoV will Eclipse proceed with the card transaction.
5. All settlement and other processes happen as per usual. Typically the tenant will keep a float in the bin sponsor banks card settlement account for inter bank and scheme settlement.