FIS Horizon

Infrastructure Process Required Before Calling APIs

API User Needed Subscriptions

1. HORIZON-Authorization-v2: Used to get the needed authorization bearer token

2. HORIZON-Customer-v1: Used to get needed customer details and list of accounts

3. HORIZON-Bank-Controls-1: Used to get needed account data regarding specific demand deposit and savings account types

4. HORIZON-Account-Aggregation-v1: Used to get needed transaction data

5. HORIZON-Transactions-v1: Used to add a new transaction to the core for accounting

6. HORIZON-Card-v1: Used to get card details associated to a transaction

7. HORIZON-Card-v2: Possible future use for block and reissue

8. HORIZON-Collateral-v1: May not be needed, was subscribed to while investigating account data lookup

Required Pega Rules To Be Configured

1. FISHorizonBaseURL - The needed base url to access the API calls

   1. Sandbox/Staging Base URL - https://api-gw-uat.fisglobal.com/rest/horizon

   2. Production Base URL - https://api-gw2-prod1.fisglobal.com/rest/horizon

   3. Override if necessary, but these will likely be accurate for all FIS Horizon clients

2. FISHorizonOrganizationId - Application setting to denote the client's organization id

3. FISHorizonSourceId - Application setting to denote the client's source id

4. FISHorizonAuthProfile - A “basic” authentication profile will need to be configured to house the client’s API user id and secret needed (in each environment)

5. FISHorizonAuthorization - An “OAuth2.0” authentication profile will need to be configured to house the client’s Authentication client id and secret needed to get a bearer token (in each environment)

6. ImplServiceTokens - A row will need to be added to the table for "FISHorizonTokenProvider", see Rockland for an example