The need to create a 3 level program hierarchy is quite rare.

In the Hyperwallet system, a 3 level program hierarchy is created in order to support this structure. In this case, the top level parent program is referred to as a Wallet Issuer (WI), each sub program on the second level of the hierarchy is referred to as an Issuing Merchant (IM), while each child program on the third level of the hierarchy - the level that serves the payee - is referred to as an Issuing Store (IS).

MULTIPLE PROGRAMS WITHIN A 3 LEVEL PROGRAM HIERARCHY EXAMPLE

COMPANY C is a global marketplace that offers both ridesharing and food delivery. In order to accommodate this unique organizational structure, Hyperwallet enables a 3 level program hierarchy for COMPANY C that includes multiple programs on each level. The first program hierarchy level is defined by the organization structure - on this level there are 2 sub programs: one is configured based on the global ridesharing payout requirements and the other is configured based on the global food delivery payout requirement. The third, child level of the hierarchy features programs configured to meet the unique payout requirements of each geography.

In some exceptional cases a marketplace or enterprise client may require a 3 level program hierarchy in order to account for unique organizational structures or specific payout use cases. These could include:

• A combination of organizational structure and payee types: For example, you have multiple lines of businesses on your platform, and each line of business has multiple payee groups (see the following example concerning the fictional ridesharing client, COMPANY C for more context).

• A combination of funding and reconciliation needs and organizational structure: For example, if your business has multiple sources of funding as well as multiple lines of business.