Recipes
CorePro supports several different configurations. See below for common recipes that match most closely to your particular use cases.
-
- Display a list of links to the bank disclosures for your user to read
- For each disclosure link the user clicks, download and display the disclosure
- Gather minimal information from your user *
- Gather basic Personally Identifiable Information from your user
- User responds to verification questions returned from previous step
-
- Create a bank account for the user in CorePro
- Create a link to another Financial Institution (for moving funds in/out of CorePro) *
- - OR -
- Send trial deposits to another Financial Institution
- Time passes. Verify the above deposits and create a link to that Financial Institution
-
- Move funds
-
- Nothing to do in CorePro
-
- Retrieve all customer information, including all open accounts (with balances), and all verified external accounts
-
- Retrieve all transactions for a given account
-
- Create a bank account for the customer in CorePro
- (Optional) Search for the "other" customer to add to the account
- Add access to that account for the "other" customer
-
-
Create a customer in CorePro to represent the child
/customer/create
- Pass
accessTypeCode
ofACCT
(aka Account Holder only)
- Create a bank account for the customer in CorePro
- Add access to that account for the child customer created in step 1.
-
Create a customer in CorePro to represent the child
-
- Add access to an account for another customer
-
- List all those who can access a given account
-
- Request the card object be created and the physical card sent to the user
- Time passes; user receives physical card
- Transfers via debit rails (ISO-8583 requests) may now be performed successfully
-
- Request the card be locked
-
- Request the card be unlocked
-
- Request the account be added
-
- Request the account be removed
* Assumes you and the Bank of Record have an agreement that you are performing due diligence and vetting everything appropriately