Qentaz
Qentaz (now operating under the brand Trazo) is a Colombian fintech providing collections, payments, disbursements, fraud control and reconciliation infrastructure for modern operations. Its REST API lets businesses generate charges (cobros), send payment links over WhatsApp, email or a hosted link, disburse funds to third parties (dispersiones), manage collector teams and administered (child) accounts, and reconcile cash and digital payments in real time. Authentication is a two-step bearer model (a static auth key exchanged for a short-lived access token), and webhooks push payment, payout and team events with a signed header. The API is versioned under /v1 and returns a custom JSON error envelope with Q-prefixed codes.
Qentaz publishes 1 API on the APIs.io network: Trazo API. Tagged areas include Company, Payments, Collections, Disbursements, and Reconciliation.
The Qentaz catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Qentaz’s developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, signup flow, and 17 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Trazo API
REST API for generating collections (cobros), disbursing funds (dispersiones), managing teams and administered accounts, reconciliation and webhooks. Two-step bearer-token authe...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Trazo (Qentaz) Webhooks
Outbound webhook events Trazo delivers to a merchant-configured endpoint for collections (cobros / payment), disbursements (dispersiones / payout) and team (equipo) state change...
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API