Organization API: Customer Portal: Crypto

Part of Customer Portal.

GET /api/v1/orgs/{org_slug}/portal/crypto/address

This customer's permanent deposit address for the network's family.

Scoped to the org, so the same customer id under two different orgs gets two different addresses and their deposits can never be confused.

GET /api/v1/orgs/{org_slug}/portal/crypto/assets

Assets this storefront can accept right now.

POST /api/v1/orgs/{org_slug}/portal/crypto/check

Look for this customer's payment now, and say where it stands.

The org portal counterpart of the platform check. An org customer waiting on a crypto payment has exactly the same question as a platform one, and the storefront SPA they are served has the same refresh button.

Rate limited per org customer, and the chain read inside is throttled per address, so several open tabs cost one read rather than one each.

application/json

Type: object or null.

GET /api/v1/orgs/{org_slug}/portal/crypto/deposits

Deposit history, including transfers still confirming.

GET /api/v1/orgs/{org_slug}/portal/crypto/deposits/{deposit_id}

One deposit, for polling while it confirms.

GET /api/v1/orgs/{org_slug}/portal/crypto/plan

Every way to pay this amount in crypto, cheapest first.

The org counterpart of the platform plan endpoint. It answers the question a customer has ("how much do I send to end up with $X?") instead of showing a rate and leaving them the arithmetic, and says outright when a chain's fee would eat the payment.

GET /api/v1/orgs/{org_slug}/portal/crypto/quote

How much to send for a target USD credit, itemised.

Quoting with invoice_id records a payment intent, which is what locks the rate and lets the deposit settle that invoice when it lands instead of arriving as a balance the customer then has to spend by hand.