Configure Galileo card issuing and use the API to activate, suspend, and close a card
domain: galileo-ft.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate each Galileo API request by constructing the SHA256 HMAC signature from your API login, key, timestamp, and providerId as documented in Galileo's authentication spec
Activate a newly issued card via the POST /card/activate endpoint with the PRN (Program Reference Number) and the card's last four digits for verification
Suspend (temporarily block) a card via POST /card/status with status code 'F' (frozen) to prevent new authorizations while keeping the card account open
Restore a suspended card by calling POST /card/status again with status code 'N' (normal) — the card resumes accepting authorizations
Permanently close a card via POST /card/status with status code 'C' (closed); closed cards cannot be reactivated and the account balance must be zeroed or transferred first
Retrieve current card status and account details via POST /get-card-info using the PRN to verify state changes before and after each lifecycle operation
Known gotchas
Galileo uses SOAP-style XML responses in some endpoints alongside newer JSON endpoints — confirm which format your integration expects before parsing responses
The PRN (Program Reference Number) is Galileo's primary card identifier — always use PRN, not PAN, in API calls to avoid exposing sensitive card data
Status codes are single-character strings (N, F, C); an unrecognized status code in the response indicates an error condition, not an intermediate state
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?