Payment Integrations in Sharetribe

Before choosing a payment provider, define the business model. Are users buying products, booking services, renting assets, subscribing, sending offers, or paying invoices?

Each model creates different requirements for authorization, capture, payout timing, cancellation rules, taxes, receipts, and platform commissions.

Stripe Connect is a common marketplace payment foundation because it supports seller onboarding, platform fees, split payouts, and compliance flows.

The implementation still needs careful UX. Sellers need to understand onboarding status, payout requirements, verification issues, and why a payout may be delayed.

Some marketplaces need PayPal, wallets, bank payments, or other local payment methods because buyers trust them or expect them in a region.

Alternate payment methods can improve conversion, but they also add transaction-state complexity. Confirm how refunds, disputes, fees, and payout timing work before adding them.

Regional providers such as Omise can be important for markets where local payment behavior differs from the default Stripe flow.

When using a regional provider, the transaction process needs to reflect provider-specific states, success callbacks, failed payments, and refund behavior.

Marketplace revenue can come from buyer fees, seller fees, commission, subscriptions, listing fees, promotions, or a combination of models.

The payment integration should make fee calculation transparent and testable. Users should see what they are paying, and admins should be able to reconcile transactions.

Refund and dispute rules should be designed before launch. A refund can affect the buyer, seller, platform fee, payment provider fee, transaction state, and accounting reports.

Payout timing should match the trust model. For example, funds may be released after shipment, after booking completion, after a review window, or after admin approval.

Test failed cards, duplicate submissions, expired sessions, abandoned checkout, webhook delays, seller onboarding failures, partial refunds, full refunds, disputes, and payout failures.

Payment QA should be part of marketplace launch planning, not a final checklist item.

Payment integrations are deeply connected to marketplace workflow. Choose providers and transaction logic based on the business model, user trust, regional needs, and operational visibility.