Partner-managed lifecycle
Partner-managed intro
In Cross River's partner-managed model, partners are responsible for managing the card’s lifecycle and communicating relevant updates to Cross River via daily reporting. There are a series of requirements that the partner must meet before a card can be issued to a customer.
IMPORTANT: The following steps are mandatory for the Partners to ensure Cross River can conduct the necessary oversight of the card program.
The customer profile is created. When a customer is created, there are several webhook events that have to be registered for. See Add personal customer for more details.
The customer passes the required OFAC/PEP screenings.
The customer’s card is associated with their COS customer record using the unique card token. Use the Add identification endpoint to add customer-identifying documents, such as a driver's license or passport. You must provide some form of primary identification for a customer.
Compliance
It is important that once the customer is created they pass the required OFAC/PEP screenings, and that a card is associated to their COS customer record using a provided unique card token. These steps are critical to ensure Cross River can conduct transaction monitoring to meet our Compliance obligations.
Detailed requirements
| Requirement | Description |
|---|---|---|
1 | Cross River performs global OFAC/PEP screens in our system (COS) at the time of onboarding and regularly after that. | |
2 | Cross River receives files from processors and from the networks with tokenized card numbers. The processor uses the tokenized card numbers as unique identifiers for each cardholder. To match cards with accounts, it is mandatory that this unique identifier is added to the cardholder’s COS customer record. In addition, this unique identifier is used by the Cross River transaction monitoring and reporting teams to ensure that customer transactions are attributed correctly and that strict compliance is observed. Cross River expects that whenever a new card token is generated, you update this COS customer record. It makes no difference if the card is new or reissued. See Add identification for details about this endpoint. | |
3 | Cross River requires Commercial card partners to create both business and cardholder customer records in COS. Use the Update beneficial owner endpoint to update the COS customer record. |
In the partner-managed model, when the processor creates the card in their system, we need the partner to create a customer in COS.
Card lifecycle and customer controls
Partners are responsible for defining and managing the full customer card experience through their processor [1], including:
- Card Issuance
- Card Activation
- Card Suspension and Unsuspension
- Administrative Blocks
- Card Closure and Replacement
[1] This is subject to due diligence review and at in the sole discretion of Cross River