Why is RD blocked for some customers? (State restrictions)
Last updated: July 8, 2026
RD (Dakota's native stablecoin) is not available in all US states. If a customer's registered address is in a restricted state, they'll be blocked from using RD, and you'll receive a state-restricted-rd error.
Which states are restricted?
RD is currently unavailable in:
State | Abbreviation |
|---|---|
Florida | FL |
Georgia | GA |
Louisiana | LA |
New York | NY |
Texas | TX |
Washington | WA |
Note: This list may change over time as Dakota expands state coverage.
Who gets blocked?
Customer type | Blocked if... |
|---|---|
Business | Their registered or operating address is in a restricted state |
Individual | Their residential address is in a restricted state |
Non-US customer | Not affected |
US customer with unresolved jurisdiction | Not affected |
What does the error look like?
When a restricted customer tries to use RD, you'll receive:
HTTP status:
403Error code:
state-restricted-rd
How to handle it in your app
Catch the state-restricted-rd error and fall back to a non-RD stablecoin for affected customers. USDC is the recommended alternative:
if (error.code === 'state-restricted-rd') {
// Fall back to USDC or USDT for this customer
}
Don't surface the raw error to your end user — instead, silently route them to a supported stablecoin.
What's not supported
RD is only available on Base (base-mainnet and base-sepolia). It is not available on other networks.
There is no way to override or bypass the state restriction for a customer — the restriction is applied based on their address on file.