Mark a sandbox customer as a house account
Sandbox-only. Marks (or unmarks) one of your business customers as a house account — the only source a purpose: prefunding payout accepts. Every sandbox organization is seeded with one house account already; use this to prefund from a customer you onboarded yourself. More than one customer can carry the marker. The marker alone is not enough to send from: the customer also needs its own active wallet on the destination chain, or its own USD account, or the payout is refused. On live, only Conduit can set it, so treat the marker itself as sandbox setup rather than something your integration writes. Returns the customer at its new state.
Body
Response
The customer at its new house-account state
Date the business was incorporated (YYYY-MM-DD)
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$"2020-03-15"
Legal structure of the business — the local jurisdiction name the customer declared at onboarding (e.g. 'Sociedade Limitada', 'GmbH', 'C-Corporation'). Free-form string; the available options are jurisdiction-specific and surfaced by the requirements discovery endpoint.
"Sociedade Limitada"
Effective signing mode for this customer right now: the per-customer override if one exists, else the organization setting, else the default. For a customer with no wallet claim yet, this is the value claim-non-custodial would freeze and the roster shape it accepts. For a customer that already claimed, the claimed wallet keeps the mode it froze at claim time, even if this value changes afterward. This field may be absent temporarily while the API is being updated.
passkey_required, programmatic, programmatic_unattended