Zertiban API

Unified REST API for PagaFactu and ZertiPay. Two environments (sandbox and production) and OAuth2 Client Credentials authentication.

Servers

Same endpoints, contracts and data model in both environments. Start in sandbox at no cost and move to production once everything is validated.

Environment	Base URL
Sandbox	https://nc-api-sandbox.zertiban.com
Production	https://nc-api.zertiban.com

Limits, capacity and migration details in Environments.

Authentication

There is no self-service signup or interactive login: credentials (clientId / clientSecret) are handed out after onboarding and every call is server-to-server using OAuth2 Client Credentials over Basic Auth.

1. Request an access_token from POST/idp/oauth2/token with grant_type=client_credentials.
2. Send it as Authorization: Bearer {access_token} on every subsequent call.
3. Refresh the token when it expires.

curl -X POST https://nc-api-sandbox.zertiban.com/idp/oauth2/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -u '{clientId}:{clientSecret}' \
  --data-urlencode 'grant_type=client_credentials'

Full walkthrough with Python and axios examples: Authentication.

How it's organised

The API is grouped by service (Flow, PagaFactu, Payment, IdP), each with its own URL prefix (/flow/..., /pagafactu/..., etc.). The left-hand menu lists every operation grouped by tag; each operation has its own page with request/response examples, parameters and error codes.

Don't have credentials yet?

Start with Registration & Onboarding.