Lunch
Guides

Vendor Onboarding

A vendor must meet four requirements before receiving an advance. GET /v1/organizations/{externalId} reports each one.

RequirementMet when
ComplianceThe vendor's compliance is cleared.
AgreementThe agreement is signed.
Bank accountA payout account is on file.
Collection accountThe account the vendor's payors pay into is ready to receive payments.

The first three can be completed in any order. Lunch normally opens the collection account once they are met. Advance requests before all four are met return 409 business_not_eligible.

Collection account: requires only an address, taken from the signed agreement or from contact in PUT /v1/organizations/{externalId}. Verification usually takes a few minutes. Once open, its details are returned as remittance on GET /v1/organizations/{externalId} and on every advance response.

Onboarding a Vendor

Vendors currently onboard by invitation.

  1. Sync the vendor with PUT /v1/organizations/{externalId}, or sync one of its invoices. Include taxId if available.
  2. If you have the vendor's bank details, set them with PUT /v1/organizations/{externalId}/payout-account.
  3. Send POST /v1/invitations so the vendor can claim its account and sign the agreement.

The vendor must be synced before it is invited. Unsynced identifiers return 404 business_not_found.

Invitations

Invitations apply only to your relationship with the vendor. Access does not extend to the vendor's relationships with other platforms, and theirs does not extend to yours.

BehaviorDetail
Existing accountsThe person is added to this vendor. No second account is created.
Repeat invitationsReissues the link. Only one link is active at a time.
ExpirySingle use. Expires after 30 days.

Hosted Onboarding

Hosted onboarding is not yet live

POST /v1/onboarding-sessions returns a single-use link, displayed in your product, where the vendor completes compliance, the agreement and bank account. Links created today do not resolve. Build against the published shape. Lunch will announce availability.

What's Next

Last modified on