Global Accounts are implemented with the same Grid objects you use for other payment flows. This page shows the build sequence from customer creation through signed withdrawal and reconciliation.
Object model
| Concept | API object | What it does |
|---|
| Platform | Platform configuration | Controls supported currencies, rails, environments, and permissions. |
| Customer | Customer | Represents the user or business receiving a Global Account. |
| Global Account | InternalAccount with type: "EMBEDDED_WALLET" | Holds the customer’s balance and participates in Grid quotes. |
| Destination account | ExternalAccount or supported destination | Represents where funds are withdrawn or sent. |
| Quote | Quote | Prices and prepares movement between the account and a destination. |
| Credential | AuthMethod | Lets the customer authenticate with passkey, OAuth, or email OTP. |
| Session | Session (AuthSession response) | Issues a short-lived signing key for signed account actions. |
| Webhook | Account or transaction event | Tells your backend when balances change, funds move, or payments settle. |
Core flow
- Create or configure the customer.
- Complete required KYC or KYB before moving funds to or from fiat rails.
- List the customer’s internal accounts and find the Global Account by filtering for
type=EMBEDDED_WALLET.
- Register at least one customer credential.
- Fund the account through a supported Grid funding flow.
- Create a quote from the Global Account to a destination.
- Authenticate the customer, sign the quote’s
payloadToSign, and execute the quote with Grid-Wallet-Signature.
- Listen for account and transaction webhooks to reconcile the movement.
Incoming funds do not require a customer signature. Outbound movement from the Global Account does.
Where to go next
