GRC Oversight

Mercury

Collect cash-account inventory as read-only finance-system evidence through the Mercury API. Mercury's public API does not document a team-member/role or money-movement-permission listing endpoint as of this writing, so 'who can move money' access-review evidence is NOT covered here -- track it manually (e.g. via Mercury's dashboard team-permissions screen) until Mercury documents one.

Finance · Banking
Tier 2 generic template — runs on the HTTP / REST endpoint connector
Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

  • Cash account inventory (read-only)
  • Money-movement permission evidence NOT covered (no documented endpoint) -- track manually
Read-only calls

Endpoints this template queries

The exact Mercury API endpoints called once connected. All read-only GET requests unless noted.

  • GET/accounts
Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

  • Base URL(prefilled: https://backend.mercury.com/api/v1)
  • Endpoints (JSON)(prefilled: [ { "id": "accounts", "name": "Accounts", "path": "/accounts" } ])

Optional

  • Auth header name(prefilled: Authorization)
  • Auth header value(secret credential)
Where this evidence goes

Which frameworks this evidence supports

Mercury evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Mercury evidence

Get a guided demo, or start by scanning any domain for free.