Quickstart
Take a test registration from name check to certificate in about ten minutes.
Test mode
Every outcome you need to handle, on demand, with
simulate.Registration lifecycle
Every status, what causes it and what you do next.
API reference
Every endpoint, parameter and response.
What you can build
- Business registration inside your product. An e-commerce platform registers a merchant’s business name during onboarding; a bank or fintech registers a customer’s business as part of account opening; an accounting firm registers businesses for many clients.
- A name checker that tells your users, before they pay, whether CAC will accept a name, and why not when it won’t (missing qualifier, restricted word, already taken).
- Status updates without polling, through webhooks.
How it works
1
Check the name
POST /v1/name-checks says whether CAC will accept the name, with a reason code when it won’t.2
Create the registration
POST /v1/registrations, then add details with PATCH until missing_fields is empty.3
Upload documents
A means of ID, a passport photograph and a signature for each proprietor.
4
Submit
POST /v1/registrations/{id}/submit. After payment, FastCAC checks identity and files with CAC.5
Follow it to approval
Webhooks tell you when it’s queried, approved or rejected. Approved registrations come with a
registration number, certificate and status report.
Test mode and live mode
Every account has test keys (fc_test_…) and live keys (fc_live_…). Both use the same base URL,
the same requests and the same responses. Test mode never reaches CAC and never moves money. When
you switch to a live key, your integration works unchanged. See Test mode.
Live registrations open after your organization is verified. Name checks already work with live
keys. See Going live.