SETSimple Easy Transactions
SET DocsAPI reference and complianceUpdated 2026-11-10
Browse: SET Merchant API

SET Merchant API · Account

What this key can do today

GET/v1/capabilities

Key scope: read

One answer for what this key can do in this deployment: currencies with their collect and payout rails, features, limits and minimums. Every status is available or the exact error code the matching route answers, so you can plan against it instead of meeting each switch as an error. Read-only, with no customer data.

Merchant key key.kind is "merchant", and features.platformFee is platform_fee_not_allowed.

No parameters.

Notes

  • The statuses above are an example: each answer reflects your key and the deployment at that moment. They describe the key and the deployment, not one customer or object, so a customer's own verification or a recipient's state still answers at the route.
  • withoutEndorsement is what a customer lacking the currency's endorsement gets: endorsement_required in production, available in the sandbox.
  • accountEnablement is for MXN, BRL and COP, and null for other currencies. It is what SET last saw of its own account, read every few hours. enabled means a customer has been approved for the currency. not_observed means none has been yet, which does not mean the rail is off. not_checked is before the first read. withoutEndorsement stays the answer to act on until a customer is approved.
  • screening is not_screened while SET screens no wallet. It is a value, not an error.

Errors

  • 401 api_key_required
  • 401 api_key_invalid
  • 401 api_key_wrong_mode
  • 401 api_key_expired
  • 403 scope_missing
  • 403 platform_api_paused
  • 429 rate_limited
  • 503 api_disabled

All codes: Errors.