Mast Bond

Connect integration guide

A hosted investing page and an unsigned-transaction API for approved partners.

Partner onboarding

Download a configuration from Mast Connect. Mast reviews eligibility, approves the portfolio list and registers the partner. A downloaded configuration is not an active integration.

Open the hosted experience

https://YOUR_MAST_HOST/connect/YOUR_PARTNER_ID

The hosted page connects to the customer’s wallet, checks the vault, requests an exact USDG approval, and submits the deposit. Use a normal link or a new browser tab; iframe embedding is not supported.

Build a native integration

GET /api/connect/v1/YOUR_PARTNER_ID
GET /api/connect/v1/YOUR_PARTNER_ID?action=quote&portfolio=balanced&wallet=0xCUSTOMER&amount=100&slippageBps=50
GET /api/connect/v1/YOUR_PARTNER_ID?action=report
GET /api/connect/v1/YOUR_PARTNER_ID?action=report&fromBlock=NEXT_BLOCK
  1. Fetch the catalog

    Use only the approved portfolio IDs. Catalog entries describe configuration, not live readiness.

  2. Request a quote

    The quote checks the network, portfolio and router. It returns integer asset/share amounts, decimals, a minimum share output, an expiry, and unsigned approval and deposit transactions.

  3. Obtain explicit consent

    Show the partner attribution disclosure, fees, portfolio, amount, minimum shares and expiry. The payer must be the customer receiving the shares. Never request a private key.

  4. Approve, simulate and submit

    Verify the response chain ID and contract addresses against your reviewed configuration. Let the wallet sign the exact allowance, wait for confirmation, simulate the deposit, then submit before expiry. If the quote expires or execution falls below the minimum, request another quote and customer confirmation.

  5. Reconcile receipts

    Verify a successful receipt and the router’s PartnerDeposit event. Poll the report with its nextBlock cursor; deduplicate by transactionHash and logIndex. Reports exclude the latest 12 blocks and expose public data. Add recent=true to start with the latest confirmed range; omit it to scan from deployment.

Limits of the pilot

Each deposit requires customer approval. No automatic payroll deductions, custody service, partner surcharge, billing or revenue share is implemented. Direct vault withdrawals remain independent of the router.

Browser API requests are accepted only from the partner’s registered HTTPS origins. Server-to-server reads need no API key because the catalog and deposit ledger are public. Do not interpret a deposit total as current AUM.