Skip to main content
Register in-game payment records. Registered payments are automatically attributed to the user’s boosted creator.

Flow

Create Payment

Request
Response (201 Created)

Required Parameters

Optional Parameters

Distribution Type

distributionType is used for settlement calculation. When omitted, it is inferred from platform. Inference rules
If the inferred value does not match your actual distribution channel, settlement amounts will be wrong. For example, mobile self-payment (MOBILE_SELF_STORE) is inferred as MOBILE_STORE on Android, incorrectly applying a 30% store fee. Always send the value explicitly when it differs from the inferred one.
Settlement Calculation: Net Amount = Payment Amount × (1 - Store Fee), then PlayCamp platform fee and creator fee are applied separately.If your game server already knows the net amount it receives after store fees, you can send it as netAmount/netCurrency.

Payment Timestamp (purchasedAt)

Settlement is always attributed to the moment the SDK API recorded the payment.
  • When purchasedAt is provided, that value is stored.
  • When omitted, the server stores the time it received the request.
  • Refunds always use the server receive time (the value cannot be supplied).
The settlement month is determined by this timestamp, so call the API as soon as a payment or refund completes. A transaction processed at the end of a month but reported the next day is attributed to the next month’s settlement.

Currency Conversion

For non-USD currencies, amount is automatically converted to USD (amountUsd field).

Refund Payment

Refunded amounts are deducted from settlement.

Error Handling

Bulk Payment

Register up to 1,000 payments at once. Request
Response (200 OK)

Bulk Payment Parameters

Result Status

Bulk payments support partial success. Even if some items fail, the remaining items are processed normally. A payment.bulk_created webhook event is triggered when the bulk payment completes.