starter.wiki中文

Payments

Payments

Choose the seller and funds-flow operating model, then select a direct payment processor or hand off to Merchant of Record or Marketplace Payments.

Three operating-model branches

This page compares direct processors only after the seller and funds-flow branch is known.

Direct processing keeps the business as merchant; Merchant of Record and marketplace flows change seller or funds-flow responsibilities and continue to dedicated Tasks.12

Direct

Direct merchant processing

The business remains merchant and selects a processor for payment acceptance.

MoR

Merchant of Record

A provider becomes seller for covered transactions; continue to the dedicated Merchant of Record Task.

Platform

Marketplace funds flow

Connected accounts and routed funds activate the dedicated Marketplace Payments Task.

  1. Seller and funds flow

    Resolve merchant identity and direct versus multi-party flow before comparing processors.12

  2. Payment coverage

    Verify merchant countries, customer regions, methods, authorization, capture, refunds, disputes, settlement, and payout.12

  3. Control and operations

    Set checkout, data, risk, tax, support, reconciliation, policy, and migration requirements.12

  4. Workload cost

    Model payment method, region, processing role, fixed and percentage fees, FX, disputes, refunds, and add-ons.3

Direct payment-processing routes

These candidates apply only after the direct-merchant branch is chosen.

A software team wants developer-first payment APIs

Evaluate Stripe.

Stripe is a direct-processing route with broad web payment and developer surfaces.

Verify: Use the dedicated Billing, Connect, Tax, Invoicing, and Radar product decisions for those jobs.1

Enterprise acquiring and global operations are justified

Evaluate Adyen.

Adyen fits organizations able to operate a larger commercial and payment-method integration.

Verify: A small self-serve software team or simple domestic card flow may not justify this route.2

A PayPal-owned gateway and payment-method model fits

Evaluate Braintree.

Braintree provides a distinct gateway and processing route within PayPal ownership.

Verify: Verify current merchant eligibility, product scope, SDK direction, methods, regions, and PayPal relationship.3

What changes the decision

Provider fit follows merchant role, coverage, integration boundary, commercial model, and exit requirements.

Merchant role
Direct processors do not become Merchant of Record for the business's ordinary transactions.12
Acquiring and coverage
Countries, entities, methods, currencies, regions, and settlement models differ.2
Product identity
Provider products such as Billing, Connect, Tax, Invoicing, and Radar require separate Claims.1
Economics
Processing, gateway, interchange, international, FX, dispute, refund, payout, and product fees must be modeled together.13

Boundary: This Task owns the initial seller and funds-flow branch plus direct payment acceptance. It hands detailed Merchant of Record and marketplace selection to their dedicated Tasks.

Official resources

Verify current product scope, eligibility, pricing, policy, data, payout, and contractual boundaries in first-party material before implementation.

DocumentationStripe Payments
DocumentationBraintree overview

Sources

Official product and policy sources supporting the bounded routes on this page.

  1. 1
    Stripe Payments

    Stripe · Accessed Official

  2. 2
    Adyen online payments

    Adyen · Accessed Official

  3. 3
    Braintree overview

    PayPal · Accessed Official