- Runs on credit rails, which generally offer higher interchange than debit
- No underwriting or credit check is required
- Payment history can be reported to the bureaus, so it works as a credit builder
- Risk is mitigated by the linked deposit account
Credit products require specific privileges on your organization. Contact your Synctera representative before planning one.
What You Are Building
The product comprises two accounts:- A deposit account as the security account
- A secured charge account that the card spends against
Step 1 — Create and Verify the Customer
A person must be set up and KYC/KYB verification completed. See Create a Personal Customer and KYC/KYB Verification.Step 2 — Record Disclosures
When the consumer is being onboarded:- USA Patriot Act Notice
- E-Sign
- Privacy Notice
- Smart card account agreement
- Security agreement
- Authorization for automatic payments from the security account (optional — see Step 6)
Step 3 — Create the Application
A charge secured account can optionally include an application, created through the Application API. See Credit Applications. If an application is denied — whether for KYC failure or another reason — adverse action reasons must be sent to personal customers, and the adverse action ID included in the application when its status is markedCREDIT_DENIED. This is optional for business customers. See Adverse Actions.
Step 4 — Create the Accounts
Create the deposit account that will act as security, then theCHARGE_SECURED account linked to it.
See Secured Charge Accounts, which covers using a customer DDA as the linked deposit account and creating the charge secured account itself.
Step 5 — Issue the Card
Issue against the charge secured account with"type": "CREDIT". Physical and virtual cards are both supported.
See Card Issuance and Management.
Step 6 — Enable Autopay, If Offered
When setting up a charge secured account with system autopay, you have two paths:- Opt in during onboarding. Send the
SC_AUTO_PAYMENTdisclosure asACKNOWLEDGEDwhen the customer opts in, then create the charge secured account withis_system_auto_pay_enabledset totrue. - Opt in later. Create the charge secured account with the default
is_system_auto_pay_enabledoffalse. When the customer opts in, send theSC_AUTO_PAYMENTdisclosure asACKNOWLEDGED, then patchis_system_auto_pay_enabledtotrue.
is_system_auto_pay_enabled cannot be set to true for a charge secured account unless that customer has acknowledged the autopay disclosure.

