Accept a payment for a seller

In this guide you’ll create a checkout that belongs to your platform, name a seller account as the destination, send the customer to it, and confirm the payment from a webhook. By the end the charge sits in your platform’s balance and the seller’s share has moved to its own. This is a destination charge. Your platform is the merchant of record, which is what a marketplace’s customer expects: they bought from the marketplace, not from the seller directly. See Choose your integration if that does not describe your case.

Before you start

A seller account. It does not need a payment-accepting capability on this shape, and does not need payouts active until it withdraws. See Create an account.
A product to sell. See Products.
Your own card_collection (or whichever payment method you offer) active on your platform, since your platform is the one being checked, not the seller. See Capabilities.

Steps

Create the checkout as your platform

Do not send X-Account-Id. Name the seller in transfer_data.destination and set platform_fee: the seller receives what is left of the sale after it, so a destination charge with no fee leaves your platform nothing to pay Bachs’s processing fee from.

curl -X POST https://sandbox-api.bachs.io/v1/checkout-sessions \
  -H "Authorization: Bearer sk_sandbox_abc123xyz..." \
  -H "Content-Type: application/json" \
  -d '{
    "product_cart": [
      { "product_id": "prod_8f2a71c4e05b", "quantity": 1 }
    ],
    "platform_fee": "2000.00",
    "transfer_data": { "destination": "acct_3Wq8ZfT1yHnJ5sVe" },
    "customer": { "email": "jane@example.com", "name": "Jane Doe" },
    "success_url": "https://example.com/thank-you",
    "cancel_url": "https://example.com/checkout"
  }'

{
  "checkout_id": "chk_c48e2a917d3f",
  "status": "open",
  "source_type": "CHECKOUT_SESSION",
  "amount": "19000.00",
  "currency": "NGN",
  "checkout_url": "https://checkout.bachs.io/c/Qm3vXk9Nf2LpR7c",
  "platform_fee": "2000.00"
}

checkout_id names the checkout for your own records and for GET calls; checkout_url carries a separate token, not the id, so do not parse one out of the other.

Send the customer to the checkout

Redirect them to checkout_url. Bachs hosts the payment page and collects the charge against your platform.

Confirm from the webhook

Bachs sends checkout.completed once the customer finishes. Check data.payment_status: paid means a charge was made. organization_id on the event is your platform, since the checkout was your platform’s.

Event

{
  "id": "evt_7f6e5d4c3b2a1908",
  "type": "checkout.completed",
  "created_at": "2026-08-12T09:15:00.000000+00:00",
  "organization_id": "acct_7KpQ2mNv4XbR9dLc",
  "data": {
    "checkout_id": "chk_c48e2a917d3f",
    "status": "completed",
    "mode": "payment",
    "payment_status": "paid",
    "amount": "19000.00",
    "currency": "NGN",
    "charge": {
      "id": "ch_2f8a71c4e05b",
      "amount": "19000.00",
      "currency": "NGN",
      "status": "succeeded"
    },
    "completed_at": "2026-08-12T09:15:00.000000+00:00"
  }
}

No Connect event routing to worry about here: this event is your platform’s own, so it arrives on any endpoint the same as any other event of yours. That is specific to this shape; a direct charge’s event originates with the account instead.

Read the seller's payout back

The seller’s share settles as a transfer from your platform to the seller once the charge settles. List it with kind=payout.

curl "https://sandbox-api.bachs.io/v1/transfers?kind=payout&connected_account_id=acct_3Wq8ZfT1yHnJ5sVe" \
  -H "Authorization: Bearer sk_sandbox_abc123xyz..."

{
  "items": [
    {
      "id": "tr_8c1e04a7b93f2d6540ab",
      "source": "acct_7KpQ2mNv4XbR9dLc",
      "destination": "acct_3Wq8ZfT1yHnJ5sVe",
      "amount": "19000.00",
      "currency": "NGN",
      "status": "paid",
      "metadata": {},
      "kind": "payout",
      "source_charge_id": "ch_2f8a71c4e05b",
      "created_at": "2026-08-12T10:31:00.000Z"
    }
  ],
  "pagination": {
    "next_cursor": null,
    "prev_cursor": null,
    "has_more": false,
    "limit": 50,
    "offset": 0,
    "returned": 1,
    "total": 1
  }
}

status is paid once settlement has posted the movement, pending before it has. The transfer carries the full "19000.00" the customer paid, because you named your cut with platform_fee. Your "2000.00" settles separately, readable from GET /v1/platform_fees. If you instead fix the seller’s share with transfer_data.amount, the transfer carries only that amount and your platform mints no separate fee record. See Destination charges for both forms.

What happens next

The charge settles into your platform’s pending_balance, then available_balance. The seller’s share moves at the same time, into its own balance. From there the seller withdraws on its own payouts capability. See Payouts.

Get started

Core concepts

Reversals and risk

Onboard an account

Build with Connect

Go live

Accept a payment for a seller

Before you start

Steps

What happens next

Next steps

​Before you start

​Steps

​What happens next

​Next steps

Before you start

Steps

What happens next

Next steps