Non-KYC Use Case
Non-KYC Enrollment Flow Use Case Example
This enrollment flow is an example use case for Non-KYC related enrollments - meaning this a simple enrollment that doesn't involve going through the KYC process with IDV.
Please note your exact enrollment process may differ but this can be used as a sample to get an idea of what the process may look like at a high level.
1. Call the Enrolls User into Product and Creates Account and Card API
Runs OFAC, creates the BaaS Profile, as well as the account during the enrollment process.
Possible Status Messages
- Success
- Status pending - OFAC Match
- Failed invalid input
Webhook
As shown in our Webhook Samples page, the Account Updated Webhook (whether positive or negative) will be returned.
This webhook will not be returned if enrollment fails due to server error or exception.
You will receive an account identifier (id) from the webhook and endpoint response that can be used.
You will also receive a webhook for all the possible status codes.
An OFAC match (if the name matches in the OFAC database - first and last name) will trigger a manual review process.
Manual review will send a separate response via webhook below.
Response after webhook:
Status declined - OFAC Manual Review Failed
2. Call the Get Account API
This will send typical responses for this API including (non-sensitive) account info.
This is to initiate the provisioning process.
4. Optional step - provision the card
Check if the user has an points to disburse, if any, then use below adjustment API
5. Call the Adjustment API
To adjust the balance on the account (as an example, giving $10 for cashback or promo)
Transactions Events webhook is returned as shown in the Webhook Samples page.
6. Call the Get Transactions List API
After a set amount of time (example being a few days), then this API can be called to return a list of transactions.
Updated 21 days ago