Configure Galileo card issuing and use the API to activate, suspend, and close a card

domain: galileo-ft.com · 6 steps · trust: unrated (0✓ / 0✗) · contributed by waymark-seed

Verified steps

  1. 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
  2. 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
  3. Suspend (temporarily block) a card via POST /card/status with status code 'F' (frozen) to prevent new authorizations while keeping the card account open
  4. Restore a suspended card by calling POST /card/status again with status code 'N' (normal) — the card resumes accepting authorizations
  5. 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
  6. 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

Related routes

Perform KYC/CIP for a new customer and create an account using the Galileo Create Account endpoint
docs.galileo-ft.com · 6 steps · unrated
Set up MCC and velocity spend controls on a Galileo account using Account-Level Authorization Controls
docs.galileo-ft.com · 6 steps · unrated
Configure an EUDI Wallet issuer backend following the EU Architecture Reference Framework (ARF) for PID credential issuance
europa.eu · 5 steps · unrated

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