Glossary
- Commons
The shared Go library providing config, cache, database, Kafka, encryption, logging, observability, and queueing utilities.
A control requiring a second approver to approve or reject a pending high-value operation (OTC orders, transfers) before execution.
- Feature activation
The risk-gated enabling of a product capability (e.g., cards, accounts) for a customer once the required verification level is met.
- Fee sponsorship
Paying blockchain gas fees from platform-controlled sponsor wallets so customer wallets do not need native tokens.
- GitOps
The deployment model in which pushes to
dev/maintrigger a shared, OIDC-authenticated workflow that builds and deploys services.- Idempotency key
A client-supplied key on POST requests ensuring that retried requests cannot execute twice; stored in Redis at the gateway and propagated downstream.
- Internal account
A Gravv-managed financial account for a tenant or customer, backed by Web3 wallets and optionally attached fiat virtual accounts.
- KYC / KYB
Know Your Customer / Know Your Business — identity verification of individuals and businesses, operated through Sumsub.
- Minor units
The integer money representation (amount plus precision) used by the transaction record to avoid floating-point errors.
- MPC wallet
A blockchain wallet whose key material is held via multi-party computation by the custody provider (Dfns); no single party holds the full private key.
- Onramp
The conversion of fiat (card or local payment methods) into crypto settled to a Web3 wallet.
- OTC
Over-the-counter — larger FX orders handled through the OTC desk with dual authorization.
- Payee
A verified payment destination (beneficiary) — bank account, mobile money, SWIFT, SEPA, or ACH/wire — with provider-side external accounts and routing.
- Payment link
A hosted public page (stablecoin or card) through which a tenant’s customer can pay without direct API integration.
- Provider routing
The platform decision of which third-party provider executes a given payout, based on corridor, rail, and payee configuration.
- Sandbox
A first-class product environment with its own API keys, deployments, secrets, and provider sandbox modes, used by tenants for integration testing before live access is granted.
- Specifications
The protobuf contract repository — the single source of truth for gRPC methods and Kafka event schemas, with generated Go and Rust packages.
- Sweep
An automated rule that moves inbound funds onward (e.g., to a main account or external destination) when deposits arrive.
- Tenant
A business customer of Gravv. All data and operations are scoped to a tenant, identified by a tenant ID propagated across every service call.
- Transfer workflow
The state-machine record that orchestrates a money movement end to end, including fiat and crypto legs, fees, and settlement confirmation.
- Virtual account
Provider-issued bank account details (account number / IBAN) attached to an internal account so it can receive local-rail deposits.
- Webhook (inbound)
An event sent by a third-party provider to Gravv (settlement confirmations, KYC reviews), ingested at the gateway and fanned out over Kafka.
- Webhook (outbound)
An HMAC-SHA256-signed event delivered by Gravv to a tenant’s configured endpoint, with retries and delivery history.