Load customer data

ofac/pep screening and loading customer data to add customer data in cos after a successful kyc (know your customer) check, call the post /core/v1/cm/customers endpoint in cos to create the cardholder’s customer account {{ofac}} uses the customer name, date of birth (dob), and address the customer identification program (cip) requires the customer social security number or government issued id (for non us persons) the webhook event core customer ofac changed is triggered and returns an initial status of clear or failed if the status is clear , you can approve and create the customer credit card facility on your side if the status is failed , the cross river {{aml}} team investigates the case the webhook event is triggered again, sending a status of reviewing or pending , indicating that a person is reviewing the case this can take up to 48 hours on occassion, the cross river team might reach out to you to ask for additional supporting documents you will need to provide an email address for this the core customer ofac changed webhook returns any change in status, not just reviewing or pending after reviewing, the cross river team moves the status to either clear or positive the webhook event fires again if clear , you can continue with approving and creating a credit card facility for your customer if positive , you must decline the application this is quite rare to trigger an ofac/ {{pep}} failure in the sandbox use these values in your call for pep, in the name object use the name vladimir putin to get a hit for ofac, in the name object use the name francisco javier arellano félix ; and in the profile object use the birthdate 1969 12 11 (december 11, 1969) for ofac entity, in the name object use the entityname value blue star diamond once the customer record is cleared, there is no longer a reason to subscribe to the specific customer webhook cross river scans customer records nightly for ofac/pep if a customer hits ofac during a nightly scan, our aml team will reach out via zendesk to help clear you must keep the customer records you create up to date if a customer changes their name, address, email, or other details, use the customer management apis to update their record you can make this part of a nightly process the scans take less than a second anything that needs manual review is taken care of within 3 business days status definition changes (applies to ofac, pep, and internal list) webhook event responses from this point on mean positive must be rejected (no change) clear everything is fine (no change) pending the case is being reviewed (no change) reviewing a potential match within a category is being reviewed by cr and is pending a disposition previously this was failed failed there isn’t enough information to know the status (for example, rfi not responded to) see the apis required customer management apis as always, if you have any questions, email our support team