Skip to main content

Getting started — sellers

This page outlines how a seller organisation becomes productive: secure access, a payout destination, a buyer relationship, and the first invoices.

1. Join and secure the account​

Sellers may arrive via invitation from a buyer or through self-registration, depending on programme rules.

  • Complete registration, email verification, and terms acceptance.
  • Prefer two-factor authentication and a strong password policy for users who can move money or change payout details.
  • Use supported login methods offered by your tenant (password, social login where enabled).

2. Configure how you receive funds​

Sellers choose how proceeds arrive:

  • Connect your own wallet for crypto-style settlement where that is in scope for your programme.
  • Or adopt a platform-hosted wallet option when your buyer or programme offers it—less operational burden, different trust assumptions.

You can later change wallet addresses with verification steps to prevent takeover fraud, withdraw to an external wallet, or use bank off-ramp options where available in your region and product configuration.

Always review payment history so finance can match inbound settlement to invoices.

3. Establish buyer relationships​

Mirroring the buyer journey:

  • Add a buyer or invite them, or accept an incoming buyer connection.
  • Configure per-buyer settings such as trust posture, payment terms, and preferred payment method where the product exposes those controls.
  • Deactivate, reactivate, or archive relationships as contracts end.

The buyer side has complementary controls; connection is a two-party state in the product.

4. Prepare invoice practices (API-first)​

Assume most invoices will appear automatically after booking reports are submitted through the API—by the buyer’s systems, yours, or both, depending on programme setup.

Decide how your operations team will:

  • Monitor auto-generated invoices and use confirmation or dispute paths when the booking feed does not match reality—before high volumes go live.
  • Fall back to manual creation with or without line items only when a booking never arrived over the API.
  • Use bulk CSV uploads where still supported for migrations or legacy windows.
  • Attach supporting documents buyers need for audit when the automated record is incomplete.

Plan checks on automated data the same way you would QA any mission-critical integration.

5. Hand off to day-to-day flows​

Continue with Invoices and payments for review cycles on the buyer side, settlement visibility, disputes, and refunds.