Skip to main content
Business & GrowthPayment Services40 lines

Marketplace Seller Onboarding and Payouts

Model seller verification, charges, transfers and payouts with provider-state checks and reconciled test flows.

Quick Summary10 lines
Use this skill to design money movement for a marketplace with multiple sellers. Establish the provider, supported countries, legal entity, charge model and responsibility for refunds, disputes and negative balances. Verify current provider capabilities for the actual account configuration; a generic API example does not establish regional eligibility.

## Key Points

- [Stripe Connect hosted onboarding](https://docs.stripe.com/connect/hosted-onboarding)
- [Separate charges and transfers](https://docs.stripe.com/connect/separate-charges-and-transfers)
- [Stripe Connect Account Links API](https://docs.stripe.com/api/account_links/create)
- [Stripe Connect charge models](https://docs.stripe.com/connect/charges)
skilldb get payment-services-skills/marketplace-seller-paymentsFull skill: 40 lines
Paste into your CLAUDE.md or agent config

Marketplace Seller Onboarding and Payouts

Use this skill to design money movement for a marketplace with multiple sellers. Establish the provider, supported countries, legal entity, charge model and responsibility for refunds, disputes and negative balances. Verify current provider capabilities for the actual account configuration; a generic API example does not establish regional eligibility.

Model seller readiness

Prefer provider-supported hosted or embedded onboarding when it fits the product. Keep sensitive identity documents within the approved provider flow where possible. Map the seller's internal ID to the provider account ID and preserve that mapping.

A return from onboarding does not prove readiness. Inspect outstanding requirements and the capabilities needed for the intended operations. Track incomplete, restricted, enabled and later-disabled states explicitly. Requirements can change after initial activation.

Use short-lived onboarding links according to the provider contract. Regenerate expired links through the authenticated seller flow rather than sharing another seller's link. Verify account ownership on every dashboard and onboarding route.

Separate money movements

Distinguish a charge, a transfer and a payout. The buyer payment, allocation to a connected account and movement to an external bank are different events with different failure and timing behavior. Choose the charge model deliberately and document the allocation of fees, refunds and disputes.

Persist a business-operation ID and provider object IDs. Process webhooks with signature verification, deduplication and an explicit state machine. Out-of-order events should trigger a fresh provider-state check, not regress a completed record.

Reconcile before retrying an uncertain create or money-movement request. A network timeout does not prove that the provider did nothing. Use supported idempotency mechanisms and verify that repeated requests have the same intended parameters.

Test the lifecycle

Use provider test accounts and test-mode credentials. Exercise incomplete onboarding, capability suspension, successful payment, failed payment, partial refund, transfer failure, payout failure and duplicate or delayed webhooks. Verify which actions affect platform and seller balances under the selected charge model.

Reconcile internal allocation records with provider transactions and settlement reports. Separate timing differences from missing money and unsupported assumptions. Do not infer bank receipt solely from a successfully created payout object.

Deliver the account-state model, money-flow diagram, responsibility matrix and test evidence. Keep production activation, real charges and payouts outside the test workflow unless explicitly authorized. Show unresolved country, liability or operational requirements before treating the marketplace as ready for live sellers.

References

Install this skill directly: skilldb add payment-services-skills

Get CLI access →

Related Skills

Mollie

Accept payments with Mollie. Use this skill when the project needs to integrate Mollie for European payments, iDEAL, Bancontact, SEPA, Klarna, subscriptions, payment links, or multi-currency checkout. Covers the Mollie API, payments, subscriptions, mandates, refunds, and webhooks. Popular in Netherlands, Belgium, Germany, and across Europe.

Payment Services•170L

Paddle

Accept payments with Paddle as merchant of record. Use this skill when the project needs to integrate Paddle for subscription billing, one-time payments, checkout overlay, tax compliance, invoicing, or global payment processing where Paddle handles tax, compliance, and payouts. Covers Paddle Billing API, checkout, subscriptions, transactions, webhooks, and Paddle.js.

Payment Services•213L

Payment Fraud Scoring and Review

Evaluate provider risk signals, review thresholds and fraud outcomes while measuring false positives and delayed labels.

Payment Services•37L

Paypal

Accept payments with PayPal. Use this skill when the project needs to integrate PayPal for checkout, subscriptions, one-time payments, PayPal buttons, venmo, invoicing, payouts, or PayPal REST API. Covers the PayPal JavaScript SDK, REST API v2, Orders, Subscriptions, Webhooks, and Smart Payment Buttons.

Payment Services•224L

Razorpay

Accept payments with Razorpay. Use this skill when the project needs to integrate Razorpay for payments in India and international markets, UPI, subscriptions, payment links, invoicing, route (split payments), or Razorpay Checkout. Covers the Razorpay API, Checkout.js, orders, subscriptions, webhooks, and UPI.

Payment Services•223L

Square

Accept payments with Square. Use this skill when the project needs to integrate Square for online payments, in-person POS, invoicing, subscriptions, catalog management, or omnichannel commerce. Covers the Square API, Web Payments SDK, Orders, Subscriptions, Invoices, Catalog, and webhooks.

Payment Services•218L