Programmatic deposit address provisioning is not yet available in the OMS API. To be notified when it launches, register your interest.
Register interest
Share your use case and we’ll reach out when programmatic deposit address provisioning is available.
Object
depositInstructions.address to display in your UI. Any supported asset sent to that address is automatically routed to the linked wallet.
How it differs from a wallet address
A customer’s wallet also has anaddress field, but direct deposits to a wallet address only trigger a wallet.depositDetected event, OMS does not auto-convert or route the funds. Deposit addresses are the correct pattern when you want OMS to act on incoming crypto.
| Wallet address | Deposit address | |
|---|---|---|
| OMS action on deposit | wallet.depositDetected event only | Auto-creates and executes transaction |
| Routing configuration | None | Asset, network, destination wallet |
| Reusable | Yes | Yes |
Status lifecycle
| Status | Meaning |
|---|---|
active | Monitoring for incoming deposits |
paused | Temporarily inactive; deposits are not processed |
deleted | Permanently removed |
Provisioning
Deposit addresses are provisioned by Polygon during onboarding and early access. In the sandbox, a simulation endpointPOST /deposit-addresses/{depositAddressId}/simulate is available for testing inbound transfers.
Related
- Deposit addresses guide: full walkthrough with request/response and webhook handling
- Virtual accounts: same concept for fiat: a bank account number that auto-converts to USDC