Legacy schema — superseded by the Cards API. New programs integrate via the Cards API. This schema remains the supported path for file-integrated programs that have not yet migrated.
Beyond the standard required and optional field checks and data type validations, Lead performs additional validations.
Enforced Today
| Validation | Description |
|---|---|
| Missing closure details | closed_at and closed_reason must be provided for closed accounts |
| Invalid Expiration | expiry_date may not be before activated_at or created_at |
| Invalid Account Reference | account_id must match an account within our system that was previously submitted via Accounts Daily file |
| Invalid Entity Reference | entity_id must match a client_customer_id or entity_id within our system |
| Disallowed Entity Reference | entity_id must match an account_holder or authorized_user on the linked account. |
| Invalid Card Reference | replaced_by must match a client_card_id within our system (or within the same file) |
| Nonterminating Update to Card on Closed Account | Updates to existing cards must include a “closed” or “expired” card status if the account is closed. |
Future Enforcements
Lead expects partners to comply with the below validations; however we do not currently enforce them upon daily processing. We will provide you with 60 days notice before enforcing the following validations.
| Validation | Description |
|---|---|
| Invalid Namespace | client_card_id may not start with the characters card_ |
| Card with ReplacedBy must be in terminal state | If a card has been replaced, it must not still be active. |
| Updates not allowed on Immutable Fields | account_id, entity_id, is_virtual, card_type, created_at, activated_at, expiry_date, closed_at, closed_reason, replaced_by |
| Card Creation on Closed Account Not Permitted | New cards may not be created when the linked account_id has a status of closed |