Pay creators

Approved earnings sit in a hold (10 days by default), then become payable and campaign_payout.payable fires. From there you pay in one of three ways, depending on the campaign's settlement.

#Fees

Every transfer to one creator carries one fee: 4% of the amount, with a $0.50 minimum. The fee is added on top, so the creator receives the full amount they earned.

The minimum applies below $12.50. Card processing costs come out of the 4%, so there is no separate card fee. Paying one creator twice costs two fees. A transfer that is refused charges no fee, and the amount goes back to payable. Tracking, review, the ledger and the creator page are free.

#Who can move money

Only the workspace owner, admins and billing admins can pay, signed in or with a full-scope API key they created. Profile-scoped keys cannot read the balance, transfers or payees.

#Pay by card

One charge on your saved card covers every payable creator you select. No balance is needed and nothing waits on a hold.

curl -X POST https://api.pozy.ai/v1/creator-campaigns/6701a2b3c4d5e6f7a8b9c0d1/payout-batches \
  -H "Authorization: Bearer $POZY_API_KEY" \
  -H "Idempotency-Key: payout-launch-clips-2026-11-15" \
  -H "Content-Type: application/json" \
  -d '{ "excludeParticipantIds": ["6702b3c4d5e6f7a8b9c0d1e2"] }'

const res = await fetch("https://api.pozy.ai/v1/creator-campaigns/6701a2b3c4d5e6f7a8b9c0d1/payout-batches", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.POZY_API_KEY}`,
    "Idempotency-Key": "payout-launch-clips-2026-11-15",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ excludeParticipantIds: ["6702b3c4d5e6f7a8b9c0d1e2"] }),
});
const data = await res.json();
if (!res.ok) throw new Error(data.error);
console.log(data.batch.id, data.batch.totalCents, data.payment.status);

import os, requests

resp = requests.post(
    "https://api.pozy.ai/v1/creator-campaigns/6701a2b3c4d5e6f7a8b9c0d1/payout-batches",
    headers={
        "Authorization": f"Bearer {os.environ['POZY_API_KEY']}",
        "Idempotency-Key": "payout-launch-clips-2026-11-15",
    },
    json={"excludeParticipantIds": ["6702b3c4d5e6f7a8b9c0d1e2"]},
    timeout=60,
)
batch = resp.json()
print(batch["batch"]["status"], batch["payment"]["status"])

• Leave out participantIds to pay everyone payable. excludeParticipantIds leaves some out. paymentMethodId picks a card other than the default.
• The response has the batch (amountCents, feeCents, totalCents, one item per creator) and the payment status: succeeded, processing or requires_action.
• Creators who have not finished payout setup are skipped and stay payable.
• campaign_payout.settled fires once per creator paid. campaign_payout.failed fires if a payout does not reach the creator.

#When the bank asks for confirmation

payment.status: "requires_action" means the card issuer wants the payer to confirm (3-D Secure). Complete it in the browser with Stripe.js handleNextAction({ clientSecret }) using payment.clientSecret, then call POST /v1/payout-batches/{batchId}/confirm. A batch left unconfirmed is cancelled after 30 minutes. POST /v1/payout-batches/{batchId}/cancel cancels it sooner and makes the creators payable again.

#Pay from your balance

#Top up

POST /v1/balance/top-ups with amountCents and method: "card" charges your saved card. The balance is credited with what the card processor delivers after its processing fee, as soon as the charge succeeds.

curl -X POST https://api.pozy.ai/v1/balance/top-ups \
  -H "Authorization: Bearer $POZY_API_KEY" \
  -H "Idempotency-Key: topup-2026-11-01" \
  -H "Content-Type: application/json" \
  -d '{ "amountCents": 200000, "method": "card" }'

• Money from a card top-up can be paid to creators from 7 days after the charge. GET /v1/balance shows availableCents and the payoutLocks with each unlocksAt.
• A top-up that needs bank confirmation returns requires_action with a clientSecret. Finish it, or it is cancelled after 30 minutes. POST /v1/balance/top-ups/{topupId}/cancel cancels it sooner.
• GET /v1/balance/top-ups/{topupId}/receipt returns the receipt.
• Bank transfer top-ups are not available yet.

#Settle a creator

POST /v1/creator-campaigns/{campaignId}/participants/{participantId}/settle pays one creator from the balance. Leave out amountCents to pay everything payable. The fee is debited with the payout.

curl -X POST https://api.pozy.ai/v1/creator-campaigns/6701a2b3c4d5e6f7a8b9c0d1/participants/6702b3c4d5e6f7a8b9c0d1e3/settle \
  -H "Authorization: Bearer $POZY_API_KEY" \
  -H "Idempotency-Key: settle-cleo-2026-11" \
  -H "Content-Type: application/json" \
  -d '{}'

#Pay on your own rails

For settlement: "external", pay the creator however you like, then record the payment so their balance and your report stay correct: call the same settle endpoint with recordOnly: true and your own externalReference (a bank reference or invoice number, up to 200 characters). No money moves through Pozy and no fee is charged.

#Creator payout setup

Before a creator can receive money through Pozy, they finish payout onboarding from their campaign page (or POST /public/creator-campaigns/{token}/payouts with action: "onboard"). Their participant record shows payout.status: not_started, onboarding, ready or restricted. Creators download a statement for each payout from their page.

For your own flows, GET /v1/payees lists everyone you can pay with their onboardingStatus and payoutsEnabled, and POST /v1/payees/{payeeId}/onboarding-link creates a fresh onboarding link to send them.

#Transfers and the ledger

• POST /v1/transfers sends a balance transfer to a payee (payeeId, amountCents, optional reference). GET /v1/transfers and GET /v1/transfers/{transferId} read them back with status (pending, paid, failed, reversed).
• GET /v1/ledger/balances and GET /v1/ledger/entries give the money view across campaigns.
• GET /v1/creator-campaigns/{campaignId}/payables lists who is payable on one campaign and how much.

A card dispute on a payout charge is debited from your balance, which can go negative. Payouts stop until it is covered.

#Errors

#Endpoints

#Webhook events