Checkout fees

Checkout fees control who pays the Usetix platform fee at checkout and any extra fee you add on top. Events inherit these account defaults unless they set a custom event policy.

This endpoint remains available for backwards compatibility. New integrations should use the dedicated Checkout settings API, which combines fee defaults with the account-wide buyer fields shown on the same Settings page.

Reading requires a token with Read or Read + Write permission. Updating requires Read + Write. See Authentication.

Changes apply only to future orders. Existing orders keep their snapshotted totals. Organizer-initiated refunds retain the Usetix fee; if a captured sale cannot be fulfilled, failed-sale recovery refunds the buyer’s complete captured amount instead.

GET /admin/account_settings/payments

curl \
  -H "Authorization: Bearer your-token-here" \
  -H "Accept: application/json" \
  https://app.usetix.io/admin/account_settings/payments

Response:

{
  "data": {
    "platform_fee_payer": "organizer",
    "custom_fee_fixed_amount": { "amount": "0.00", "currency": "EUR" },
    "custom_fee_percentage": "0.0"
  }
}

PATCH /admin/account_settings/payments

Send only the fields you want to change, directly at the JSON top level. This example charges the Usetix fee to the buyer and adds €2.50 plus 5%:

curl -X PATCH \
  -H "Authorization: Bearer your-token-here" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"platform_fee_payer": "buyer", "custom_fee_fixed_amount": "2.50", "custom_fee_percentage": "5"}' \
  https://app.usetix.io/admin/account_settings/payments

Writable fields:

Response: 200 OK with the complete updated data object in the same shape as GET.

Validation failures return 422 Unprocessable Entity:

{
  "errors": {
    "custom_fee_fixed_amount": ["is not a number"]
  }
}

A Read token attempting PATCH receives 401 Unauthorized and no settings are changed.