Write the task-oriented guide a merchant (or the platform team onboarding them) follows to go from nothing to accepting payments: registration, activation, verification, account setup, token selection, and webhook configuration, in the correct order with the correct signer at each step.
Proposed steps:
- Create
docs/guides/merchant-onboarding.md.
- Present an ordered checklist with the caller and required signature for each step:
register_merchant (merchant) → set_merchant_status (admin) → verify_merchant (admin) → set_merchant_account → set_merchant_accepted_tokens → set_merchant_key → set_merchant_webhook.
- For each step give the CLI invocation, expected result, and how to verify it with the corresponding read function.
- Document which steps are optional and what capability each unlocks.
- Include a post-onboarding smoke test: create an invoice, pay it with a test payer, confirm settlement and analytics.
- Add a troubleshooting section for the failures merchants actually hit (inactive merchant, token not accepted, missing merchant account).
Acceptance criteria:
docs/guides/merchant-onboarding.md exists as an ordered, executable checklist.- Each step names the required signer and includes a verification call.
- Optional steps are clearly marked with the capability they unlock.
- A smoke test and troubleshooting section are included.
Write the task-oriented guide a merchant (or the platform team onboarding them) follows to go from nothing to accepting payments: registration, activation, verification, account setup, token selection, and webhook configuration, in the correct order with the correct signer at each step.
Proposed steps:
docs/guides/merchant-onboarding.md.register_merchant(merchant) →set_merchant_status(admin) →verify_merchant(admin) →set_merchant_account→set_merchant_accepted_tokens→set_merchant_key→set_merchant_webhook.Acceptance criteria:
docs/guides/merchant-onboarding.mdexists as an ordered, executable checklist.