Review the Customer ID Verification (KYC/CIP) guide at docs.galileo-ft.com/pro/docs/customer-id-verification to understand which fields are required for your program's CIP configuration before submitting.
POST to the Create Account endpoint (reference: docs.galileo-ft.com/pro/reference/post_createaccount) with customer PII including name, date of birth, address, and government ID details alongside account configuration parameters.
Parse the response for the CIP verdict field if your program uses Galileo's integrated CIP solution — the verdict is returned synchronously in the Create Account response.
If the CIP result is pending or requires manual review, monitor the Events API for account status update events indicating the final KYC outcome.
Once the account and card are active, use the card-creation endpoints guide (docs.galileo-ft.com/pro/docs/card-creation-endpoints) if a separate card issuance step is needed beyond what Create Account provides.
Test KYC flows in sandbox using the Galileo sandbox environment (sandbox.gpsrv.com) before promoting to production.
Known gotchas
The Create Account endpoint creates a customer record, account, and card in a single call; if you need only a virtual card without a physical card product, use the Create Virtual Card Account endpoint instead.
Galileo's Program API uses a different authentication model than REST bearer tokens — consult the Environments and Quickstart guides at docs.galileo-ft.com/pro/docs/environments for credential setup specifics.
CIP verdicts from Galileo's integrated solution may be synchronous in sandbox but subject to additional review delays in production depending on the KYC provider configuration.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp