501 KiB
501 KiB
Z.ro Bank documentation review and required services list
Session ID: ses_29db90a57ffeTmuUWkytK6ZXjK Created: 4/6/2026, 11:11:50 AM Updated: 4/6/2026, 11:28:14 AM
User
I was looking at Z.ro bank at they seem to be able to provide most of the services we need to get started, go over their documentation and tell me exactly what we need. https://zrobank.com/en
Assistant (Plan · GPT-5.4 · 20.0s)
Thinking:
Researching documentation options
The task involves mostly research, and I wonder if we could skip the to-do list if it's manageable. I think using a task explore agent might help to check external sites, but I’m not sure if it can only search codebases. I feel like the general agent could address complex questions and execute multi-step tasks. Since the user wants a documentation review, I’m considering whether we should use webfetch to access the homepage and documentation pages to identify gaps in information.
Thinking:
Reading core documentation
Since the repo docs are available and relevant, I think it's wise to read through the core documentation to tailor the requirements. I could use multi_tool_use.parallel to read key docs and fetch site pages simultaneously. I need to provide a commentary update before diving into the tasks, indicating I'm reviewing both our docs and the Z.ro pages. It's essential to identify if there are documentation pages for "developers," "open finance," or "banking as a service" on the Z.ro site. Using the browser or webfetch could help navigate and capture links efficiently.
Reviewing our current product requirements alongside Z.ro’s public site and documentation so I can map their offering to the exact launch needs and gaps.
Tool: read
Input:
{
"filePath": "/home/alex/projects/payroll/docs/core-idea.md"
}
Output:
<path>/home/alex/projects/payroll/docs/core-idea.md</path>
<type>file</type>
<content>
1: # Core Idea
2:
3: ## One-line thesis
4:
5: A B2B2C fintech platform that turns customer payments into real-time commission balances, gives employees instant access to earned commissions, and gives employers a reliable system of record for commission payouts and performance.
6:
7: ## The problem
8:
9: ### Employers
10:
11: - Commission calculation is often manual, delayed, and hard to audit.
12: - Sales teams ask for informal advances when payroll cycles lag behind real sales activity.
13: - Finance teams struggle to forecast commission liability and reconcile payouts.
14: - Sales performance data is scattered across spreadsheets, POS tools, CRMs, and payroll systems.
15:
16: ### Employees
17:
18: - A sale can happen today, but the commission may not be usable for days or weeks.
19: - Early access to money often depends on asking for an informal advance.
20: - There is rarely a clear view of what has been earned, what is available, and what is still pending.
21:
22: ## The product
23:
24: The product sits between customer payment collection and employer payout.
25:
26: - A customer makes a payment.
27: - The platform receives the payment event directly, or receives trusted payment data from a partner.
28: - A commission engine applies employer-defined rules.
29: - The internal ledger allocates balances between employer and employee.
30: - A safe portion of the employee's commission becomes available immediately.
31: - The employee can cash out instantly, and later can also spend from a wallet or card.
32: - The employer gets the remaining balance on a defined settlement schedule.
33: - Both sides get visibility into earnings, payouts, and performance.
34:
35: ## Core product layers
36:
37: ### Payment collection or orchestration
38:
39: - Accept customer payments directly, or integrate with the employer's processor.
40: - Use payment events as the source of truth for commission creation.
41:
42: ### Commission rules engine
43:
44: - Support percentage-based, tiered, and custom rules.
45: - Lock an auditable calculation for every sale or payment event.
46: - Track exceptions, reversals, and dispute states.
47:
48: ### Ledger and balances
49:
50: - Maintain an internal double-entry ledger.
51: - Track at least three states: `earned`, `available`, `settled`.
52: - Keep clear subledgers for employee balances, employer balances, fees, reserves, and adjustments.
53:
54: ### Instant access rails
55:
56: - Start with instant bank transfer or `Pix` cash-out.
57: - Later add stored balance inside the app.
58: - Later add a prepaid or debit card linked to the balance.
59:
60: ### Employer analytics
61:
62: - Real-time commission liability.
63: - Sales staff performance based on actual money movement.
64: - Forecasts for payouts, reserve needs, and commission trends.
65:
66: ### Optional later financing layer
67:
68: - Employer-backed advances.
69: - True risk-based credit only after the business has reliable repayment and reversal data.
70:
71: ## Recommended money flow
72:
73: The safest early structure is partner-led custody.
74:
75: - A regulated bank or licensed financial partner holds funds.
76: - The platform owns the application layer, commission logic, ledger, and payout orchestration.
77: - Cards, `Pix`, KYC, and regulated money movement are handled through partners.
78:
79: Example flow:
80:
81: ```text
82: Customer pays R$1,000
83: |
84: v
85: Partner-held account receives funds
86: |
87: v
88: Commission engine calculates split
89: |
90: +-- Employee commission: R$200
91: +-- Employer balance: R$800
92: +-- Platform fee and reserve logic applied
93: |
94: v
95: Employee sees commission balance in app
96: |
97: +-- Instant cash-out
98: +-- Hold balance
99: +-- Later: card spend
100: ```
101:
102: ## Product thesis
103:
104: This should not start as a generic wallet, a payroll platform, or a payday loan app.
105:
106: The strongest wedge is:
107:
108: `real-time commission access tied to actual payment events`
109:
110: That positioning matters because it keeps the first product grounded in employer ROI, worker liquidity, and trusted payment data.
111:
112: ## Revenue model
113:
114: The business should start with software and money movement economics, not balance-sheet lending.
115:
116: - Platform or SaaS fee for employers.
117: - Take rate or processing fee on payment volume.
118: - Payout fee or bundled payout plan.
119: - Premium analytics tier.
120: - Later: interchange from card spend.
121: - Later: float-sharing or treasury economics if allowed by partner structure.
122: - Much later: advance fee for employer-backed early access products.
123:
124: ## What the company is not
125:
126: - Not a general neobank.
127: - Not a full payroll processor.
128: - Not a full CRM or sales engagement tool.
129: - Not a payday lender.
130:
131: The company is best understood as `commission infrastructure`.
132:
133: ## Phased expansion
134:
135: ### Phase 1
136:
137: - Payment-linked commission calculation.
138: - Employer and employee onboarding.
139: - Ledger with `earned`, `available`, and `settled` states.
140: - Instant payout access.
141: - Employer and employee dashboards.
142:
143: ### Phase 2
144:
145: - Stored balance and wallet behavior.
146: - Better analytics and forecasting.
147: - Reserve and holdback controls for refunds and chargebacks.
148: - Early employer-backed advance logic for selected customers.
149:
150: ### Phase 3
151:
152: - Card issuance.
153: - Spend directly from balance.
154: - More balance retention and interchange revenue.
155: - Deeper employer integrations.
156:
157: ### Phase 4
158:
159: - Multi-entity support.
160: - Broader partner distribution.
161: - Carefully controlled credit products if the data and regulation support them.
162:
163: ## Key risks and guardrails
164:
165: ### Regulatory boundary
166:
167: - Do not begin by directly holding deposits or acting like an unlicensed financial institution.
168: - Use a licensed partner for custody and regulated money movement.
169:
170: ### Reversals and chargebacks
171:
172: - Do not make all commissions instantly withdrawable on day one.
173: - Use availability rules, reserves, and holdbacks.
174:
175: ### Commission disputes
176:
177: - Require explicit employer-approved rules.
178: - Preserve a full audit trail for every calculation and adjustment.
179:
180: ### Labor and tax treatment
181:
182: - Distinguish `earned access` from `credit`.
183: - Map payroll, withholding, and deduction obligations with counsel before product launch.
184:
185: ### Partner dependence
186:
187: - Expect early dependence on bank, card, and processor partners.
188: - Build the ledger and business logic so the company can swap infrastructure providers later.
189:
190: ## Current strategic recommendation
191:
192: - Start in Brazil.
193: - Lead with `Pix`-based instant access to earned commissions.
194: - Use partner-led custody and compliance.
195: - Treat stored balances and cards as retention tools, not the initial wedge.
196: - Treat employer analytics as a second major value driver.
197: - Delay true lending until the core ledger and payout engine are reliable.
(End of file - total 197 lines)
</content>
Tool: read
Input:
{
"filePath": "/home/alex/projects/payroll/docs/brazil-market.md"
}
Output:
<path>/home/alex/projects/payroll/docs/brazil-market.md</path>
<type>file</type>
<content>
1: # Tese para o mercado brasileiro
2:
3: ## Resumo
4:
5: A melhor entrada para esta ideia no Brasil e uma plataforma B2B2C que conecta recebimento, calculo de comissao, ledger interno e acesso instantaneo ao saldo via `Pix`.
6:
7: O produto inicial nao deve ser vendido como banco digital nem como credito ao consumidor. A tese mais forte e:
8:
9: `transformar cada venda validada em saldo de comissao disponivel quase em tempo real`
10:
11: ## Por que o Brasil primeiro
12:
13: - `Pix` ja criou expectativa de movimentacao instantanea e barata.
14: - O mercado convive com atraso no pagamento de comissoes e com o uso informal de `vales`.
15: - Existem instituicoes financeiras, cooperativas, BaaS e emissores abertos a parcerias.
16: - Ha muitos segmentos com equipes comerciais comissionadas e operacao digital crescente.
17: - O argumento de valor e simples: menos atraso, menos friccao operacional e mais retencao do time de vendas.
18:
19: ## Dor local que o produto resolve
20:
21: ### Para a empresa
22:
23: - Calculo manual de comissao.
24: - Fechamento mensal demorado.
25: - Falta de visibilidade sobre passivo de comissao.
26: - Uso informal de `vales`, com pouca governanca.
27: - Dificuldade para reconciliar recebimento, comissao, estorno e repasse final.
28:
29: ### Para o vendedor
30:
31: - Venda feita hoje, dinheiro disponivel so dias ou semanas depois.
32: - Dependencia de `vale` para cobrir caixa pessoal.
33: - Falta de transparencia sobre o que foi ganho, o que esta disponivel e o que ainda esta pendente.
34:
35: ## ICP inicial
36:
37: O foco deve ser empresas brasileiras com time comercial comissionado e recebimento digital identificavel.
38:
39: Segmentos promissores:
40:
41: - franquias e operacoes de varejo com vendedores comissionados
42: - clinicas de estetica, odontologia e procedimentos eletivos
43: - academias e servicos recorrentes com equipe de vendas
44: - escolas, cursos e educacao privada com captacao comercial
45: - telecom, distribuicao e revendas com metas e bonificacao variavel
46:
47: ## Proposta de valor no Brasil
48:
49: ### Para a empresa
50:
51: - Automatizar o calculo e o repasse de comissoes.
52: - Reduzir dependencia de `vales` informais.
53: - Melhorar retencao e motivacao do time.
54: - Ter visao confiavel de performance comercial e custo de comissao.
55: - Ganhar previsibilidade de caixa e de passivo.
56:
57: ### Para o colaborador
58:
59: - Ver a comissao quase em tempo real.
60: - Sacar instantaneamente via `Pix` quando o saldo estiver disponivel.
61: - Ter mais clareza sobre metas, historico e projecao de ganhos.
62: - No futuro, usar saldo por cartao sem precisar sacar tudo.
63:
64: ## Produto recomendado para o Brasil
65:
66: ### V1
67:
68: - recebimento via parceiros de pagamento
69: - motor de regras de comissao
70: - ledger com estados `ganho`, `disponivel` e `liquidado`
71: - saldo para colaborador e empresa
72: - saque instantaneo via `Pix`
73: - dashboard basico para empresa e vendedor
74: - trilha de auditoria por transacao, comissao e ajuste
75:
76: ### V2
77:
78: - saldo retido em carteira
79: - analytics de performance e passivo de comissao
80: - regras de reserva para estorno e chargeback
81: - alertas e projecoes
82: - piloto de adiantamento com respaldo do empregador
83:
84: ### V3
85:
86: - cartao prepago ou debito
87: - maior retencao de saldo na plataforma
88: - integracoes com ERP, POS, CRM ou software vertical
89:
90: ## Parceiros locais que importam
91:
92: ### Infra financeira
93:
94: - instituicao de pagamento, banco parceiro ou BaaS para custodia e movimento regulado
95: - exemplos de infraestrutura para avaliar: `Dock`, `QI Tech`, `Celcoin`
96: - cooperativas e bancos menores podem ser parceiros comerciais ou institucionais, incluindo nomes como `Sicredi`, dependendo do modelo
97:
98: ### Processamento de pagamentos
99:
100: - parceiros para `Pix`, boleto e cartao
101: - exemplos para avaliar: `Pagar.me`, `Stripe BR`, `Adyen`
102:
103: ### Emissao de cartao
104:
105: - exemplos para avaliar: `Dock`, `Pomelo`, `Swap`
106:
107: ### KYC e KYB
108:
109: - exemplos para avaliar: `idwall`, `BigDataCorp`
110:
111: ### Juridico e regulatorio
112:
113: - escritorio com experiencia em instituicao de pagamento, arranjos de pagamento, `Pix`, LGPD e temas trabalhistas
114:
115: ## Consideracoes regulatorias
116:
117: O produto encosta em varias frentes e precisa de mapeamento juridico desde cedo.
118:
119: - Banco Central: estrutura de `Pix`, conta transacional, instituicao de pagamento, regras de reporte e compliance.
120: - Direito do trabalho: natureza da comissao, reflexos em folha, desconto de adiantamentos, regras contratuais com empregador.
121: - LGPD: dados financeiros e de performance do colaborador.
122: - CDC e transparencia: fees, prazos, disponibilidade e regras de estorno.
123:
124: Recomendacao pratica:
125:
126: - comecar debaixo da licenca e da infraestrutura de um parceiro regulado
127: - evitar custodia direta no inicio
128: - evitar vender o produto inicial como emprestimo
129:
130: ## Como tratar `vales`
131:
132: No Brasil, `vale` e um substituto informal para um problema real de liquidez. O produto pode reduzir esse comportamento sem virar credito agressivo logo no inicio.
133:
134: Sequencia recomendada:
135:
136: - acesso ao que ja foi ganho e validado
137: - liberacao conservadora de parte do saldo antes da liquidacao total
138: - adiantamento com respaldo do empregador
139: - so depois, se fizer sentido, credito com underwriting proprio
140:
141: Mensagem correta:
142:
143: - nao: `emprestimo para vendedor`
144: - sim: `acesso controlado a comissao ja gerada`
145:
146: ## Go-to-market no Brasil
147:
148: ### Primeiro movimento
149:
150: - fechar 5 a 10 design partners com dor forte de comissao e operacao relativamente simples
151: - priorizar empresas em que o evento de venda e facil de mapear ao pagamento
152: - vender para dono, financeiro, operacoes e gestor comercial
153:
154: ### Canais de distribuicao
155:
156: - venda direta para SMB e mid-market
157: - parceria com software vertical, POS e adquirencia
158: - grupos de franquia
159: - escritorios contabeis e consultorias de operacao ou folha
160:
161: ### Pitch inicial
162:
163: - reduza trabalho manual no fechamento de comissoes
164: - de ao time acesso mais rapido ao que ja foi ganho
165: - troque `vales` informais por um processo auditavel
166: - tenha visao em tempo real de performance e passivo de comissao
167:
168: ## Modelo economico mais provavel
169:
170: - fee de plataforma para a empresa
171: - fee por volume processado ou por pagamento conciliado
172: - fee por saque, ou plano com franquia de saques
173: - camada premium de analytics
174: - depois: interchange de cartao
175: - depois: compartilhamento de economia financeira, se permitido pelo arranjo com parceiro
176:
177: ## Principais riscos no mercado brasileiro
178:
179: - estorno ou chargeback depois da liberacao da comissao
180: - disputa entre empresa e vendedor sobre regra de comissao
181: - dependencia excessiva de um parceiro bancario ou de BaaS
182: - classificacao regulatoria errada do produto
183: - onboarding ruim para empresa e colaborador
184:
185: ## Tese final para o Brasil
186:
187: O melhor posicionamento nao e `mais um app de EWA` e nem `mais um banco digital`.
188:
189: O melhor posicionamento e:
190:
191: `a infraestrutura de comissao em tempo real para empresas brasileiras, com saldo disponivel via Pix e visibilidade operacional para o empregador`
(End of file - total 191 lines)
</content>
Tool: read
Input:
{
"filePath": "/home/alex/projects/payroll/docs/year-one-roadmap.md"
}
Output:
<path>/home/alex/projects/payroll/docs/year-one-roadmap.md</path>
<type>file</type>
<content>
1: # Year-One Roadmap
2:
3: ## Guiding principle
4:
5: Do not start by building a broad neobank or a consumer lending app.
6:
7: Start with the smallest product that proves the core wedge:
8:
9: `payment-linked commission calculation plus instant access to earned balances`
10:
11: ## Success goal for year one
12:
13: By the end of 12 months, the company should prove that employers will adopt a commission-led payout workflow and that employees will use it for faster access to earnings.
14:
15: The year-one target is not maximum feature breadth. It is proof of product-market fit for the core loop.
16:
17: ## Foundation and partner design
18:
19: ### Months 0-2
20:
21: #### Objectives
22:
23: - validate the first customer segment
24: - choose partner model for custody, payouts, and compliance
25: - lock the ledger and commission system design
26:
27: #### Workstreams
28:
29: - run design-partner interviews with target employers
30: - map employer commission workflows and exception cases
31: - choose payment and banking partner shortlist
32: - define balance states: `earned`, `available`, `settled`
33: - define reserve and holdback logic for reversals
34: - specify onboarding flows for employers and employees
35:
36: #### Deliverables
37:
38: - product requirements for v1
39: - legal and regulatory issue map
40: - partner shortlist and integration plan
41: - event model for payments, commissions, adjustments, and payouts
42:
43: #### Exit criteria
44:
45: - 5 to 10 serious design partners in pipeline
46: - clear v1 scope that does not depend on lending
47: - chosen path for `Pix` and custody infrastructure
48:
49: ## Core ledger and instant payout access
50:
51: ### Months 2-5
52:
53: #### Objectives
54:
55: - launch the first working employer flow
56: - prove that a verified sale can become an eligible commission balance
57: - enable instant cash-out for employees
58:
59: #### Product scope
60:
61: - employer onboarding
62: - employee onboarding through partner KYC
63: - payment ingestion or payment reconciliation
64: - commission rules engine
65: - internal ledger
66: - employee balance with `earned`, `available`, and `settled`
67: - employer settlement scheduling
68: - instant payout access via `Pix` or equivalent instant transfer rail
69: - employer dashboard with payout and commission views
70: - employee dashboard with balance and payout history
71:
72: #### Operational scope
73:
74: - manual support for edge cases
75: - conservative limits on instant availability
76: - dispute and adjustment workflows
77:
78: #### Metrics
79:
80: - number of active employers
81: - commission volume processed
82: - payout latency
83: - adjustment and reversal rate
84: - employee activation rate
85:
86: ## Analytics and stored balance
87:
88: ### Months 5-8
89:
90: #### Objectives
91:
92: - make the product more valuable to employers
93: - improve employee retention of balances
94: - reduce the need for manual reporting
95:
96: #### Product scope
97:
98: - stored balance in the app
99: - clearer balance segmentation and reserve visibility
100: - employer analytics for team performance and commission liability
101: - projections for upcoming payouts
102: - employee insights on earnings pace and history
103: - alerts for anomalies and budget spikes
104: - admin tools for corrections and policy configuration
105:
106: #### Metrics
107:
108: - percent of balances retained in-platform
109: - dashboard usage by employers
110: - frequency of manual interventions
111: - repeat payout behavior per employee
112:
113: ## Card and retention tools
114:
115: ### Months 8-10
116:
117: #### Objectives
118:
119: - make the balance more useful without requiring immediate cash-out
120: - unlock interchange economics
121:
122: #### Product scope
123:
124: - prepaid or debit card issuance through a partner
125: - spend from available balance
126: - card controls and transaction views
127: - balance retention incentives tied to usage, not explicit interest promises
128: - stronger notifications and mobile experience
129:
130: #### Metrics
131:
132: - card activation rate
133: - card spend volume
134: - balance retention before and after card launch
135: - support load per active user
136:
137: ## Scale features and controlled advance pilot
138:
139: ### Months 10-12
140:
141: #### Objectives
142:
143: - deepen product value for employers
144: - test a tightly controlled version of advance functionality without becoming credit-led
145:
146: #### Product scope
147:
148: - multi-entity or franchise support
149: - API or integration layer for ERP, CRM, or POS tools
150: - employer cash flow forecasting
151: - pilot of employer-backed advances with strict limits
152: - improved risk rules for refunds, clawbacks, and employee exits
153:
154: #### Metrics
155:
156: - employer expansion within existing accounts
157: - integration adoption
158: - advance usage and repayment behavior
159: - loss or exception rate on pilot advances
160:
161: ## What should stay out of scope in year one
162:
163: - standalone consumer lending
164: - full payroll replacement
165: - broad international expansion
166: - feature-heavy consumer banking experience
167: - deep CRM functionality
168:
169: ## Year-one product philosophy
170:
171: The roadmap should stay disciplined.
172:
173: - build the commission ledger first
174: - prove instant access to earned money second
175: - add retention tools third
176: - add credit only after the company has the data and controls to support it
177:
178: ## Recommended milestone sequence
179:
180: - prove employer demand for payment-linked commission automation
181: - prove worker demand for instant access to eligible balances
182: - prove safe operating rules around reversals and disputes
183: - prove that analytics improves employer retention
184: - prove that cards increase balance retention
185: - only then test employer-backed advance products
(End of file - total 185 lines)
</content>
Tool: webfetch
Input:
{
"url": "https://zrobank.com/en",
"format": "markdown",
"timeout": 60
}
Output:
Z.ro BankZro
[](/en)
[Home](/en)[About Us](/en/quem-somos)
Services
[Local Payments](/en/servicos/pagamentos-locais)[Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)[Cryptocurrencies](/en/servicos/criptomoedas)[Financial Infratech](/en/servicos/infratech-financeira)
Countries
[Brazil](/en/paises/brasil)[Argentina](/en/paises/argentina)[Chile](/en/paises/chile)[Peru](/en/paises/peru)
[Developers](https://coinwise-io.github.io/zrobank-doc-api/)[Contact](/en#contact)
[Access your Account](https://internet-banking.zrobank.com.br/auth/login)
---
en
## The evolution
of global
payments starts here
Welcome to the first developer-first bank, with open APIs for your company to plug in and customize your way.
[Contact Us](/en#contact)
## See how
Z.ro can evolve
your business now
Local Payments
Integrate with the main payment methods.
Cross-Border
Cryptocurrencies
Banking
## Who is Z.ro for?
Integrate with the main payment methods.
### Companies
#### E-commerce
#### Online Travel Agencies
#### Online Gaming
#### Digital Content Production
#### Sports Betting
#### Financial Services
#### Streaming
#### Other Companies
#### Marketplaces
#### Subscription Services
## Partners
### Fintechs
Enjoy the best Bank as a Service infrastructure
### Payment Providers
Become an indirect participant of Z.ro
### ERP
Customize payment journeys and add revenue to your business
### Digital Platforms
Add the best payment methods
## Become a referred business partner
We certify your company to represent us in various countries. Be a trusted consultant, with our endorsement and support, wherever you are, so we can grow together.
## Why Z.ro?
### Technology, scale and precision
- #### $10 billion
transacted (in local currencies)
- #### 100 million
transactions
- #### 50 thousand
payments per minute at daily peaks
- #### 1 million
app downloads
- #### 99.98%
conversion rate
### Credibility and trust
- #### 150
employees in 4 countries
- #### A-level company
in the Central Bank of Brazil ranking
- #### Ernst & Young and KPMG
Audited by
- #### Multinvest Capital
Invested by
- #### Endeavor, Visa, BID and Itaú
Accelerated by
## In the media
Z.ro Bank launches international payments with crypto assets following Central Bank regulation
[Read Article](https://www1.folha.uol.com.br/colunas/painelsa/2025/12/zro-bank-lanca-pagamentos-internacionais-com-criptoativos-apos-regulacao-do-bc.shtml)
Fintech launches robot that buys tickets and places bets
[Read Article](https://www1.folha.uol.com.br/colunas/painelsa/2025/03/fintech-lanca-robo-que-compra-ingressos-e-faz-apostas.shtml)
Zro Bank obtains a payment institution license
[Read Article](https://valor.globo.com/financas/noticia/2024/07/24/zro-bank-obtm-licena-de-instituio-de-pagamento.ghtml)
Brazilian bank combining the real and cryptocurrencies receives a R$25 million investment
[Read Article](https://exame.com/future-of-money/banco-brasileiro-que-une-real-e-criptomoedas-recebe-aporte-de-r25-milhoes/)
This Recife-based business has already processed R$45 billion and now aims to take Pix to the world
[Read Article](https://exame.com/negocios/este-negocio-de-recife-ja-processou-r-22-bilhoes-e-agora-quer-levar-o-pix-para-o-mundo/)
Zro Bank, of cryptocurrencies, will receive a contribution of up to R$ 61 million
[Read Article](https://valor.globo.com/financas/noticia/2021/10/19/zro-bank-de-criptomoeda-recebe-aporte-de-r-61-mi.ghtml)
Multicurrency chatbank, Zro Bank wants to be the Brazilian WeChat
[Read Article](https://forbes.com.br/forbes-money/2021/01/chatbank-multimoeda-zro-bank-quer-ser-o-wechat-brasileiro/)
Brazilian fintech Z.ro Bank expands into Latin America
[Read Article](https://www.estadao.com.br/economia/coluna-do-broad/fintech-brasileira-zro-bank-expande-para-america-latina)
## Contact Us
Subject
By continuing, you allow Z.ro Bank to contact you through the provided channels.
Send
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
#### Services
- [Local Payments](/en/servicos/pagamentos-locais)
- [Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)
- [Cryptocurrencies](/en/servicos/criptomoedas)
- [Financial Infratech](/en/servicos/infratech-financeira)
- [Digital Account](/en/paises/brasil#digital-account)
#### Countries
- [Brazil](/en/paises/brasil)
- [Argentina](/en/paises/argentina)
- [Chile](/en/paises/chile)
- [Peru](/en/paises/peru)
#### Transparency
- [Ethics and Compliance](/en/transparencia#ethics-and-compliance)
- [Privacy Policy](/en/politicas-de-privacidade)
- [Terms of Use](/en/termos-de-uso)
- [Reporting Channel Policy](/en/politicas-canal-denuncias)
[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)[](https://apps.apple.com/br/app/zro-bank-multimoedas/id1528780452)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
Assistant (Plan · GPT-5.4 · 18.6s)
Thinking:
Researching Z.ro documentation
I need to dive into the Z.ro documentation to tailor it for our startup launch. Using webfetch on their docs site seems essential, potentially involving both the browser and webfetch tools. Since it could be a GitHub Pages site, I should check if the open API spec is available. I might ask clarifying questions, but I can likely move forward. I’ll categorize what Z.ro covers, what we still need to build, and what we need to confirm with them. Using todowrite might help, but it might not be necessary yet.
Pulling the developer docs and the Brazil/product-specific pages next so I can separate what Z.ro can handle for us from what we still need to build ourselves.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/",
"format": "markdown",
"timeout": 60
}
Output:
Z.ro Bank | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
# Z.ro Bank
Documentation
[Get Started](/overview/introduction)
### Pix as a Service
Send and receive instant payments through our Pix API, quickly and safely.
[See more](/paas/api-overview/introduction)
### Zro Gateway
Manage your wallets, track your transactions, and enjoy availability across multiple banks with the lowest fees.
[See more](/gateway/api-overview/introduction)
### Crypto as a Service
Increase liquidity in your operations and offer your customers the most popular cryptocurrencies on your website or app, using our Crypto API.
[See more](/caas/api-overview/introduction)
### Payments Gateway
Accept card payments with agility and security through our Payments Gateway API, enabling seamless integration for in-person and online transactions.
[See more](https://docs-international.zrobank.io)
Customer support: alo@zrobank.com.br | LGPD: dpo.zro@zrobank.com.br | CNPJ: 26.264.220/0001-16
[](https://www.linkedin.com/company/zrobank)[](https://www.instagram.com/zrobank)
Tool: webfetch
Input:
{
"url": "https://zrobank.com/en/paises/brasil",
"format": "markdown",
"timeout": 60
}
Output:
Z.ro BankBrazil - Zro
[](/en)
[Home](/en)[About Us](/en/quem-somos)
Services
[Local Payments](/en/servicos/pagamentos-locais)[Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)[Cryptocurrencies](/en/servicos/criptomoedas)[Financial Infratech](/en/servicos/infratech-financeira)
Countries
[Brazil](/en/paises/brasil)[Argentina](/en/paises/argentina)[Chile](/en/paises/chile)[Peru](/en/paises/peru)
[Developers](https://coinwise-io.github.io/zrobank-doc-api/)[Contact](/en/paises/brasil#contact)
[Access your Account](https://internet-banking.zrobank.com.br/auth/login)
---
en
# See what Z.ro offers to help your business take off in Brazil.
### Pix
Send and receive Pix at hyperscale, automating your payment flows.
### Exchange (eFX)
Process local payments and automatically close currency exchange for international transfers.
### Other Payments
Accept credit cards, debit cards, and various digital wallets, with just one connection.
### Cryptocurrencies
Pay, receive, and make instant conversions of over 100 cryptocurrencies.
### Specialists
in what we do
- #### 50 billion
Reais transacted
- #### 100 million
transactions
- #### 50 thousand
transactions per minute at daily peaks
- #### 1 million
app downloads
- #### 99.98%
conversion rate
### Credibility
and trust
- #### A-level company
in the Central Bank of Brazil ranking
- #### Ernst & Young and KPMG
Audited by
- #### Multinvest Capital
Invested by
- #### Endeavor, Visa, BID and Itaú
Accelerated by
- #### 150
employees in 4 countries
## Partners
### Fintechs
Enjoy the best Bank as a Service infrastructure
### Payment Providers
Become an indirect participant of Z.ro
### ERP
Customize payment journeys and add revenue to your business
### Digital Platforms
Add the best payment methods
## For your company
#### Integrate our API into your system and automate your financials
#### Send and receive payments via Pix at hyperscale
#### Reduce fraud with our security layers
#### Schedule automatic refunds and returns
#### Program slips upon receiving via Pix for as many accounts as you want
#### Start issuing static and dynamic QR Codes
#### Track all your operations in real-time
#### Receive Webhook notifications for all operations
#### Reconcile your payments quickly and simply
#### Make scheduled Pix, reducing costs with automatic debit
## For you
### Multi-currency digital account
At Z.ro, you have a free digital account, with a VISA debit card and cryptocurrency conversion, all in one place. It's like an Exchange, but inside your bank.
## Contact Us
Subject
By continuing, you allow Z.ro Bank to contact you through the provided channels.
Send
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
#### Services
- [Local Payments](/en/servicos/pagamentos-locais)
- [Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)
- [Cryptocurrencies](/en/servicos/criptomoedas)
- [Financial Infratech](/en/infratech-financeira)
- [Digital Account](/en/paises/brasil#digital-account)
[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)[](https://apps.apple.com/br/app/zro-bank-multimoedas/id1528780452)
#### Transparency
- [Privacy Policy](/en/politicas-de-privacidade)
- [Security policy](/en/politicas-de-seguranca)
- [Terms of Use](/en/termos-de-uso)
- [Reporting Channel Policy](/en/politicas-canal-denuncias)
#### Regulatory
- [Ethics and Compliance](/en/transparencia#ethics-and-compliance)
- [Whistleblowing channel](/en/transparencia#reporting-channel)
- [Scam manual](https://drive.google.com/file/d/1kRNIA23YYz_8r3y9tZ9okeEZX3D8UGEc/view)
- [Risk manual](/en/manual-de-gerenciamento-do-risco-de-liquidez)
#### Support
#### SAC
- [\[email protected\]](/cdn-cgi/l/email-protection#4f222a2e253a2b2e0f353d202d2e2124612c2022612d3d)
- [(11) 5043-6444](tel:1150436444)
[Customer support](/en/ouvidoria)
#### LGPD (Marcelo Bueno Carneiro)
- [\[email protected\]](/cdn-cgi/l/email-protection#b3d7c3dc9dc9c1dcf3c9c1dcd1d2ddd89dd0dcde9dd1c1)
[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
Tool: webfetch
Input:
{
"url": "https://zrobank.com/en/servicos/infratech-financeira",
"format": "markdown",
"timeout": 60
}
Output:
Z.ro BankFinancial Infratech - Zro
[](/en)
[Home](/en)[About Us](/en/quem-somos)
Services
[Local Payments](/en/servicos/pagamentos-locais)[Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)[Cryptocurrencies](/en/servicos/criptomoedas)[Financial Infratech](/en/servicos/infratech-financeira)
Countries
[Brazil](/en/paises/brasil)[Argentina](/en/paises/argentina)[Chile](/en/paises/chile)[Peru](/en/paises/peru)
[Developers](https://coinwise-io.github.io/zrobank-doc-api/)[Contact](/en/servicos/infratech-financeira#contact)
[Access your Account](https://internet-banking.zrobank.com.br/auth/login)
---
en
# Enjoy the entire infrastructure of Latin America's first developer-first bank.
All our open APIs for your company to plug in and customize. Your way.
### Fintechs
Enjoy our Bank as a Service infrastructure
### Payment Providers
Become an indirect participant
### ERP
Create payment journeys and add revenue to your business
### Digital Platforms
Add the best payment methods
### Backoffice
Manage your sub-account ecosystem with all the features and reports needed for your business to grow.
### Payment Gateway
Offer various payment methods connected in a single gateway.
### Internet Banking
Provide a complete Banking platform for your stakeholders.
### White-label Application
Personalize and adapt our Bank's application for your customers with your brand.
## Contact Us
Subject
By continuing, you allow Z.ro Bank to contact you through the provided channels.
Send
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
#### Services
- [Local Payments](/en/servicos/pagamentos-locais)
- [Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)
- [Cryptocurrencies](/en/servicos/criptomoedas)
- [Financial Infratech](/en/servicos/infratech-financeira)
- [Digital Account](/en/paises/brasil#digital-account)
#### Countries
- [Brazil](/en/paises/brasil)
- [Argentina](/en/paises/argentina)
- [Chile](/en/paises/chile)
- [Peru](/en/paises/peru)
#### Transparency
- [Ethics and Compliance](/en/transparencia#ethics-and-compliance)
- [Privacy Policy](/en/politicas-de-privacidade)
- [Terms of Use](/en/termos-de-uso)
- [Reporting Channel Policy](/en/politicas-canal-denuncias)
[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)[](https://apps.apple.com/br/app/zro-bank-multimoedas/id1528780452)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
Tool: webfetch
Input:
{
"url": "https://zrobank.com/en/servicos/pagamentos-locais",
"format": "markdown",
"timeout": 60
}
Output:
Z.ro BankLocal Payments - Zro
[](/en)
[Home](/en)[About Us](/en/quem-somos)
Services
[Local Payments](/en/servicos/pagamentos-locais)[Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)[Cryptocurrencies](/en/servicos/criptomoedas)[Financial Infratech](/en/servicos/infratech-financeira)
Countries
[Brazil](/en/paises/brasil)[Argentina](/en/paises/argentina)[Chile](/en/paises/chile)[Peru](/en/paises/peru)
[Developers](https://coinwise-io.github.io/zrobank-doc-api/)[Contact](/en/servicos/pagamentos-locais#contact)
[Access your Account](https://internet-banking.zrobank.com.br/auth/login)
---
en
# One integration, multiple possibilities
Scale your business with the main payment methods. All with centralized management on a platform awarded as the best technological solution in the Latin American financial market.
## Much more than credit and debit cards
Receive payments through digital wallets as well and convert many more sales, allowing your customer to pay how they want.
## Discover the solutions only Z.ro offers for your company
### Conversion
Convert more of your sales, with our APIs that guarantee an average conversion rate of 99.8%
### Scale
We grow exponentially together. Our platform has record peaks of 50,000 transactions per minute to sustain your sales peaks.
### Monitoring
Manage your business through our specialized dashboards for your segment.
### Control
Automatic reconciliation and personalized reports for your company.
### Conversion
Convert more of your sales, with our APIs that guarantee an average conversion rate of 99.8%
### Scale
We grow exponentially together. Our platform has record peaks of 50,000 transactions per minute to sustain your sales peaks.
### Monitoring
Manage your business through our specialized dashboards for your segment.
### Control
Automatic reconciliation and personalized reports for your company.
## Contact Us
Subject
By continuing, you allow Z.ro Bank to contact you through the provided channels.
Send
[](https://www.linkedin.com/company/zrobank/)[](https://www.instagram.com/zrobank/)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
#### Services
- [Local Payments](/en/servicos/pagamentos-locais)
- [Cross-border Payments (eFX)](/en/servicos/pagamentos-cross-border)
- [Cryptocurrencies](/en/servicos/criptomoedas)
- [Financial Infratech](/en/servicos/infratech-financeira)
- [Digital Account](/en/paises/brasil#digital-account)
#### Countries
- [Brazil](/en/paises/brasil)
- [Argentina](/en/paises/argentina)
- [Chile](/en/paises/chile)
- [Peru](/en/paises/peru)
#### Transparency
- [Ethics and Compliance](/en/transparencia#ethics-and-compliance)
- [Privacy Policy](/en/politicas-de-privacidade)
- [Terms of Use](/en/termos-de-uso)
- [Reporting Channel Policy](/en/politicas-canal-denuncias)
[](https://play.google.com/store/apps/details?id=br.com.zrobank.app&hl=pt_BR)[](https://apps.apple.com/br/app/zro-bank-multimoedas/id1528780452)
[](https://www.instagram.com/zrobank/)[](https://www.linkedin.com/company/zrobank/)
Assistant (Plan · GPT-5.4 · 18.7s)
Thinking:
Understanding service requirements
I need to get a clear picture of the services available. It seems like for the MVP with Z.ro, we require certain APIs, modules, and contractual setups. I'll have to check the API documentation for details on authentication, entities, and endpoints.
It's also essential to find out if they support features like webhooks, KYC, and payment gateways. I might need to do a parallel webfetch on specific documentation pages to gather all necessary information. Let’s explore those docs!
Thinking:
Exploring API documentation needs
I need to identify specific API documentation pages for auth, webhooks, and services like Pix for cash transactions and wallets. Since the user is asking for exact requirements, I should create a thorough mapping.
I'll look at the site structure of the documentation, potentially using webfetch or GitHub insights since they’re on GitHub Pages. I might fetch the sitemap or simply inspect the navigation through the browser to know what paths I need to follow. This way, I can gather all necessary information.
Looking into the actual API docs now to identify the concrete modules, auth model, and operational pieces we would need to contract or build around.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/overview/introduction",
"format": "markdown",
"timeout": 60
}
Output:
Introduction | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [Overview](/overview/introduction)
- [Introduction](/overview/introduction)
- [Security](/overview/security)
- [Environments](/overview/environments)
- [Support](/overview/support)
- [](/)
- Overview
- Introduction
# Introduction
Welcome to Z.ro Bank!
Here you'll find all the information you must have to integrate with Z.ro Bank and our API endpoints. We've tried to build this documentation as user-friendly as possible, creating a simple and gentle experience for you.
# Overview
Z.ro Bank is a Brazilian digital bank and cryptocurrency exchange based on blockchain technology. We build financial services for customers and their businesses using proprietary technology.
**Z.RO FOR BUSINESS** \- Made for your company
For institutional clients, we build all crypto and payments infrastructure using the best practices and technology available. Count on us to always deliver the software your company needs to reach its full potential.
# What is Pix?
Pix is a new instant payment system that was launched in Brazil, November 2020. This system allows individuals and businesses to make instant money transfers through a mobile app or online banking platform. The main advantage of Pix is that it is available 24/7, including holidays, and the transactions are processed instantly.
One of the benefits of Pix is that it is a cheaper and faster alternative to traditional payment methods, such as bank transfers, and credit cards. There are no fees for individuals and small businesses to use Pix. Large businesses may incur fees depending on the volume of transactions.
On our Pix as a Service API, you can send and receive money by a Pix Key, dynamic QR code or bank account.
The Pix payment system, through Pix keys, works by allowing users to link a unique identification process, such as a phone number, email address, document number or random key, to their bank account. When making a payment, the user simply provides a Pix key instead of bank account information. Pix dynamic QR code works by allowing the payer to scan or copy the QR code created by the merchant or service provider. The QR code contains information such as the payment amount and the recipient’s account details. The use of dynamic QR codes allows for greater security and flexibility in payments, as the code is generated for each individual transaction, reducing the risk of fraudulent activity. In order to receive a Pix Payment, if you didn’t register a pix key, you can use your bank account information on Pix. You can use the data that is usually provided by a traditional bank, the money will then be credited to the recipient’s account instantly as a Pix Payment.
You can find more information on Pix on Central Bank FAQ section on its website [https://www.bcb.gov.br/en/financialstability/pixfaqen](https://www.bcb.gov.br/en/financialstability/pixfaqen)
# Questions?
It’s always a pleasure to help you! If you require assistance with the integration or have any questions, please feel free to use our documentation and do not hesitate to [contact us](/overview/support).
[
Next
Security
](/overview/security)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/paas/api-overview/introduction",
"format": "markdown",
"timeout": 60
}
Output:
Introduction | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/paas/api-overview/introduction)
- [Introduction](/paas/api-overview/introduction)
- [Authentication](/paas/api-overview/authentication)
- [Protocol](/paas/api-overview/protocol)
- [Idempotence](/paas/api-overview/idempotence)
- [Rate Limiting](/paas/api-overview/rate-limiting)
- [Request ID (Nonce)](/paas/api-overview/request-id)
- [Serialization](/paas/api-overview/serialization)
- [Replay Protection](/paas/api-overview/replay)
- [Pagination](/paas/api-overview/pagination)
- [API Responses](/paas/api-overview/api-responses)
- [Changelog](/paas/api-overview/changelog)
- [Webhooks](/paas/api-overview/webhooks)
- [Endpoints](/paas/endpoints/zro-global-paas-api)
- [](/)
- API Overview
- Introduction
On this page
# Introduction
Welcome to the Z.ro Bank Pix-as-a-Service (PaaS) API documentation. Our API provides a comprehensive set of endpoints to enable developers to build powerful applications that interact with our technology.
This documentation provides all the necessary information to help you integrate with our API seamlessly. So let's get started and explore the exciting world of Pix with our Z.ro Bank PaaS API.
## API ID and API Key Setup[](#api-id-and-api-key-setup "Direct link to API ID and API Key Setup")
Once your `API ID` and `API Key` are created, you are ready to start the integration.
- If you have not registered your company yet, please access: [Register to Z.ro Bank PaaS API](https://docs.google.com/forms/d/e/1FAIpQLSdMHWF1sZm7jjSsKiYGZIcd7sN2vCwx_OH5Eh3W1X8n7wS6ug/viewform)
- If you have already registered your company, but your credentials were not provided yet, please contact our [support team](/overview/support).
> Note: Never share your `API ID` and `API Key` to anyone. If you have accidentally shared, please contact our [support team](/overview/support) immediately.
## API Base URLs[](#api-base-urls "Direct link to API Base URLs")
- **Test environment:** [](https://paas-hml.zrobank.xyz/api)[https://paas-hml.zrobank.xyz/api](https://paas-hml.zrobank.xyz/api)
[
Next
Authentication
](/paas/api-overview/authentication)
- [API ID and API Key Setup](#api-id-and-api-key-setup)
- [API Base URLs](#api-base-urls)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/api-overview/introduction",
"format": "markdown",
"timeout": 60
}
Output:
Introduction | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Introduction](/baas/api-overview/introduction)
- [Authentication](/baas/api-overview/authentication)
- [Protocol](/baas/api-overview/protocol)
- [Idempotence](/baas/api-overview/idempotence)
- [Rate Limiting](/baas/api-overview/rate-limiting)
- [Request ID (Nonce)](/baas/api-overview/request-id)
- [Serialization](/baas/api-overview/serialization)
- [Replay Protection](/baas/api-overview/replay)
- [Pagination](/baas/api-overview/pagination)
- [API Responses](/baas/api-overview/api-responses)
- [Changelog](/baas/api-overview/changelog)
- [Webhooks](/baas/api-overview/webhooks)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- API Overview
- Introduction
On this page
# Introduction
Welcome to the Z.ro Bank Banking-as-a-Service (BaaS) API documentation. Our API provides a comprehensive set of endpoints to enable developers to build powerful applications that interact with our technology.
This documentation provides all the necessary information to help you integrate with our API seamlessly. So let's get started and explore the exciting world of Banking with our Z.ro Bank BaaS API.
## API ID and API Key Setup[](#api-id-and-api-key-setup "Direct link to API ID and API Key Setup")
Once your `API ID` and `API Key` are created, you are ready to start the integration.
- If you have not registered your company yet, please access: [Register to Z.ro Bank BaaS API](https://docs.google.com/forms/d/e/1FAIpQLSdMHWF1sZm7jjSsKiYGZIcd7sN2vCwx_OH5Eh3W1X8n7wS6ug/viewform)
- If you have already registered your company, but your credentials were not provided yet, please contact our [support team](/overview/support).
> Note: Never share your `API ID` and `API Key` to anyone. If you have accidentally shared, please contact our [support team](/overview/support) immediately.
## API Base URLs[](#api-base-urls "Direct link to API Base URLs")
- **Test environment:** [](https://api-baas-hml.zrobank.xyz/api)[https://api-baas-hml.zrobank.xyz/api](https://api-baas-hml.zrobank.xyz/api)
[
Next
Authentication
](/baas/api-overview/authentication)
- [API ID and API Key Setup](#api-id-and-api-key-setup)
- [API Base URLs](#api-base-urls)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/gateway/api-overview/introduction",
"format": "markdown",
"timeout": 60
}
Output:
Introduction | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/gateway/api-overview/introduction)
- [Introduction](/gateway/api-overview/introduction)
- [Authentication](/gateway/api-overview/authentication)
- [Protocol](/gateway/api-overview/protocol)
- [Serialization](/gateway/api-overview/serialization)
- [Errors](/gateway/api-overview/errors)
- [How to use](/gateway/api-overview/how-to-use)
- [API Responses](/gateway/api-overview/api-responses)
- [Duplication Prevention](/gateway/api-overview/duplication-prevention)
- [Changelog](/gateway/api-overview/changelog)
- [Webhooks](/gateway/api-overview/webhooks)
- [Endpoints](/gateway/endpoints/zrobank)
- [](/)
- API Overview
- Introduction
On this page
# Introduction
Welcome to the Z.ro Gateway API documentation. Our API provides a comprehensive set of endpoints to enable developers to build powerful applications that interact with our technology.
This documentation provides all the necessary information to help you integrate with our API seamlessly. So let’s get started and explore the world of payments with our Z.ro Gateway API.
## Authentication[](#authentication "Direct link to Authentication")
There are two types of authentication methods available for the Z.ro Gateway API:
- Using PaaS Token
- Using `x-api-key` (DEPRECATED)
You can see the details of each authentication method at the [Authentication section](/gateway/api-overview/authentication).
## API Base URLs[](#api-base-urls "Direct link to API Base URLs")
- **Test environment:** [](https://payments-api-hml.zrobank.xyz/api/documentation)[https://payments-api-hml.zrobank.xyz/api/documentation](https://payments-api-hml.zrobank.xyz/api/documentation)
[
Next
Authentication
](/gateway/api-overview/authentication)
- [Authentication](#authentication)
- [API Base URLs](#api-base-urls)
Assistant (Plan · GPT-5.4 · 16.4s)
Thinking:
Analyzing Z.ro Bank Services
The user is interested in Z.ro Bank for its service offerings, and I need to review their documentation to see what fits our needs. I plan to dive into their endpoint docs to fully understand their capabilities, inspecting their API lists related to PaaS and BaaS. It’s essential to identify the modules necessary for our launch, including aspects like KYB/KYC support and various payment features. I might also consider using web scraping for a deeper examination of their endpoints.
Thinking:
Examining Z.ro Bank Requirements
I need to pinpoint exact endpoints and requirements like API credentials, onboarding processes, and legal documents. Since we’re in plan mode, using webfetch could help, but the accessible site docs might be sufficient. I plan to inspect endpoint listings for BaaS and PaaS capabilities and review guides. It’s crucial to clarify what we need from Z.ro Bank and what parts we’ll build ourselves. I might highlight any unanswered questions stemming from gaps in the documentation. Let's get into those relevant docs!
Thinking:
Defining PaaS and BaaS Needs
I need to consider PaaS features for things like Pix transactions, QR codes, webhooks, and refunds. A payment gateway might come in handy later if we want card acceptance. I’m also weighing the need for a white-label app and a Visa debit card for future use. It’s essential to find out if BaaS includes debit card issuance or digital accounts. I'll inspect endpoint listings and onboarding guides for insights on bank account management and other functionalities. Let’s gather that information!
I’ve got the high-level product fit. Now I’m checking endpoint coverage and onboarding guides so the recommendation is concrete rather than just “they look compatible.”
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/zro-global-baas-api",
"format": "markdown",
"timeout": 60
}
Output:
Zro Global Baas API | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Introduction
Version: 1.82.0
Export
- [OpenAPI Spec](/specs/baas-spec.json)
# Zro Global Baas API
Zro Global Baas API
## Authentication[](#authentication "Direct link to Authentication")
- HTTP: Bearer Auth
Security Scheme Type:
http
HTTP Authorization Scheme:
bearer
Bearer format:
JWT
### Contact
Z.ro Bank: [tecnologia@zrobank.com.br](mailto:tecnologia@zrobank.com.br)URL: [https://www.zrobank.com.br](https://www.zrobank.com.br)
### License
[All rights reserved](https://www.zrobank.com.br)
[
Previous
Natural Person Onboarding
](/baas/guides/natural-person-onboarding)[
Next
Create Access Token for Login
](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/paas/endpoints/zro-global-paas-api",
"format": "markdown",
"timeout": 60
}
Output:
Zro Global Paas API | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/paas/api-overview/introduction)
- [Endpoints](/paas/endpoints/zro-global-paas-api)
- [Introduction](/paas/endpoints/zro-global-paas-api)
- [Authentication](/paas/endpoints/login-auth-rest-controller-execute)
- [Pix | Keys](/paas/endpoints/get-all-pix-key-rest-controller-execute)
- [Pix | Keys | Dynamic QR Code](/paas/endpoints/create-qr-code-dynamic-instant-billing-rest-controller-execute)
- [Pix | Keys | Static QR Code](/paas/endpoints/get-all-qr-code-static-rest-controller-execute)
- [Split Payments](/paas/endpoints/create-split-pix-qr-code-static-rest-controller-execute)
- [Pix | Payments](/paas/endpoints/v-2-create-decoded-qr-code-rest-controller-execute-v-2)
- [Pix | Devolutions](/paas/endpoints/create-pix-devolution-rest-controller-execute)
- [Pix | Deposits](/paas/endpoints/v-5-get-all-pix-deposit-rest-controller-execute-v-5)
- [Otc | Conversions](/paas/endpoints/v-2-create-conversion-rest-controller-execute-v-2)
- [Quotations | Conversions](/paas/endpoints/v-2-get-quotation-rest-controller-execute-v-2)
- [Operations | Wallets](/paas/endpoints/get-all-wallet-rest-controller-execute)
- [Operations | P2P Transfers](/paas/endpoints/create-p-2-p-transfer-rest-controller-execute)
- [Operations | Wallet Accounts](/paas/endpoints/get-all-wallet-account-rest-controller-execute)
- [Operations | Currency](/paas/endpoints/get-all-currency-rest-controller-execute)
- [Operations | Operation](/paas/endpoints/get-all-operations-rest-controller-execute)
- [Operations | Wallet limits](/paas/endpoints/update-wallet-limit-rest-controller-execute)
- [Banking](/paas/endpoints/v-2-get-all-banking-ted-received-rest-controller-execute-v-2)
- [Banking | Bank Billet | Pix Deposits](/paas/endpoints/create-banking-billet-pix-deposit-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Template](/paas/endpoints/create-banking-billet-pix-deposit-template-rest-controller-execute)
- [Banking | Bank Billet | Payments](/paas/endpoints/get-banking-billet-payment-by-id-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Batch](/paas/endpoints/create-banking-billet-pix-deposit-batch-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Batch Item](/paas/endpoints/create-banking-billet-pix-deposit-batch-item-rest-controller-execute)
- [Utils | User Withdraw Settings](/paas/endpoints/get-all-user-withdraw-setting-rest-controller-execute)
- [Health](/paas/endpoints/health-controller-execute)
- [Reports](/paas/endpoints/v-5-generate-pix-statement-export-rest-controller-execute-v-5)
- [Storage](/paas/endpoints/get-all-files-rest-controller-execute)
- [Users | User Bank Account](/paas/endpoints/get-user-bank-account-by-wallet-rest-controller-execute)
- [Pix | Recurrence](/paas/endpoints/create-pix-recurrence-rest-controller-execute)
- [Pix | Scheduled Payments](/paas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute)
- [Pix | Automatic Receiver Limits](/paas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute)
- [Card](/paas/endpoints/create-virtual-card-rest-controller-execute)
- [Card | Onboarding](/paas/endpoints/get-terms-of-use-rest-controller-execute)
- [Open Finance | Participants](/paas/endpoints/get-all-open-finance-participants-rest-controller-execute)
- [Open Finance | Payment Consents](/paas/endpoints/create-open-finance-payment-consent-by-pix-key-rest-controller-execute)
- [Open Finance | Payments](/paas/endpoints/create-open-finance-payment-rest-controller-execute)
- [Schemas](/paas/endpoints/schemas/authenticaterestrequest)
- [](/)
- Endpoints
- Introduction
Version: 1.82.0
Export
- [OpenAPI Spec](/specs/paas-spec.json)
# Zro Global Paas API
Zro Global Paas API
## Authentication[](#authentication "Direct link to Authentication")
- HTTP: Bearer Auth
Security Scheme Type:
http
HTTP Authorization Scheme:
bearer
Bearer format:
JWT
### Contact
Z.ro Bank: [tecnologia@zrobank.com.br](mailto:tecnologia@zrobank.com.br)URL: [https://www.zrobank.com.br](https://www.zrobank.com.br)
### License
[All rights reserved](https://www.zrobank.com.br)
[
Previous
Webhooks
](/paas/api-overview/webhooks)[
Next
Create Access Token for Login
](/paas/endpoints/login-auth-rest-controller-execute)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/guides/legal-person-onboarding",
"format": "markdown",
"timeout": 60
}
Output:
Legal Person Onboarding | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Legal Person Onboarding](/baas/guides/legal-person-onboarding)
- [Natural Person Onboarding](/baas/guides/natural-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- Guides
- Legal Person Onboarding
On this page
# Legal Person Onboarding
Complete flow for onboarding a Legal Person through the BaaS API.
## Flow Overview[](#flow-overview "Direct link to Flow Overview")
Execute steps 1-7 in order.
---
## Step 1: Create User Account[](#step-1-create-user-account "Direct link to Step 1: Create User Account")
`POST /users/accounts`
Create user account as Legal Person with CNPJ.
**Returns:** `user_id`
---
## Step 2: Create Onboarding[](#step-2-create-onboarding "Direct link to Step 2: Create Onboarding")
`POST /users/onboarding/legal-person`
Create onboarding record with legal person address and revenue.
**Returns:** `onboarding_id` → Save for Steps 6 and 7
**Note:** Cannot create if user has active onboarding (PENDING, IN\_PROCESS, FINISHED). Can create new if previous was REJECTED or FAILED.
---
## Step 3: Create Shareholders[](#step-3-create-shareholders "Direct link to Step 3: Create Shareholders")
`POST /users/shareholders`
Register shareholders. Can be Natural Person (CPF) or Legal Person (CNPJ).
**Returns:** `shareholder_id` → Save for Step 4 (Natural Person shareholders only)
**Requirements:**
- At least one shareholder
- If shareholder is Natural Person (CPF), the `document` must match the legal representative's document created in Step 4
- Legal Person (CNPJ) shareholders do not require a legal representative
- Total `participation_percentage` ≤ 100%
---
## Step 4: Create Legal Representatives[](#step-4-create-legal-representatives "Direct link to Step 4: Create Legal Representatives")
`POST /users/legal-representatives`
Register legal representatives. Must be Natural Person with CPF.
**Requires:** `shareholder_id` from Step 3
**Returns:** `legal_representative_id` → Save for Step 5
**Requirements:**
- Must be Natural Person (CPF)
- Must link to a Natural Person shareholder via `shareholder_id`
- At least one legal representative required
---
## Step 5: Upload Representative Documents[](#step-5-upload-representative-documents "Direct link to Step 5: Upload Representative Documents")
`POST /users/legal-representatives/{id}/documents`
Upload documents for each legal representative (multipart/form-data).
**Required:**
- `selfie` (file)
- `identity_document` (file)
- `identity_document_type` (enum: `id`, `cnh`, `passaporte`)
- `qualification_declaration` (file)
**Optional:**
- `income_declaration` (file)
- `address_proof` (file)
**Requirements:**
- Upload for ALL legal representatives
- Max 25 MB per file
- Formats: PDF, JPEG, JPG, PNG
---
## Step 6: Upload Legal Person Documents[](#step-6-upload-legal-person-documents "Direct link to Step 6: Upload Legal Person Documents")
`POST /users/onboarding/legal-person/{id}/documents`
Upload legal person documents. Call once per document type.
**Body:**
- `file` (binary)
- `type` (enum)
**Required types:**
- `SOCIAL_CONTRACT`
- `BALANCE_SHEET` OR `REVENUE_STATEMENT` (at least one)
**Optional:**
- `KYC_AML_POLICY`
**Requirements:**
- Max 25 MB per file
- Formats: PDF, JPEG, JPG, PNG
---
## Step 7: Finalize[](#step-7-finalize "Direct link to Step 7: Finalize")
`POST /users/onboarding/legal-person/{id}/finalize`
Submit onboarding for processing.
**Returns:** Status changes to `IN_PROCESS`
**Validation:**
- ✓ Onboarding exists and is in PENDING status
- ✓ At least one shareholder created
- ✓ At least one legal representative created
- ✓ All legal representatives are Natural Person
- ✓ All legal representatives linked to Natural Person shareholders
- ✓ All legal representatives have uploaded: selfie, identity\_document, qualification\_declaration
- ✓ Legal person has uploaded: SOCIAL\_CONTRACT
- ✓ Legal person has uploaded: BALANCE\_SHEET or REVENUE\_STATEMENT
- ✓ Total shareholder participation does not exceed 100%
**If validation fails:** Returns `422` with error details. Fix and retry.
After finalization, use the endpoint below to check the onboarding status.
---
## Checking Status[](#checking-status "Direct link to Checking Status")
`GET /users/onboarding/legal-person/{id}`
Use this endpoint to check the current onboarding status.
**Status flow:**
PENDING → IN_PROCESS → FINISHED / REJECTED / FAILED
Status
Meaning
Action
`PENDING`
Incomplete
Complete steps 1-7
`IN_PROCESS`
Processing
Wait
`FINISHED`
Approved
Proceed
`REJECTED`
Not approved
Create new onboarding
`FAILED`
Error
Contact support
**Webhooks:**
If webhooks are configured, you will receive notifications for:
- `FINISHED` - Onboarding approved
- `REJECTED` - Onboarding not approved
Configure webhooks to receive real-time notifications instead of polling this endpoint.
---
## Error Handling[](#error-handling "Direct link to Error Handling")
**422 on finalization:**
- Response contains missing requirements
- Fix and retry
**REJECTED:**
- Create new onboarding with corrected data
**FAILED:**
- Contact support with onboarding ID
[
Previous
Webhooks
](/baas/api-overview/webhooks)[
Next
Natural Person Onboarding
](/baas/guides/natural-person-onboarding)
- [Flow Overview](#flow-overview)
- [Step 1: Create User Account](#step-1-create-user-account)
- [Step 2: Create Onboarding](#step-2-create-onboarding)
- [Step 3: Create Shareholders](#step-3-create-shareholders)
- [Step 4: Create Legal Representatives](#step-4-create-legal-representatives)
- [Step 5: Upload Representative Documents](#step-5-upload-representative-documents)
- [Step 6: Upload Legal Person Documents](#step-6-upload-legal-person-documents)
- [Step 7: Finalize](#step-7-finalize)
- [Checking Status](#checking-status)
- [Error Handling](#error-handling)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/overview/security",
"format": "markdown",
"timeout": 60
}
Output:
Security | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [Overview](/overview/introduction)
- [Introduction](/overview/introduction)
- [Security](/overview/security)
- [Environments](/overview/environments)
- [Support](/overview/support)
- [](/)
- Overview
- Security
On this page
# Security
Our company's culture revolves around prioritizing security, and we have embraced a security-first approach since our inception. Our security philosophy is guided by three core principles:
### Implementing Layered Defense[](#implementing-layered-defense "Direct link to Implementing Layered Defense")
We employ a multi-layered defense strategy to safeguard our systems and data against external threats. This includes using firewalls, intrusion detection systems,encryption, and robust authentication mechanisms. By employing multiple layers of security measures, we create a robust barrier against potential attacks.
### Mitigating Human Error[](#mitigating-human-error "Direct link to Mitigating Human Error")
We recognize that humans can inadvertently introduce vulnerabilities or make mistakes that compromise security. To address this, we prioritize training and awareness programs to educate our employees about best practices and potential risks. Additionally, we implement controls and processes that minimize the impact of human errors, such as implementing access controls, regular audits, and monitoring systems.
### Preventing Insider Misuse[](#preventing-insider-misuse "Direct link to Preventing Insider Misuse")
While we trust our employees, we understand the importance of guarding against insider threats. We strictly control and monitor access privileges to ensure that only authorized individuals have appropriate access to sensitive information. This includes implementing role-based access controls, conducting periodic access reviews, and employing user activity monitoring to detect and prevent any unauthorized or suspicious activities.
### Contact Us[](#contact-us "Direct link to Contact Us")
For more information about our security measures, [contact us](/overview/support) for assistance.
[
Previous
Introduction
](/overview/introduction)[
Next
Environments
](/overview/environments)
- [Implementing Layered Defense](#implementing-layered-defense)
- [Mitigating Human Error](#mitigating-human-error)
- [Preventing Insider Misuse](#preventing-insider-misuse)
- [Contact Us](#contact-us)
Assistant (Plan · GPT-5.4 · 20.6s)
Thinking:
Analyzing Z.ro bank services
I need to address the user's request about Z.ro bank, which seems to offer the services we need. I’ll review their documentation to determine precisely what we should focus on. If necessary, I can ask for clarifications. I aim to assess how their offerings align with our launch requirements, checking details about authentication, webhooks, natural person onboarding, and potential subaccounts. Additionally, I should verify endpoint specifics for various functionalities like payments and onboarding merchant accounts. Using something like the OpenAPI spec might be helpful.
Thinking:
Gathering evidence for user request
I need to gather evidence regarding Z.ro's capabilities. Using an agent might not be necessary, but it could help thoroughly analyze their documentation. For our read-only approach, I should focus on fetching information about natural person onboarding and key endpoints like authentication, webhooks, split payments, user accounts, and card issuance. I need to be careful with how I respond since the user desires clarity. My conclusion should affirm that Z.ro can likely support the regulated requirements for our launch in Brazil.
Thinking:
Defining project requirements
I need to build a commission engine, ledger, employer/employee product, payout policy logic, integrations, support operations, and legal design. For detailed vendor coverage, it's essential to contract with a BaaS API for functionalities like subaccounts, onboarding, bank/wallet accounts, and handling Pix transactions, among other features. I should also consider a PaaS API if we only need Pix without complete account onboarding. Ultimately, I need to decide what exactly we'll require from Z.ro and think this through carefully.
Thinking:
Gathering onboarding specifics
I need to fetch various details related to environments, authentication protocols, idempotence, webhooks, and onboarding for both natural and legal persons. It’s crucial to understand the exact signup flow and relevant endpoint specifics, especially for authentication—which uses API ID/Key to obtain a JWT bearer. I should also look into headers, signatures, and request IDs. Let’s grab documents on auth, protocol, webhooks, and the natural person onboarding guide while we're at it.
Checking the integration mechanics now: auth, webhook model, KYC/KYB flows, and whether their Pix split / account structure matches our commission flow or if we still need our own internal ledger.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/guides/natural-person-onboarding",
"format": "markdown",
"timeout": 60
}
Output:
Natural Person Onboarding | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Legal Person Onboarding](/baas/guides/legal-person-onboarding)
- [Natural Person Onboarding](/baas/guides/natural-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- Guides
- Natural Person Onboarding
On this page
# Natural Person Onboarding
Complete flow for onboarding a Natural Person through the BaaS API.
## Flow Overview[](#flow-overview "Direct link to Flow Overview")
Execute steps 1-3 in order. Step 4 is for checking the result.
---
## Step 1: Create User Account[](#step-1-create-user-account "Direct link to Step 1: Create User Account")
`POST /users/accounts`
Create user account as Natural Person with CPF.
**Returns:** `user_id`
---
## Step 2: Create Onboarding[](#step-2-create-onboarding "Direct link to Step 2: Create Onboarding")
`POST /users/onboardings`
Create onboarding record with user address and personal data.
**Returns:** `onboarding_id` → Save for Steps 3 and 4
**Body (required):**
- `address` (object): `zip_code`, `street`, `number`, `city`, `federative_unit`, `country` (required); `neighborhood`, `complement` (optional)
- `nationality` (string)
- `pep` (boolean)
**Body (optional):**
- `pep_since` (date, format: `YYYY-MM-DD`)
- `occupation_cbo_code` (number)
- `occupation_income` (number, R$ cents)
- `patrimony` (number, R$ cents)
**Note:** Cannot create if user has active onboarding (PENDING, FINISHED). Can create new if previous was REJECTED or FAILED.
---
## Step 3: Upload Documents[](#step-3-upload-documents "Direct link to Step 3: Upload Documents")
`POST /users/onboardings/{id}/documents`
Upload documents (multipart/form-data). Two methods available:
**Method A — Physical document:**
- `selfie` (file, required)
- `document_front` (file, required)
- `document_back` (file, required)
- `document_file_type` (enum: `rg`, `cnh`, required)
**Method B — Digital identity:**
- `selfie` (file, required)
- `document_id` (string, required)
**Optional:**
- `address_proof` (file)
**Requirements:**
- Max 25 MB per file
- Choose one method (A or B), not both
---
## Step 4: Check Status[](#step-4-check-status "Direct link to Step 4: Check Status")
`GET /users/onboardings/{id}`
Use this endpoint to check the current onboarding status.
**Status flow:**
PENDING → FINISHED / REJECTED / FAILED
Status
Meaning
Action
`PENDING`
Awaiting documents or processing
Complete step 3 or wait
`FINISHED`
Approved
Proceed
`REJECTED`
Not approved
Create new onboarding
`FAILED`
Error
Contact support
**Webhooks:**
If webhooks are configured, you will receive notifications for:
- `FINISHED` - Onboarding approved
- `REJECTED` - Onboarding not approved
Configure webhooks to receive real-time notifications instead of polling this endpoint.
---
## Error Handling[](#error-handling "Direct link to Error Handling")
**REJECTED:**
- Create new onboarding with corrected data
**FAILED:**
- Contact support with onboarding ID
[
Previous
Legal Person Onboarding
](/baas/guides/legal-person-onboarding)[
Next
Introduction
](/baas/endpoints/zro-global-baas-api)
- [Flow Overview](#flow-overview)
- [Step 1: Create User Account](#step-1-create-user-account)
- [Step 2: Create Onboarding](#step-2-create-onboarding)
- [Step 3: Upload Documents](#step-3-upload-documents)
- [Step 4: Check Status](#step-4-check-status)
- [Error Handling](#error-handling)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/api-overview/authentication",
"format": "markdown",
"timeout": 60
}
Output:
Authentication | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Introduction](/baas/api-overview/introduction)
- [Authentication](/baas/api-overview/authentication)
- [Protocol](/baas/api-overview/protocol)
- [Idempotence](/baas/api-overview/idempotence)
- [Rate Limiting](/baas/api-overview/rate-limiting)
- [Request ID (Nonce)](/baas/api-overview/request-id)
- [Serialization](/baas/api-overview/serialization)
- [Replay Protection](/baas/api-overview/replay)
- [Pagination](/baas/api-overview/pagination)
- [API Responses](/baas/api-overview/api-responses)
- [Changelog](/baas/api-overview/changelog)
- [Webhooks](/baas/api-overview/webhooks)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- API Overview
- Authentication
On this page
# Authentication
All API requests require HTTP Bearer Authentication security authentication through an **Access Token**.
It is important to note that all API requests must be made via HTTPS, as calls made by simple HTTP will not be accepted. In addition, it is essential that API requests be authenticated, otherwise they will not be successfully executed.
## How to generate a new Access Token?[](#how-to-generate-a-new-access-token "Direct link to How to generate a new Access Token?")
**[To generate a new Access Token](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)**, simply provide your `API ID` and `API Key` in the request body of the `/auth/signin` endpoint. This request will return an Access Token, which is precisely the Bearer Token required for authentication of all requests.
info
If your Access Token stops working or you have accidentally shared it, insert it into the ["Refresh token"](/baas/endpoints/v-1-refresh-token-auth-rest-controller-execute-v-1) endpoint and a new valid Access Token will be returned, ready to be used.
[
Previous
Introduction
](/baas/api-overview/introduction)[
Next
Protocol
](/baas/api-overview/protocol)
- [How to generate a new Access Token?](#how-to-generate-a-new-access-token)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/api-overview/webhooks",
"format": "markdown",
"timeout": 60
}
Output:
Webhooks | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Introduction](/baas/api-overview/introduction)
- [Authentication](/baas/api-overview/authentication)
- [Protocol](/baas/api-overview/protocol)
- [Idempotence](/baas/api-overview/idempotence)
- [Rate Limiting](/baas/api-overview/rate-limiting)
- [Request ID (Nonce)](/baas/api-overview/request-id)
- [Serialization](/baas/api-overview/serialization)
- [Replay Protection](/baas/api-overview/replay)
- [Pagination](/baas/api-overview/pagination)
- [API Responses](/baas/api-overview/api-responses)
- [Changelog](/baas/api-overview/changelog)
- [Webhooks](/baas/api-overview/webhooks)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- API Overview
- Webhooks
On this page
# Webhooks
Your account can be configured so that when certain events occur on your account, a HTTP POST request containing JSON data pertaining to that event is sent to one or more URLs of your choosing. These URLs can be configured inside your settings making a request to our team. Notifications of all events listed below are sent to all the configured URLs.
## Types of webhooks[](#types-of-webhooks "Direct link to Types of webhooks")
Type
Description
PAYMENT
When you send a pix payment.
PAYMENT FAILED
When you send a pix payment and it fails.
DEVOLUTION
When you send a pix devolution.
DEVOLUTION FAILED
When you send a pix devolution and it fails.
DEVOLUTION RECEIVED
When receive a pix devolution.
DEPOSIT
When receive a pix deposit.
ONBOARDING FINISHED
When you create a new user onboarding and it is approved.
ONBOARDING REJECTED
When you create a new user onboarding and it is rejected.
MERCHANT ONBOARDING KYC STATUS
When merchant onboarding KYC status is updated.
WALLET ACCOUNT BALANCE UPDATED
When the balance is updated.
JUDICIAL BLOCK ACCOUNT
When a court order blocks the user's account entirely.
JUDICIAL BLOCK ACCOUNT BALANCE
When a court order blocks a specific amount from the user's account balance.
JUDICIAL UNBLOCK ACCOUNT
When a court order unblocks the user's account.
JUDICIAL UNBLOCK ACCOUNT BALANCE
When a court order releases a previously blocked balance amount.
## Credentials (Not required)[](#credentials-not-required "Direct link to Credentials (Not required)")
Type
Description
Authorization Basic
base64<username:password>
Authorization Bearer
API key or token.
Signature Verification
Shared secret key.
Custom header
Header name is not previous defined , using with api key or token.
mTLS
TLS certificate.
## Payloads (Version 1)[](#payloads-version-1 "Direct link to Payloads (Version 1)")
- Payment
- Payment Failed
- Devolution
- Devolution Failed
- Devolution Received
- Deposit
- Onboarding Finished
- Onboarding Rejected
- Balance updated
- Merchant Onboarding KYC Status
{ "id": "4b344f93-68fb-4ddc-83b4-6288eb7c63ce", "type": "PAYMENT", "end_to_end_id": "E26264220202404171729SrlHOwU3HqB", "txid": null, "operation_id": "0f0aca83-8ea1-5ecb-9fe9-d31782ef06fb", "amount": "270", "owner_name": "Zro Bolsao", "owner_person_type": "CNPJ", "owner_document": "00000000000000", "beneficiary_name": "Name", "beneficiary_person_type": "CPF", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T17:30:00.020Z"}
{ "id": "77198133-185e-4c08-8252-f47c9b15785b", "type": "PAYMENT", "end_to_end_id": "E26264220202404171336mckyTdpt5VZ", "txid": null, "operation_id": null, "amount": "3", "owner_name": "Zro Bolsao", "owner_person_type": "CNPJ", "owner_document": "00000000000000", "beneficiary_name": "Name", "beneficiary_person_type": "CPF", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "error_code": "NOT_ENOUGH_FUNDS", "error_description": "Não há saldo disponível.", "created_at": "2024-04-17T13:36:21.188Z"}
{ "id": "0a1d863e-98bd-49a3-916d-840a1ec0609f", "type": "DEVOLUTION", "end_to_end_id": "D26264220202404171733p6FuxQmuCKp", "operation_id": "fbfe1a0f-011f-5edb-a01d-19e669a6d853", "amount": "270", "owner_name": "Name", "owner_document": "*000000", "owner_bank_ispb": "26264220", "owner_bank_name": "ZRO IP S/A", "beneficiary_name": "Zro Bolsao", "beneficiary_document": "00000000000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T17:33:05.523Z"}
{ "id": "0a1d863e-98bd-49a3-916d-840a1ec0609f", "type": "DEVOLUTION", "end_to_end_id": "D26264220202404171733p6FuxQmuCKp", "operation_id": null, "amount": "270", "owner_name": "Name", "owner_document": "*000000", "owner_bank_ispb": "26264220", "owner_bank_name": "ZRO IP S/A", "beneficiary_name": "Zro Bolsao", "beneficiary_document": "00000000000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "error_code": "AB03", "error_description": "Liquidação da transação interrompida devido a timeout no SPI.", "created_at": "2024-04-17T17:33:05.523Z"}
{ "id": "10b66e97-c747-4dcb-92ad-da1420a0a6b9", "type": "DEVOLUTION_RECEIVED", "end_to_end_id": "D26264220202404171733p6FuxQmuCKp", "txid": null, "operation_id": "fbfe1a0f-011f-5edb-a01d-19e669a6d853", "original_id": "4b344f93-68fb-4ddc-83b4-6288eb7c63ce", "original_end_to_end_id": "E26264220202404171729SrlHOwU3HqB", "amount": "270", "owner_name": "Name", "owner_document": "*000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "beneficiary_name": "Zro Bolsao", "beneficiary_document": "00000000000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T17:33:05.712Z"}
{ "id": "a839f358-0e39-409e-b9a5-5a56b18ba3f2", "type": "DEPOSIT", "end_to_end_id": "E26264220202404171333Hq7F9SWyvUE", "txid": null, "operation_id": "7da84c17-d40c-5bc1-9b69-867d1460736b", "amount": "63", "owner_name": "Zro Bolsao", "owner_document": "00000000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "beneficiary_name": "Name", "beneficiary_account_number": "000000", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T13:33:41.071Z"}
{ "id": "9c4af5a2-6a6b-4e4e-8af8-e03a331b9c5a", "user_id": "c324fb70-db23-482c-a85e-ec3eb58d5941", "type": "ONBOARDING_FINISHED", "name": "John", "full_name": "John Doe", "genre": "M", "mother_name": "Jane Doe", "birth_date": "1984-11-03", "document": "11122233344", "phone_number": "5511955551234", "email": "new-user@zrobank.com.br", "active": true, "person_type": "LEGAL_PERSON", "legal_person_type": "LTDA", "address": { "zip_code": "96075858", "street": "Alameda", "number": 10, "neighborhood": "Alphaville", "city": "São Paulo", "federative_unit": "SP", "country": "Brasil", "complement": "flat 1201" }, "nationality": "Brasileiro", "pep": true, "pep_since": "2015-02-18T18:38:09.412Z", "occupation_cbo_code": 0, "occupation_income": 0, "patrimony": 1299, "failed_code": null, "failed_message": null}
{ "id": "4b344f93-68fb-4ddc-83b4-6288eb7c63ce", "user_id": "a379d727-5409-4b9f-9cae-902aed13efcd", "type": "ONBOARDING_REJECTED", "name": "John", "full_name": "John Doe", "genre": "M", "mother_name": "Jane Doe", "birth_date": "1984-11-03", "document": "11122233344", "phone_number": "5511955551234", "email": "new-user@zrobank.com.br", "active": true, "person_type": "LEGAL_PERSON", "legal_person_type": "LTDA", "address": { "zip_code": "96075858", "street": "Alameda", "number": 10, "neighborhood": "Alphaville", "city": "São Paulo", "federative_unit": "SP", "country": "Brasil", "complement": "flat 1201" }, "nationality": "Brasileiro", "pep": true, "pep_since": "2015-02-18T18:38:09.412Z", "occupation_cbo_code": 0, "occupation_income": 0, "patrimony": 1299, "failed_code": "DOCUMENT_INVALID", "failed_message": "Failed document onboarding."}
{ "id": "d3558873-388a-4a98-a185-578a03bce8e2", "user_id": "9d77c248-c5b5-4f6d-9d12-d1463dc49bd9", "wallet_uuid": "f08e96c8-b659-40bf-a1bd-5225ef4e5632", "wallet_name": "DEFAULT", "operation_id": "cb835846-47b2-4bad-abd3-56e8b0d65ffe", "type": "WALLET_ACCOUNT_BALANCE_UPDATED", "action": "credit", "value": 100, "old_balance": 1000, "new_balance": 1100, "created_at": "2024-06-20T12:34:56.071Z"}
> `action` possible values: `credit` or `debit`.
{ "slug_merchant": "0897A2E2022D4B68AD15DB6204C11BE7", "document_id": "12345678000195", "dt_insert": "2025-02-04T10:30:00Z", "risk_analysis_status": "PENDING", "dt_risk_analysis_status": "2025-02-04T12:00:00Z", "risk_analysis_status_justification": "Documents pending for risk review"}
## Payloads (Version 2)[](#payloads-version-2 "Direct link to Payloads (Version 2)")
- Devolution Received
- Deposit
- Payment Failed
- Devolution Failed
{ "id": "10b66e97-c747-4dcb-92ad-da1420a0a6b9", "type": "DEVOLUTION_RECEIVED", "end_to_end_id": "D26264220202404171733p6FuxQmuCKp", "txid": null, "operation_id": "fbfe1a0f-011f-5edb-a01d-19e669a6d853", "original_id": "4b344f93-68fb-4ddc-83b4-6288eb7c63ce", "original_end_to_end_id": "E26264220202404171729SrlHOwU3HqB", "amount": "270", "owner_name": "Name", "owner_document": "*000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "beneficiary_name": "Name", "beneficiary_account_number": "000000", "beneficiary_branch_number": "0000", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T17:33:05.712Z"}
{ "id": "a839f358-0e39-409e-b9a5-5a56b18ba3f2", "type": "DEPOSIT", "end_to_end_id": "E26264220202404171333Hq7F9SWyvUE", "txid": null, "operation_id": "7da84c17-d40c-5bc1-9b69-867d1460736b", "amount": "63", "owner_name": "Zro Bolsao", "owner_document": "00000000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "beneficiary_name": "Name", "beneficiary_account_number": "000000", "beneficiary_branch_number": "0000", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T13:33:41.071Z"}
{ "id": "77198133-185e-4c08-8252-f47c9b15785b", "type": "PAYMENT_FAILED", "end_to_end_id": "E26264220202404171336mckyTdpt5VZ", "txid": null, "operation_id": null, "amount": "3", "owner_name": "Zro Bolsao", "owner_person_type": "CNPJ", "owner_document": "00000000000000", "beneficiary_name": "Name", "beneficiary_person_type": "CPF", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "error_code": "NOT_ENOUGH_FUNDS", "error_description": "Não há saldo disponível.", "created_at": "2024-04-17T13:36:21.188Z"}
{ "id": "0a1d863e-98bd-49a3-916d-840a1ec0609f", "type": "DEVOLUTION_FAILED", "end_to_end_id": "D26264220202404171733p6FuxQmuCKp", "operation_id": null, "amount": "270", "owner_name": "Name", "owner_document": "*000000", "owner_bank_ispb": "26264220", "owner_bank_name": "ZRO IP S/A", "beneficiary_name": "Zro Bolsao", "beneficiary_document": "00000000000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "error_code": "AB03", "error_description": "Liquidação da transação interrompida devido a timeout no SPI.", "created_at": "2024-04-17T17:33:05.523Z"}
## Payloads (Version 3)[](#payloads-version-3 "Direct link to Payloads (Version 3)")
- Deposit
- Payment Failed
{ "id": "a839f358-0e39-409e-b9a5-5a56b18ba3f2", "type": "DEPOSIT", "end_to_end_id": "E26264220202404171333Hq7F9SWyvUE", "txid": null, "operation_id": "7da84c17-d40c-5bc1-9b69-867d1460736b", "amount": "63", "owner_name": "Zro Bolsao", "owner_document": "00000000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "owner_branch_number": "0000", "owner_account_number": "000000", "beneficiary_name": "Name", "beneficiary_account_number": "000000", "beneficiary_branch_number": "0000", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T13:33:41.071Z"}
{ "id": "77198133-185e-4c08-8252-f47c9b15785b", "type": "PAYMENT_FAILED", "end_to_end_id": "E26264220202404171336mckyTdpt5VZ", "txid": null, "operation_id": null, "amount": "3", "owner_name": "Zro Bolsao", "owner_person_type": "CNPJ", "owner_document": "00000000000000", "beneficiary_name": "Name", "beneficiary_person_type": "CPF", "beneficiary_document": "*000000", "beneficiary_account_type": "CACC", "beneficiary_account_number": "000000", "beneficiary_branch_number": "0000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "error_code": "NOT_ENOUGH_FUNDS", "error_description": "Não há saldo disponível.", "created_at": "2024-04-17T13:36:21.188Z"}
## Payloads (Version 4)[](#payloads-version-4 "Direct link to Payloads (Version 4)")
- Deposit
{ "id": "a839f358-0e39-409e-b9a5-5a56b18ba3f2", "type": "DEPOSIT", "end_to_end_id": "E26264220202404171333Hq7F9SWyvUE", "txid": null, "operation_id": "7da84c17-d40c-5bc1-9b69-867d1460736b", "amount": "63", "owner_name": "Zro Bolsao", "owner_document": "00000000000", "owner_bank_name": "ZRO IP S/A", "owner_bank_ispb": "26264220", "owner_branch_number": "0000", "owner_account_number": "000000", "owner_account_type": "CACC", "beneficiary_name": "Name", "beneficiary_account_number": "000000", "beneficiary_branch_number": "0000", "beneficiary_document": "*000000", "beneficiary_bank_name": "ZRO IP S/A", "beneficiary_bank_ispb": "26264220", "created_at": "2024-04-17T13:33:41.071Z"}
## Judicial Webhooks[](#judicial-webhooks "Direct link to Judicial Webhooks")
Judicial webhooks are triggered by court-ordered operations on user accounts. You can register multiple URLs for the same event type — all registered URLs will receive the notification independently. This is useful if you operate multiple products (e.g., PaaS and Gateway) and need each one to receive the event.
### Payloads (Version 1)[](#payloads-version-1-1 "Direct link to Payloads (Version 1)")
- Judicial Block Account
- Judicial Block Account Balance
- Judicial Unblock Account
- Judicial Unblock Account Balance
Triggered when a court order blocks the user's account entirely.
{ "idJudicialBlockAccount": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "userId": "9d77c248-c5b5-4f6d-9d12-d1463dc49bd9", "accountNumber": "000001", "branchNumber": "0001", "processNumber": "0001234-56.2026.8.26.0100", "courtName": "1ª Vara Cível de São Paulo", "createdAt": "2024-04-17T17:30:00.020Z"}
> `processNumber` and `courtName` are optional — they are only present when provided in the court order.
Triggered when a court order blocks a specific amount from the user's account balance. The `requestedAmount` field is included only when provided by the court order.
{ "idJudicialBlockAccount": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "userId": "9d77c248-c5b5-4f6d-9d12-d1463dc49bd9", "accountNumber": "000001", "branchNumber": "0001", "isTotalValue": false, "requestedAmount": 150000, "processNumber": "0001234-56.2026.8.26.0100", "courtName": "1ª Vara Cível de São Paulo", "createdAt": "2024-04-17T17:30:00.020Z"}
> When `isTotalValue` is `true`, the entire available balance is blocked. `requestedAmount` is optional and only present when informed in the court order. `processNumber` and `courtName` are also optional.
Triggered when a court order lifts a full account block.
{ "idJudicialUnblockAccount": "c3e9b7f1-12ab-4d88-9e4f-1a2b3c4d5e6f", "userId": "9d77c248-c5b5-4f6d-9d12-d1463dc49bd9", "accountNumber": "000001", "branchNumber": "0001", "processNumber": "0001234-56.2026.8.26.0100", "courtName": "1ª Vara Cível de São Paulo", "createdAt": "2024-04-17T17:35:00.020Z"}
> `processNumber` and `courtName` are optional — they are only present when provided in the court order.
Triggered when a court order releases a previously blocked balance amount.
{ "idJudicialUnblockAccount": "c3e9b7f1-12ab-4d88-9e4f-1a2b3c4d5e6f", "userId": "9d77c248-c5b5-4f6d-9d12-d1463dc49bd9", "blockAccountBalanceId": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "accountNumber": "000001", "branchNumber": "0001", "processNumber": "0001234-56.2026.8.26.0100", "courtName": "1ª Vara Cível de São Paulo", "requestedAmount": 150000, "createdAt": "2024-04-17T17:35:00.020Z"}
> `blockAccountBalanceId` references the original `JUDICIAL_BLOCK_ACCOUNT_BALANCE` event that is being released.
[
Previous
Changelog
](/baas/api-overview/changelog)[
Next
Legal Person Onboarding
](/baas/guides/legal-person-onboarding)
- [Types of webhooks](#types-of-webhooks)
- [Credentials (Not required)](#credentials-not-required)
- [Payloads (Version 1)](#payloads-version-1)
- [Payloads (Version 2)](#payloads-version-2)
- [Payloads (Version 3)](#payloads-version-3)
- [Payloads (Version 4)](#payloads-version-4)
- [Judicial Webhooks](#judicial-webhooks)
- [Payloads (Version 1)](#payloads-version-1-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/paas/endpoints/create-split-pix-qr-code-static-rest-controller-execute",
"format": "markdown",
"timeout": 60
}
Output:
Create Split PIX QR Code Static | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/paas/api-overview/introduction)
- [Endpoints](/paas/endpoints/zro-global-paas-api)
- [Introduction](/paas/endpoints/zro-global-paas-api)
- [Authentication](/paas/endpoints/login-auth-rest-controller-execute)
- [Pix | Keys](/paas/endpoints/get-all-pix-key-rest-controller-execute)
- [Pix | Keys | Dynamic QR Code](/paas/endpoints/create-qr-code-dynamic-instant-billing-rest-controller-execute)
- [Pix | Keys | Static QR Code](/paas/endpoints/get-all-qr-code-static-rest-controller-execute)
- [Split Payments](/paas/endpoints/create-split-pix-qr-code-static-rest-controller-execute)
- [Create Split PIX QR Code Static](/paas/endpoints/create-split-pix-qr-code-static-rest-controller-execute)
- [Pix | Payments](/paas/endpoints/v-2-create-decoded-qr-code-rest-controller-execute-v-2)
- [Pix | Devolutions](/paas/endpoints/create-pix-devolution-rest-controller-execute)
- [Pix | Deposits](/paas/endpoints/v-5-get-all-pix-deposit-rest-controller-execute-v-5)
- [Otc | Conversions](/paas/endpoints/v-2-create-conversion-rest-controller-execute-v-2)
- [Quotations | Conversions](/paas/endpoints/v-2-get-quotation-rest-controller-execute-v-2)
- [Operations | Wallets](/paas/endpoints/get-all-wallet-rest-controller-execute)
- [Operations | P2P Transfers](/paas/endpoints/create-p-2-p-transfer-rest-controller-execute)
- [Operations | Wallet Accounts](/paas/endpoints/get-all-wallet-account-rest-controller-execute)
- [Operations | Currency](/paas/endpoints/get-all-currency-rest-controller-execute)
- [Operations | Operation](/paas/endpoints/get-all-operations-rest-controller-execute)
- [Operations | Wallet limits](/paas/endpoints/update-wallet-limit-rest-controller-execute)
- [Banking](/paas/endpoints/v-2-get-all-banking-ted-received-rest-controller-execute-v-2)
- [Banking | Bank Billet | Pix Deposits](/paas/endpoints/create-banking-billet-pix-deposit-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Template](/paas/endpoints/create-banking-billet-pix-deposit-template-rest-controller-execute)
- [Banking | Bank Billet | Payments](/paas/endpoints/get-banking-billet-payment-by-id-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Batch](/paas/endpoints/create-banking-billet-pix-deposit-batch-rest-controller-execute)
- [Banking | Bank Billet | Pix Deposit Batch Item](/paas/endpoints/create-banking-billet-pix-deposit-batch-item-rest-controller-execute)
- [Utils | User Withdraw Settings](/paas/endpoints/get-all-user-withdraw-setting-rest-controller-execute)
- [Health](/paas/endpoints/health-controller-execute)
- [Reports](/paas/endpoints/v-5-generate-pix-statement-export-rest-controller-execute-v-5)
- [Storage](/paas/endpoints/get-all-files-rest-controller-execute)
- [Users | User Bank Account](/paas/endpoints/get-user-bank-account-by-wallet-rest-controller-execute)
- [Pix | Recurrence](/paas/endpoints/create-pix-recurrence-rest-controller-execute)
- [Pix | Scheduled Payments](/paas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute)
- [Pix | Automatic Receiver Limits](/paas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute)
- [Card](/paas/endpoints/create-virtual-card-rest-controller-execute)
- [Card | Onboarding](/paas/endpoints/get-terms-of-use-rest-controller-execute)
- [Open Finance | Participants](/paas/endpoints/get-all-open-finance-participants-rest-controller-execute)
- [Open Finance | Payment Consents](/paas/endpoints/create-open-finance-payment-consent-by-pix-key-rest-controller-execute)
- [Open Finance | Payments](/paas/endpoints/create-open-finance-payment-rest-controller-execute)
- [Schemas](/paas/endpoints/schemas/authenticaterestrequest)
- [](/)
- Endpoints
- Split Payments
- Create Split PIX QR Code Static
# Create Split PIX QR Code Static
POST
## /split-payments/pix/qr-codes/static
**Tag**: api-paas-post-split-payments-pix-qr-codes-static**Description**: Generate a new static QR Code with split payment configuration.
## Request[](#request "Direct link to Request")
### Header Parameters
**x-include-replay-protection-schema** string
The replay-protection-schema allows the user to choose between 3 options:
- If there's no value: The default protection checks that the values in this request are equal: **{ method, params, path, query, body, userId }.** This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and **{ method, params, path, query, body, userId }** value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and **{ method, params, path, query, body, userId }** value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and **{ method, params, path, query, body, userId }** are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**x-transaction-uuid** stringrequired
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
- application/json
### Body
**required**
**key\_id** stringrequired
Associated key ID.
**value** numberrequired
Value in R$ cents.
**summary** string
User friendly static QR Code identifier.
**description** string
User defined payment description.
**expiration\_date** date-time
Expiration date to pay static QR Code. **Max date is 3 months ahead.**
**payable\_many\_times** boolean
If it is true, static QR Code can be paid many times. **When it is false, expiration date is required.**
**merchant\_id** string
User defined payment merchant ID.
**split** objectrequired
**split\_type** stringrequired
**Possible values:** \[`PERCENTUAL`, `ABSOLUTE`\]
Split type (PERCENTUAL or ABSOLUTE).
**accounts** object\[\]required
Array of accounts to receive split payments.
- Array \[
**person\_type** stringrequired
**Possible values:** \[`NATURAL_PERSON`, `LEGAL_PERSON`\]
Person type (NATURAL\_PERSON or LEGAL\_PERSON).
**name** stringrequired
Name of the account holder.
**document** stringrequired
CPF or CNPJ of the account holder.
**bank\_ispb** stringrequired
Bank ISPB code.
**branch** stringrequired
Branch number.
**account\_number** stringrequired
Account number.
**account\_type** stringrequired
**Possible values:** \[`CACC`, `CASH`, `CHAR`, `CISH`, `COMM`, `CPAC`, `LLSV`, `LOAN`, `MGLD`, `MOMA`, `NREX`, `ODFT`, `ONDP`, `OTHR`, `SACC`, `SLRY`, `SVGS`, `TAXE`, `TRAN`, `TRAS`, `CC`, `PG`, `CD`, `CG`, `CI`, `PP`\]
Account type.
**split\_value** numberrequired
Split value. For PERCENTUAL: percentage (0-100). For ABSOLUTE: value in cents.
- \]
## Responses[](#responses "Direct link to Responses")
- 201
- 400
- 401
- 422
The split QR Code returned successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
Split QR Code ID.
**key\_id** stringrequired
Associated key ID.
**state** stringrequired
**Possible values:** \[`PENDING`, `READY`, `ERROR`\]
Split QR Code state.
**summary** string
User defined payment ID.
**description** string
User defined payment description.
**expiration\_date** date-time
Expiration date to pay static QR Code. **When it is false, expiration date is required.**
**created\_at** date-timerequired
Split QR Code created at.
{ "id": "9a1c2d3e-4f56-4789-8abc-def012345678", "key_id": "f6e2e084-29b9-4935-a059-5473b13033aa", "state": "PENDING", "summary": "party-payment", "description": "User defined description", "expiration_date": "2026-04-05T13:55:25.556Z", "created_at": "2026-04-05T13:55:25.556Z"}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Delete Static QR Code
](/paas/endpoints/delete-by-qr-code-static-id-rest-controller-execute)[
Next
Create Decoded QR Code
](/paas/endpoints/v-2-create-decoded-qr-code-rest-controller-execute-v-2)
Assistant (Plan · GPT-5.4 · 18.7s)
Thinking:
Evaluating BaaS and PaaS options
I’m considering how to approach the user's request. We can read documentation pages individually or potentially fetch JSONs. Using webfetch or bash could work. The focus seems to be on understanding whether a BaaS (Backend as a Service) or PaaS (Platform as a Service) is the correct choice for onboarding end users and managing wallets.
It looks like BaaS might be the better option, offering features like onboarding, wallets, and user accounts. PaaS might be more limited in that sense.
Thinking:
Investigating BaaS features
I need to explore the differences regarding x-product-uuid for targeting users. It seems that BaaS allows platforms to operate on users' behalf within products. I might have to understand features like subaccounts, backoffice, and white-label aspects from the website. I wonder if Bely requires configuration through a team instead of an API. I should also inspect the BaaS endpoint documentation to clarify details about user accounts, wallet accounts, and whether employees receive bank accounts or cards.
Thinking:
Inspecting support requirements
I’m thinking that it could be important to ensure that production URLs have the right support. I should confirm the support email and the registration process through the Google Form. Also, it seems there’s no mention of self-service webhook configuration, which I’ll need to request from the team. That definitely feels like a concrete requirement. I’ll take a closer look at the support page to clarify everything.
One more pass on operational details: production access, support path, environment model, and a few user/wallet/card endpoints that affect the exact launch integration shape.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/overview/environments",
"format": "markdown",
"timeout": 60
}
Output:
Environments | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [Overview](/overview/introduction)
- [Introduction](/overview/introduction)
- [Security](/overview/security)
- [Environments](/overview/environments)
- [Support](/overview/support)
- [](/)
- Overview
- Environments
On this page
# Environments
We offer two environments for our API: **Sandbox** and **Production**
## Sandbox Environment[](#sandbox-environment "Direct link to Sandbox Environment")
The Sandbox Environment is designed for integration testing, experimentation, and development purposes. It allows you to test and validate your integrations without affecting your production systems or data.
## Production Environment[](#production-environment "Direct link to Production Environment")
The Production Environment is the live environment where your application interacts with our API in a production-ready manner. It provides stable and secure access to real-time data.
## Contact us[](#contact-us "Direct link to Contact us")
For further information, assistance regarding both environments and pricing details, please contact our [support team](/overview/support)
[
Previous
Security
](/overview/security)[
Next
Support
](/overview/support)
- [Sandbox Environment](#sandbox-environment)
- [Production Environment](#production-environment)
- [Contact us](#contact-us)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/overview/support",
"format": "markdown",
"timeout": 60
}
Output:
Support | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [Overview](/overview/introduction)
- [Introduction](/overview/introduction)
- [Security](/overview/security)
- [Environments](/overview/environments)
- [Support](/overview/support)
- [](/)
- Overview
- Support
# Support
It’s always a pleasure to help you! If you require assistance with the integration or have any questions, please feel free to use our documentation and do not hesitate to contact us by:
- Support Email: [meajuda@zrobank.com.br](mailto:meajuda@zrobank.com.br)
If you have a commercial request or issue, please contact us by:
- Commercial Email: [comercial@zrobank.com.br](mailto:comercial@zrobank.com.br)
[
Previous
Environments
](/overview/environments)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
Create Virtual Card | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Create Virtual Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [List all cards](/baas/endpoints/v-1-get-all-cards-rest-controller-execute-v-1)
- [Unblock Card](/baas/endpoints/v-1-unblock-card-rest-controller-execute-v-1)
- [Block Card](/baas/endpoints/v-1-block-card-rest-controller-execute-v-1)
- [Card details](/baas/endpoints/v-1-card-details-rest-controller-execute-v-1)
- [Cancel Card](/baas/endpoints/v-1-cancel-card-rest-controller-execute-v-1)
- [Create Physical Card](/baas/endpoints/v-1-create-physical-card-rest-controller-execute-v-1)
- [Activate Card](/baas/endpoints/v-1-activate-card-rest-controller-execute-v-1)
- [Issue a Replacement Physical Card](/baas/endpoints/v-1-create-new-physical-card-via-rest-controller-execute-v-1)
- [Change Card Password](/baas/endpoints/v-1-change-card-password-rest-controller-execute-v-1)
- [Get Card Tracking](/baas/endpoints/v-1-get-card-tracking-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Card
- Create Virtual Card
# Create Virtual Card
POST
## /v1/cards/virtual
**Tag**: api-baas-post-virtual-card**Description**: Create a new virtual card.
## Request[](#request "Direct link to Request")
### Header Parameters
**x-transaction-uuid** stringrequired
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
## Responses[](#responses "Direct link to Responses")
- 201
- 400
- 401
- 422
Virtual card created.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
Card ID.
**is\_virtual** booleanrequired
Is Virtual Card.
**status** stringrequired
**Possible values:** \[`password_locked`, `activated`, `pending`, `blocked`, `cancelled`, `preventive_blocked`\]
Card Status.
{ "id": "f6e2e084-29b9-4935-a059-5473b13033aa", "is_virtual": true, "status": "blocked"}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Get Company Registration by ID.
](/baas/endpoints/v-1-get-company-registration-by-id-rest-controller-execute-v-1)[
Next
List all cards
](/baas/endpoints/v-1-get-all-cards-rest-controller-execute-v-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
List User Bank Account | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [List User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Users | User Bank Account
- List User Bank Account
# List User Bank Account
GET
## /v1/users/banking/accounts
Retrieve a user bank account.
## Request[](#request "Direct link to Request")
### Header Parameters
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
## Responses[](#responses "Direct link to Responses")
- 200
- 400
- 401
- 422
The user bank account returned successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
User bank account ID.
**user\_id** stringrequired
User UUID.
**user\_document** stringrequired
User document.
**onboarding\_id** stringrequired
Onboarding UUID.
**account\_number** stringrequired
Account number.
**branch\_number** stringrequired
Branch number.
**active** booleanrequired
User bank account is active.
**default** booleanrequired
User bank account default flag.
**created\_at** date-timerequired
User bank account created at.
{ "id": "f6e2e084-29b9-4935-a059-5473b13033aa", "user_id": "caff7d9f-b554-4978-b87d-717a4115a7a8", "user_document": "84411010003", "onboarding_id": "79ffc231-d5b5-4e84-9384-4b9ce5d36a9c", "account_number": "123456", "branch_number": "0001", "active": true, "default": false, "created_at": "2026-03-26T14:02:59.126Z"}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Update User Account by ID
](/baas/endpoints/v-2-update-user-account-rest-controller-execute-v-2)[
Next
List Legal Person Onboardings
](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
Assistant (Plan · GPT-5.4 · 57.2s)
Thinking:
Verifying onboarding details
I need to consider using webfetch for certain endpoints to confirm if merchant onboarding exists, especially for split and card onboarding. It feels like I might require more details on the merchant onboarding process. I wonder if I have enough information already. I guess when I think about “exactly what we need,” it really means having all the required information from our side to get started. So, let's ensure I get that clarified!
Thinking:
Creating an onboarding checklist
I think we should create a detailed checklist for our processes. For commercial and contracting steps, I need to register the company for BaaS and PaaS API using a Google form, obtain API ID and key for both sandbox and production, and define product details and webhook URLs. I also need to confirm pricing and settlement models, and sign necessary agreements.
For employer and employee onboarding via BaaS, I’ll outline specific legal steps and required documents. Lastly, I need to set up financial flows, like using Pix keys for collections and payments.
Thinking:
Evaluating banking solutions
I'm considering the need for regulated accounts and wallets for employers and employees, and it looks like BaaS will be our main focus. PaaS might suffice if we only have one master merchant, but since we need to onboard both legal and natural persons into bank-like accounts, BaaS feels necessary. We might also need Gateway for card processing and local payment methods beyond Pix. For version one, leading with a BaaS/PaaS approach, primarily using Pix for commissions, seems like a solid plan.
Thinking:
Exploring PaaS vs. BaaS
I'm thinking about whether we really need PaaS, especially if there's a simpler solution available or if we want a split payment feature. It seems important to examine the overlap between BaaS and PaaS to avoid duplicating features. I want to ensure that we’re making the most efficient choice based on our specific needs while balancing functionality. So, I’m diving deeper to understand what each service truly brings to the table.
Thinking:
Analyzing payment systems
I'm looking into various payment systems like Pix Keys, Payments, and Deposits. PaaS seems to have a split QR feature, while BaaS likely encompasses managed accounts and wallets. I think if we require direct splits during collection, the static split QR could work, but it's not robust enough for customizing rules like holdbacks or partial releases. Dynamic splits aren’t clear either. Our method will focus on depositing into partner accounts and calculating splits internally, so direct splits might be limited. I should consider reviewing the OpenAPI spec for specifics.
Thinking:
Reviewing payment integration options
I think I need to consider not just documentation but also public site claims regarding local payments, including credit/debit, digital wallets, and back-office solutions. For our purposes, we’re primarily focused on local Pix and BaaS, so we might ignore crypto and cross-border options for the initial version due to regulatory complexity. It could be wise to check merchant onboarding since employers might need it to accept card payments, even if we initially integrate with their existing processors. I'll look into the merchant onboarding documentation for clarity.
Thinking:
Clarifying payment requirements
The user asked me to review the documentation to determine our specific needs. These requirements depend on whether we're using Z.ro solely for payouts and accounts or also for payment acceptance. I think it’s important to check if there’s a Gateway or merchant onboarding option available. There’s an endpoint for merchant onboarding that I should look into. Since local payments mention cards and digital wallets, if we're processing employer customer payments through Z.ro, we would need that gateway. However, our docs suggest starting with payment-linked commission calculations while integrating with employer processors.
Thinking:
Clarifying integration needs
I’m focusing on the integration requirements for our platform. We need to generate UUIDs per request and manage JWT token refreshes, while securely handling idempotency keys and webhooks with proper signatures. Authentication will rely on API ID/API Key, plus the nonce for endpoints. I might check the protocol/idempotence documentation for specifics. Maybe I’ll ask the user if they want to develop a launch architecture doc, but for now, I think the current details are sufficient.
Thinking:
Detailing project requirements
I need to be precise with my final response since the user asked for exact information. So, I’ll start by stating that for our Brazil-first version, Z.ro can cover regulated custody, money movement, and onboarding, but it won’t replace our existing commission system. To get going with them, we'll need: 1) BaaS contract and credentials, 2) employer/employee onboarding data and documents, 3) Pix collection and payout integration, 4) a webhook/reconciliation layer, and 5) our own internal ledger and commission engine. Then I’ll elaborate on each point.
Thinking:
Identifying onboarding requirements
I need to outline what we require from Z.ro for commercial access, including things like BaaS API access, potential PaaS or Gateway API access, and necessary documentation like product configuration and compliance documents.
For onboarding employers, I should also gather necessary legal documents such as CNPJ, legal names, and shareholder information. Employees will need to provide personal data, CPF, and certain identification documents too. We also need to manage onboarding status and potential rejections effectively.
Thinking:
Outlining integration requirements
I’m identifying what we need to develop or integrate on our side. This includes an onboarding UI for both employers and employees that can handle document collection. I also need to build a token/auth service for Z.ro, a webhook receiver, and systems for payout orchestration and retry handling.
Additionally, I’ll focus on creating a commission rules engine, double-entry ledger, and rules for availability and holdbacks. Lastly, I'll incorporate reconciliation, analytics, customer support tools, and legal/tax policy features.
Thinking:
Clarifying gaps before decision
I need to gather more information before making a choice. First, I want to confirm the production base URL and pricing, which aren’t public. Next, I need clarity on the settlement and custody model — specifically whether funds are in individual sub-accounts per employee or just in a master account. I also have questions about fees for onboarding and payouts, judicial block impacts, webhook security methods, and whether they can support our target verticals and risk profile.
Thinking:
Exploring split payment options
I’m looking into whether split payments can support delayed availability or dynamic scenarios. If we're using a gateway for card acceptance, I want to understand the merchant onboarding flow and the timeline for settlement. It's probably not relevant for version 1, but I should check about data localization, audit reports, and potential KYC issues. My recommendation is to start with BaaS and possibly add PaaS split features or Gateway later, avoiding crypto for now. I’ll also fetch the merchant onboarding documentation for clarity.
I’ve got enough to assess the core fit. I’m checking one last area: whether using Z.ro for customer payment acceptance would require a separate merchant/gateway track, or whether BaaS alone is enough for our recommended v1.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
Create Merchant Onboarding | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Create Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [List Merchants](/baas/endpoints/v-1-get-all-merchant-rest-controller-execute-v-1)
- [Upload Merchant Onboarding Document](/baas/endpoints/v-1-upload-merchant-onboarding-document-rest-controller-execute-v-1)
- [Get Merchant Term Acceptance](/baas/endpoints/v-1-get-merchant-term-acceptance-rest-controller-execute-v-1)
- [Accept Merchant Term Acceptance](/baas/endpoints/v-1-accept-merchant-term-acceptance-rest-controller-execute-v-1)
- [Get Merchant by ID](/baas/endpoints/v-1-get-merchant-by-id-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Users | Merchant Onboarding
- Create Merchant Onboarding
# Create Merchant Onboarding
POST
## /v1/users/merchant-onboarding
Creates a merchant onboarding to register the legal person as a commercial establishment at Dock Acquiring. The legal person onboarding must be finished.
## Request[](#request "Direct link to Request")
### Header Parameters
**x-transaction-uuid** stringrequired
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
- application/json
### Body
**required**
**onboarding\_id** stringrequired
Finished legal person onboarding ID.
**trade\_name** stringrequired
Establishment trade name. Maximum 30 characters.
**mcc** stringrequired
MCC (Merchant Category Code). 4 digits identifying the business type.
**cnae** stringrequired
CNAE code (Classificação Nacional de Atividades Econômicas).
**bank\_number** stringrequired
Bank number (3 digits).
**bank\_branch** stringrequired
Bank branch number.
**bank\_branch\_check\_digit** string
Bank branch check digit.
**bank\_account\_number** stringrequired
Bank account number.
**bank\_account\_digit** stringrequired
Bank account check digit.
**bank\_account\_type** stringrequired
**Possible values:** \[`CHECKING`, `SAVINGS`, `DEPOSIT`, `PAYMENT`\]
Bank account type.
**opening\_date** stringrequired
Establishment opening date. Format: YYYY-MM-DD.
**opening\_days** stringrequired
Operating days. 7-character binary string where each position represents a day (Sun-Sat). Position 0 = Sunday, 1 = Monday, ..., 6 = Saturday. Use 1 for open, 0 for closed.
**opening\_hour** stringrequired
Opening hour. Format: HH:mm.
**closing\_hour** stringrequired
Closing hour. Format: HH:mm.
**municipal\_registration** string
Municipal registration number.
**state\_subscription** string
State registration number.
**establishment\_format** stringrequired
**Possible values:** \[`EI`, `MEI`, `EIRELI`, `LTDA`, `SS`, `SA`, `ME`, `EPP`, `EMPG`, `COOP`, `OTHER`\]
Establishment legal format.
**revenue** numberrequired
Annual revenue in BRL cents.
**legal\_nature\_code** stringrequired
Legal nature code. Common codes:
- 213-5: Empresário Individual (includes MEI)
- 206-2: Sociedade Empresária Limitada (LTDA)
- 232-1: Sociedade Unipessoal de Advocacia
## Responses[](#responses "Direct link to Responses")
- 201
- 400
- 401
- 403
- 422
Merchant onboarding created successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
Merchant onboarding ID.
**status** stringrequired
**Possible values:** \[`PENDING`, `WAITING_DOCUMENTS`, `APPROVED`, `DECLINED`, `FAILED`\]
Merchant onboarding status.
**external\_id** string
Merchant external identifier.
**created\_at** date-timerequired
Created at timestamp.
{ "id": "8fc58500-b12e-49d7-892c-dfd704b94c2d", "status": "PENDING", "external_id": "ABC123DEF456", "created_at": "2024-01-15T10:00:00.000Z"}
If any required parameter is missing or has invalid format/type.
User authentication failed.
User does not have permission to access this resource.
If any required parameter is missing or has invalid format/type.
Loading...
[
Previous
Update Shareholder
](/baas/endpoints/v-1-update-shareholder-rest-controller-execute-v-1)[
Next
List Merchants
](/baas/endpoints/v-1-get-all-merchant-rest-controller-execute-v-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/gateway/api-overview/how-to-use",
"format": "markdown",
"timeout": 60
}
Output:
How to use | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/gateway/api-overview/introduction)
- [Introduction](/gateway/api-overview/introduction)
- [Authentication](/gateway/api-overview/authentication)
- [Protocol](/gateway/api-overview/protocol)
- [Serialization](/gateway/api-overview/serialization)
- [Errors](/gateway/api-overview/errors)
- [How to use](/gateway/api-overview/how-to-use)
- [API Responses](/gateway/api-overview/api-responses)
- [Duplication Prevention](/gateway/api-overview/duplication-prevention)
- [Changelog](/gateway/api-overview/changelog)
- [Webhooks](/gateway/api-overview/webhooks)
- [Endpoints](/gateway/endpoints/zrobank)
- [](/)
- API Overview
- How to use
On this page
# How to use
## Customer Bank Account Registration[](#customer-bank-account-registration "Direct link to Customer Bank Account Registration")
The Zro Gateway has a feature that limits the bank accounts authorized for deposits and/or withdrawals made by customers.
By default, this protection is disabled and can be activated upon request to our team.
Once activated, customers will only be able to make deposits and/or withdrawals to bank accounts that have been previously registered. The management of these accounts can be done in two ways, which are detailed below.
According to BACEN regulations, there is a limit of up to 3 accounts per customer.
## QR Code Generation[](#qr-code-generation "Direct link to QR Code Generation")
One of the ways to manage bank accounts is through the QR Code generation endpoint. In this process, all permitted accounts must be provided in each request.
Example:
URI:
POST /api/transaction/generate_qr_code_pix
Body:
{ "value": 10, "description": "Cobrança de deposito", "client_name": "Johnny", "client_email": "client@email.com", "client_document": "00000000000", "merchant_id": "271e4016-47de-45e0-9340-6f2560ce3a90", "expiration_date": "2024-01-25T18:25:43.000Z", "client_bank_accounts": [ { "bank_ispb": "11111111", "account_number": "111111", "account_branch": "1111" }, { "bank_ispb": "22222222", "account_number": "222222", "account_branch": "2222" } ]}
In the example above, the customer with document number 00000000000 will be authorized to make deposits and/or withdrawals to accounts 111111 and 222222. If the deposit is made through an account other than the registered ones, the transaction will be reversed. And if a different account is provided in the withdrawal request, the transaction will not be processed.
The list of accounts sent will always replace the previous one. For example, if the next QR Code generated for this customer only includes account 111111, that will be the only account authorized for withdrawals, while account 222222 will be removed.
## Customer Bank Account Management Endpoints[](#customer-bank-account-management-endpoints "Direct link to Customer Bank Account Management Endpoints")
Customer bank account management can be done through different endpoints provided by the API. The system will always consider the last account submission, whether through the QR Code generation endpoint or the endpoints listed below.
Here are the main operations:
### List Bank Accounts of a Customer[](#list-bank-accounts-of-a-customer "Direct link to List Bank Accounts of a Customer")
Returns all bank accounts registered for the customer.
GET /api/clients/{document}/bank-accounts
> **document** (required): Customer's document (CPF).
### Define Bank Accounts[](#define-bank-accounts "Direct link to Define Bank Accounts")
Adds new bank accounts to the customer. The provided accounts will replace the previous ones. This endpoint behaves the same as the one used for QR Code generation.
PUT /api/clients/{document}/bank-accounts
> **document** (required): Customer's document (CPF).
### Register Bank Accounts[](#register-bank-accounts "Direct link to Register Bank Accounts")
This endpoint allows registering one bank account at a time for the customer.
POST /api/clients/{document}/bank-accounts
> **document** (required): Customer's document (CPF).
### Delete Bank Account[](#delete-bank-account "Direct link to Delete Bank Account")
Removes a specific bank account associated with the customer.
DELETE /api/clients/{document}/bank-accounts/{bankAccountId}
> **document** (required): Customer's document (CPF).
> **bankAccountId**: ID of the bank account to be removed.
[
Previous
Errors
](/gateway/api-overview/errors)[
Next
API Responses
](/gateway/api-overview/api-responses)
- [Customer Bank Account Registration](#customer-bank-account-registration)
- [QR Code Generation](#qr-code-generation)
- [Customer Bank Account Management Endpoints](#customer-bank-account-management-endpoints)
- [List Bank Accounts of a Customer](#list-bank-accounts-of-a-customer)
- [Define Bank Accounts](#define-bank-accounts)
- [Register Bank Accounts](#register-bank-accounts)
- [Delete Bank Account](#delete-bank-account)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/gateway/api-overview/webhooks",
"format": "markdown",
"timeout": 60
}
Output:
Webhooks | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/gateway/api-overview/introduction)
- [Introduction](/gateway/api-overview/introduction)
- [Authentication](/gateway/api-overview/authentication)
- [Protocol](/gateway/api-overview/protocol)
- [Serialization](/gateway/api-overview/serialization)
- [Errors](/gateway/api-overview/errors)
- [How to use](/gateway/api-overview/how-to-use)
- [API Responses](/gateway/api-overview/api-responses)
- [Duplication Prevention](/gateway/api-overview/duplication-prevention)
- [Changelog](/gateway/api-overview/changelog)
- [Webhooks](/gateway/api-overview/webhooks)
- [Endpoints](/gateway/endpoints/zrobank)
- [](/)
- API Overview
- Webhooks
On this page
# Webhooks
Webhooks enable real-time communication by automatically sending HTTP requests when events occur. Unlike APIs that require polling, webhooks push data to a specified URL, improving efficiency. Common uses include payment processing, notifications, and automation.
The ZroBank API supports webhooks for various events, such as **payment status updates**, **withdraws**, **refunds** and **KYC** (Know Your Customer).
## Webhooks URLs[](#webhooks-urls "Direct link to Webhooks URLs")
All webhook URLs must be **HTTPS** and publicly accessible. The ZroBank API sends a `POST` request to the URL with a JSON payload (example below). These URLs must be provided to ZroBank Integration Team to enable the webhooks.
The URLs we need:
- **Payment Status Update**: URL to receive payment status updates.
- **Withdraw**: URL to receive withdraw events.
- **Refund**: URL to receive refund events.
- **Returned Withdraw**: URL to receive returned withdraw events.
- **KYC**: URL to receive KYC events.
All URLs can be the same or different, depending on your requirements.
## Webhook Security[](#webhook-security "Direct link to Webhook Security")
By default, all webhooks are sent without any authentication. If you need to secure your webhooks, you can use the
### OAuth2 Client Credentials Flow[](#oauth2-client-credentials-flow "Direct link to OAuth2 Client Credentials Flow")
If all the URLs provided are an authenticated URL, we support the **OAuth2 Client Credentials** flow for authentication.
- You need to provide the `client_id`, `client_secret` and `token endpoint` (commonly `/oauth/token`) to the ZroBank Integration Team.
- We will call the token endpoint to get the access token.
- All the next webhooks will include the access token in the `Authorization` header.
You can read more about the OAuth2 Client Credentials flow [here](https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/).
## Webhook Payloads[](#webhook-payloads "Direct link to Webhook Payloads")
This section provides examples of the latest webhook payload versions. If you are using an outdated version, we recommend updating or contacting our [Support Team](/overview/support) for assistance.
### Transactional Webhooks[](#transactional-webhooks "Direct link to Transactional Webhooks")
Transactional Webhooks notify merchants of payment-related events, including payments, withdrawals, and refunds. Below, you will find different webhook versions and their respective payload structures, along with a detailed explanation of each field.
- V7 (Transactions)
- V6/V5/V4 (Transactions)
- V3 (Transactions)
- V7 (Withdraw)
- V6/V5/V4 (Withdraw)
- V6/V5 (Refund)
- V4 (Refund)
{ "status": "paid", "webhook_type": "transaction", "transaction_uuid": "e2e30fe2-f7cf-4310-808e-faa60d70e9ee", "description": "Payment Description", "value": "1.16", "payment_date": "2025-02-12T19:29:22.000000", "end_to_end_id": "E26264220202502121929xKDMdFWi5Q5", "merchant_id": "c50539dc-94de-495b-958a-324edf76b348", "client": { "name": "José da Silva", "cpf_cnpj": "12345678900" }, "payer": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "*004714", "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220", "paid_by_client": false, "kyc": { "ofLegalAge": true, "birthdate": "1955-01-16T00:00:00", "suspectedDeath": false, "pep": null, "age": 70 } }, "receiver": null, "refund": null, "bank_account_data": { "bank_name": "ZRO PAGAMENTOS S.A.", "bank_ispb": "26264220", "account_number": "5684", "account_digit": "1", "account_branch": "0001", "account_type": "CACC" }}
{ "status": "paid", "webhook_type": "transaction", "transaction_uuid": "e2e30fe2-f7cf-4310-808e-faa60d70e9ee", "description": "Payment Description", "value": "1.16", "payment_date": "2025-02-12T19:29:22.000000", "end_to_end_id": "E26264220202502121929xKDMdFWi5Q5", "merchant_id": "c50539dc-94de-495b-958a-324edf76b348", "client": { "name": "José da Silva", "cpf_cnpj": "12345678900" }, "payer": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "*004714", "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220", "paid_by_client": false, "kyc": { "ofLegalAge": true, "birthdate": "1955-01-16T00:00:00", "suspectedDeath": false, "pep": null, "age": 70 } }, "receiver": null, "refund": null, "bank_account_data": { "bank_name": "ZRO PAGAMENTOS S.A.", "bank_ispb": "26264220", "account_number": "56841", "account_branch": "0001", "account_type": "CACC" }}
{ "status": "paid", "webhook_type": "transaction", "transaction_uuid": "e2e30fe2-f7cf-4310-808e-faa60d70e9ee", "description": "Payment Description", "value": "1.16", "payment_date": "2025-02-12T19:29:22.000000", "end_to_end_id": "E26264220202502121929xKDMdFWi5Q5", "merchant_id": "c50539dc-94de-495b-958a-324edf76b348", "client": { "name": "José da Silva", "cpf_cnpj": "12345678900" }, "payer": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "*004714", "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220", "paid_by_client": false, "kyc": { "ofLegalAge": true, "birthdate": "1955-01-16T00:00:00", "suspectedDeath": false, "pep": null, "age": 70 } }, "receiver": null, "refund": null}
{ "status": "paid", "webhook_type": "withdraw", "transaction_uuid": "01dea582-a6ad-59f8-8ec4-7dfedf23fd50", "description": "Payment Description", "value": "1.01", "payment_date": "2025-02-12T19:29:22.000000", "end_to_end_id": "E26264220202502121929xKDMdFWi5Q5", "merchant_id": "2b541929-6ea2-4259-913e-45edd05178d0", "client": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "12345678900" }, "payer": null, "receiver": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "12345678900", "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220" }, "refund": null, "bank_account_data": { "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220", "account_number": "8720077", "account_digit": "7", "account_branch": "0001", "account_type": "CACC" }}
{ "status": "paid", "webhook_type": "withdraw", "transaction_uuid": "01dea582-a6ad-59f8-8ec4-7dfedf23fd50", "description": "Payment Description", "value": "1.01", "payment_date": "2025-02-12T19:29:22.000000", "end_to_end_id": "E26264220202502121929xKDMdFWi5Q5", "merchant_id": "2b541929-6ea2-4259-913e-45edd05178d0", "client": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "12345678900" }, "payer": null, "receiver": { "name": "Maria Ferreira Da Silva", "cpf_cnpj": "12345678900", "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220" }, "refund": null, "bank_account_data": { "bank_name": "Zro Pagamento S.A", "bank_ispb": "26264220", "account_number": "8720077", "account_branch": "0001", "account_type": "CACC" }}
{ "status": "paid", "webhook_type": "refund", "transaction_uuid": "1f1a1031-2cb7-474e-ad13-deb5a8f92d27", "description": "Refund Description", "value": "1.00", "payment_date": "2025-02-12T21:30:51.000000", "end_to_end_id": "D26264220202502122130unPayQe0TZA", "merchant_id": "f157244c-0d1f-4fd8-9329-e3222a981e76", "client": { "name": "José da Silva", "cpf_cnpj": "12345678900" }, "payer": null, "receiver": { "name": "José da Silva", "cpf_cnpj": "12345678900", "bank_name": "FACTA S.A. CFI", "bank_ispb": "15581638" }, "refund": { "transaction_parent_uuid": "dbbb6c6f-a7d5-4162-9569-4aa0de58c6e2", "transaction_parent_merchant_id": "07d464eb-df1c-45a0-9e43-b275cec7b1da", "error_code": "INVALID_PAYER_DOCUMENT" }, "bank_account_data": { "bank_name": "FACTA S.A. CFI", "bank_ispb": "15581638", "account_number": "152", "account_branch": "5856", "account_type": "" }}
{ "status": "paid", "webhook_type": "refund", "transaction_uuid": "1f1a1031-2cb7-474e-ad13-deb5a8f92d27", "description": "Refund Description", "value": "1.00", "payment_date": "2025-02-12T21:30:51.000000", "end_to_end_id": "D26264220202502122130unPayQe0TZA", "merchant_id": "f157244c-0d1f-4fd8-9329-e3222a981e76", "client": { "name": "José da Silva", "cpf_cnpj": "12345678900" }, "payer": null, "receiver": { "name": "José da Silva", "cpf_cnpj": "12345678900", "bank_name": "FACTA S.A. CFI", "bank_ispb": "15581638" }, "refund": { "transaction_parent_uuid": "dbbb6c6f-a7d5-4162-9569-4aa0de58c6e2" }, "bank_account_data": { "bank_name": "FACTA S.A. CFI", "bank_ispb": "15581638", "account_number": "152", "account_branch": "5856", "account_type": "" }}
#### Fields Description[](#fields-description "Direct link to Fields Description")
Field
Possible Values/Format
Description
`status`
`"paid"`, `"failed"`
The status of the transaction.
`webhook_type`
`"transaction"`, `"withdraw"`, `"refund"`
The type of the webhook event.
`transaction_uuid`
String (UUID format)
A unique identifier for the transaction.
`description`
String
A description of the payment.
`value`
Numeric String (e.g., `"10.75"`)
The transaction amount in the respective currency.
`payment_date`
String (ISO 8601 format, e.g., `"2023-01-01T12:11:39.090"`)
The date and time when the payment was processed.
`end_to_end_id`
String (alphanumeric)
A unique identifier for tracking the transaction.
`merchant_id`
String
A unique identifier passed by merchant to identify the transaction.
`client`
Object
The client who generated the QR code, requested withdraw or received refund.
`client.name`
String
The name of the client associated with the transaction.
`client.cpf_cnpj`
Numeric String (CPF: 11 digits, CNPJ: 14 digits)
The unmasked CPF or CNPJ of the client.
`payer`
(nullable) Object
The payer's data. Null when the `webhook_type` is **not** `transaction`.
`payer.name`
String
The name of the payer.
`payer.cpf_cnpj`
String (CPF: 11 digits, CNPJ: 14 digits)
The payer’s CPF or CNPJ. May be masked.
`payer.bank_name`
String
The name of the payer’s bank.
`payer.bank_ispb`
Numeric String (8-digit ISPB code)
The ISPB (bank identifier) of the payer’s bank.
`payer.paid_by_client`
Boolean: `true`, `false`
Indicates if the payer is the client who generated the QR code.
`payer.kyc`
Object or Empty Object
KYC (Know Your Customer) data for the payer. May be an empty object.
`payer.kyc.ofLegalAge`
(nullable) Boolean
Indicates if the client is of legal age.
`payer.kyc.birthdate`
(nullable) String (ISO format)
The client’s birth date.
`payer.kyc.age`
(nullable) Integer
The client’s age.
`payer.kyc.pep`
(nullable) Boolean
Indicates if the client is a PEP (Politically Exposed Person).
`payer.kyc.suspectedDeath`
(nullable) Boolean
Indicates if the client is suspected to have passed away.
`receiver`
(nullable) Object
The receiver's data. Null when the `webhook_type` is not `withdraw` or `refund`.
`receiver.name`
String
The name of the receiver.
`receiver.cpf_cnpj`
Numeric String (CPF: 11 digits, CNPJ: 14 digits)
The unmasked CPF or CNPJ of the receiver.
`receiver.bank_name`
String
The name of the receiver’s bank.
`receiver.bank_ispb`
Numeric String (8-digit ISPB code)
The ISPB (bank identifier) of the receiver’s bank.
`refund`
(nullable) Object
Refund data. Null when the `webhook_type` is **not** `refund`.
`refund.transaction_parent_uuid`
String (UUID format)
The UUID of the original transaction if this is a refund.
`refund.transaction_parent_merchant_id`
String (UUID format)
The merchant ID of the original transaction if this is a refund.
`refund.error_code`
ISPB\_NOT\_IN\_PERMISSION\_LIST", "INVALID\_PAID\_VALUE", "INVALID\_PAYER\_DOCUMENT", "KYC\_RESTRICTION", "INVALID\_PAYER\_BANK\_ACCOUNT", "INVALID\_DEPOSIT\_FROM\_JURIDIC\_PERSON"
Error code when an automatic (due to company policies validations) refund happens.
`bank_account_data`
Object
Payer's bank account data.
`bank_account_data.bank_name`
String
The name of the bank where the QR code was paid.
`bank_account_data.bank_ispb`
Numeric String (8-digit ISPB code)
The ISPB code of the bank.
`bank_account_data.account_number`
Numeric String (may be empty)
The account number from which the payment originated.
`bank_account_data.account_digit`
Numeric String (may be empty)
The account number digit from which the payment originated.
`bank_account_data.account_branch`
Numeric String (may be empty)
The branch number of the payer’s bank account.
`bank_account_data.account_type`
`"CACC"`, `"SVGS"`, `"SLRY"`, `"CASH"`, `"TRAN"`, `"TAXE"`, `"OTHR"` (may be empty)
The type of account.
### KYC Webhook[](#kyc-webhook "Direct link to KYC Webhook")
The KYC (Know Your Customer) Webhook provides real-time verification data for payers involved in transactions (when enabled). Below is the JSON payload structure returned by the webhook.
- V1
{ "name": "José da Silva", "document": "12345678900", "age": 54, "ofLegalAge": true, "suspectedDeath": false, "pep": null, "merchantId": "761f802a-1635-4b21-acd0-858277cc5c45", "transactionUuid": "215e8f33-183f-4fd7-8ec1-346ca9999184"}
#### Fields Description[](#fields-description-1 "Direct link to Fields Description")
Field
Possible Values/Format
Description
`name`
String
Full name of the individual.
`document`
String Numbers Only
Identification document number (e.g., CPF in Brazil).
`age`
Integer
The age of the individual.
`ofLegalAge`
Boolean
Indicates whether the individual is of legal age (18 or older).
`suspectedDeath`
Boolean
Indicates if there is suspicion of the individual’s death.
`pep`
(nullable) Boolean
Politically Exposed Person status; `null` if not applicable.
`merchantId`
String (UUID format)
Unique identifier for the merchant.
`transactionUuid`
String (UUID format)
Unique identifier for the transaction.
## Support[](#support "Direct link to Support")
It’s always a pleasure to help you! If you need assistance with the integration or have any questions, please feel free to use our documentation and do not hesitate to [contact us](/overview/support).
[
Previous
Changelog
](/gateway/api-overview/changelog)[
Next
Introduction
](/gateway/endpoints/zrobank)
- [Webhooks URLs](#webhooks-urls)
- [Webhook Security](#webhook-security)
- [OAuth2 Client Credentials Flow](#oauth2-client-credentials-flow)
- [Webhook Payloads](#webhook-payloads)
- [Transactional Webhooks](#transactional-webhooks)
- [KYC Webhook](#kyc-webhook)
- [Support](#support)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/api-overview/idempotence",
"format": "markdown",
"timeout": 60
}
Output:
Idempotence | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Introduction](/baas/api-overview/introduction)
- [Authentication](/baas/api-overview/authentication)
- [Protocol](/baas/api-overview/protocol)
- [Idempotence](/baas/api-overview/idempotence)
- [Rate Limiting](/baas/api-overview/rate-limiting)
- [Request ID (Nonce)](/baas/api-overview/request-id)
- [Serialization](/baas/api-overview/serialization)
- [Replay Protection](/baas/api-overview/replay)
- [Pagination](/baas/api-overview/pagination)
- [API Responses](/baas/api-overview/api-responses)
- [Changelog](/baas/api-overview/changelog)
- [Webhooks](/baas/api-overview/webhooks)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [](/)
- API Overview
- Idempotence
# Idempotence
Idempotence is a fundamental concept in our API, as it ensures that the same request can be made multiple times without causing unwanted side effects, maintaining data consistency.
When making a request to our API, it is automatically forwarded to Kafka, a distributed messaging system that allows us to work with real-time data and ensure its integrity. This way, we can ensure that each request is treated independently and with total security, without causing side effects or inconsistencies in the data.
[
Previous
Protocol
](/baas/api-overview/protocol)[
Next
Rate Limiting
](/baas/api-overview/rate-limiting)
Assistant (Plan · GPT-5.4 · 49.3s)
Thinking:
Considering payment options
I need to think about whether we want card acceptance or a consumer-facing merchant collection. That might require separate gateway or merchant onboarding with Dock acquiring. If our design partners already have their payment processors and we're just reconciling trusted payment data, we might not actually need the Z.ro Gateway at launch. If we go for collecting via Pix, maybe PaaS/BaaS would be sufficient for that. Card acceptance via Z.ro could require a separate gateway for merchant onboarding. Perhaps we can defer some of these decisions for now.
Thinking:
Considering endpoint details
I need to answer accurately, and while I have enough information, I might need specific endpoint details. I could fetch relevant documentation for exact names or mention endpoint paths from onboarding. I already have some path names, but understanding PaaS/BaaS differences could help. It’s crucial to address x-product-uuid and x-product-target-user-uuid, as they indicate one platform product with multiple end users. Mentioning how product/user delegation works and confirming with Z.ro would be important too.
Thinking:
Reviewing documentation needs
I’m considering whether an explore agent is necessary, but I might need real page content for international payment gateway docs. The user wants me to go over documentation and identify exactly what we need. I can reference public docs, but I should highlight their limitations as they don’t include critical pricing and regulatory terms, which need to be confirmed with Z.ro. It might help to compile this into a due diligence questionnaire and clarify if the user prefers a narrow v1 or full stack approach. Assuming a Brazil-first approach, I could mention that in my response.
Thinking:
Considering documentation alignment
I could reference docs/core-idea.md and potentially use code or file references, though it might not be necessary. I might want to mention, "Based on our current Brazil-first v1: payment-linked commission calculation + Pix cash-out." While it probably isn't essential to cite specific file lines, mentioning our repo thesis could be helpful. I should also think about computing the exact required flows and steps. This aligns with our startup thesis around employer workflows, payment-linked commissions, and instant access to earned commissions.
Thinking:
Evaluating onboarding solutions
I'm considering the onboarding process. It looks like BaaS is the best option for user and company onboarding, especially since we need wallet/account management and employee balances. PaaS might only be necessary if we don't onboard end users. I should assess the exact needs because using just BaaS might work since it provides access to Pix services, including payments and wallets. The documentation shows options for both, so I need to be careful about assuming one will suffice over the other.
Thinking:
Assessing financial architecture
I'm exploring how PaaS could work, but since we need user accounts and onboarding, BaaS seems essential. BaaS is likely our core contract, while PaaS may be redundant for our initial version unless they offer packaged Pix services with better pricing. We also need an internal ledger that tracks various states and manages the commission engine, reserve logic, dashboards, and audit trails. I can't rely on Z.ro wallet balances for this, as they only reflect banking movements, so I must ensure a clear mapping between sales, employer rules, and ledger entries.
Thinking:
Deciding on cash-out flow
For the cash-out flow, once the commission is available in our ledger, we can either execute a Pix payment from the employer or platform wallet directly to the employee's external account, or transfer funds to the employee's Z.ro wallet for them to withdraw or use later. I really need to decide which model is better. Currently, my thinking leans towards partner-held custody with a later stored balance or card, while starting V1 with Pix for instant cash-out and a stored balance afterward.
Thinking:
Fetching payment documentation
I’m considering whether we should gather specific documentation for the Pix payment endpoint and P2P transfers. That could help clarify things. I’m also thinking about fetching docs related to creating user accounts and product targets, although we already have onboarding covered. To recommend a minimal model, I need to confirm if payouts can go to an external Pix key. Let’s focus on the Pix payment endpoint, including wallet headers and payment body details, particularly the beneficiary Pix key and idempotency headers.
I’m validating the payout-side mechanics before I wrap this up, because that determines whether we need full employee bank accounts on day one or can start with simpler Pix cash-out.
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
Create Decoded Pix Key ID | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Create Decoded Pix Key ID](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Create Decoded QR Code](/baas/endpoints/v-2-create-decoded-qr-code-rest-controller-execute-v-2)
- [Create Decoded Pix Account ID](/baas/endpoints/v-1-create-decoded-pix-account-rest-controller-execute-v-1)
- [Create Pix Payment by Bank Account](/baas/endpoints/v-2-create-by-account-payment-rest-controller-execute-v-2)
- [Decode and Create Pix Payment by Bank Account](/baas/endpoints/v-1-decode-and-create-by-account-payment-rest-controller-execute-v-1)
- [Withdraw Payment with Static QR Code](/baas/endpoints/v-1-withdrawal-by-qr-code-static-payment-rest-controller-execute-v-1)
- [Withdraw Payment with Dynamic QR Code](/baas/endpoints/v-1-withdrawal-by-qr-code-dynamic-payment-rest-controller-execute-v-1)
- [Create Due Date Payment with Dynamic QR Code](/baas/endpoints/v-1-duedate-by-qr-code-dynamic-payment-rest-controller-execute-v-1)
- [Create Change Payment with Dynamic QR Code](/baas/endpoints/v-1-change-by-qr-code-dynamic-payment-rest-controller-execute-v-1)
- [Create Payment with Dynamic QR Code](/baas/endpoints/v-1-create-by-qr-code-dynamic-payment-rest-controller-execute-v-1)
- [Create Payment with Static QR Code](/baas/endpoints/v-1-create-by-qr-code-static-payment-rest-controller-execute-v-1)
- [Create Pix Payment by Pix Key](/baas/endpoints/v-1-create-by-pix-key-payment-rest-controller-execute-v-1)
- [Decode and Create Pix Payment by Pix Key](/baas/endpoints/v-1-decode-and-create-by-pix-key-payment-rest-controller-execute-v-1)
- [Cancel Payment by Operation ID](/baas/endpoints/v-1-cancel-payment-by-operation-id-rest-controller-execute-v-1)
- [List Pix Payments](/baas/endpoints/v-1-get-all-payment-rest-controller-execute-v-1)
- [Get Pix Payment by ID](/baas/endpoints/v-1-get-payment-by-id-rest-controller-execute-v-1)
- [Create Pix Trusted Contact](/baas/endpoints/v-1-create-pix-trusted-contact-rest-controller-execute-v-1)
- [List Pix Trusted Contact](/baas/endpoints/v-1-get-all-pix-trusted-contact-by-wallet-rest-controller-execute-v-1)
- [Get Pix Trusted Contact by ID](/baas/endpoints/v-1-get-pix-trusted-contact-by-id-and-wallet-rest-controller-execute-v-1)
- [Delete pix trusted contact](/baas/endpoints/v-1-delete-pix-trusted-contact-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Pix | Payments
- Create Decoded Pix Key ID
# Create Decoded Pix Key ID
GET
## /v1/pix/payments/decode/by-key
Generate a new Decoded Pix Key ID to facilitate pix payments by pix key. Provide the pix key's information in the request body and execute to obtain its ID (decoded\_pix\_key\_id), which is required for creating pix payments using a pix key.
## Request[](#request "Direct link to Request")
### Query Parameters
**key** stringrequired
Pix key.
**type** stringrequired
**Possible values:** \[`CNPJ`, `CPF`, `PHONE`, `EMAIL`, `EVP`\]
Pix Key state:
- CPF: Key type CPF.
- EVP: Key type EVP.
- EMAIL: Key type EMAIL.
- PHONE: Key type PHONE.
- CNPJ: Key type CNPJ.
### Header Parameters
**x-transaction-uuid** stringrequired
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** stringrequired
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
## Responses[](#responses "Direct link to Responses")
- 200
- 400
- 401
- 422
Pix key decoded successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
Unique decoded pix key UUID.
**type** stringrequired
**Possible values:** \[`CNPJ`, `CPF`, `PHONE`, `EMAIL`, `EVP`\]
Pix Key state:
- CPF: Key type CPF.
- EVP: Key type EVP.
- EMAIL: Key type EMAIL.
- PHONE: Key type PHONE.
- CNPJ: Key type CNPJ.
**person\_type** stringrequired
**Possible values:** \[`NATURAL_PERSON`, `LEGAL_PERSON`\]
**key** stringrequired
Pix key.
**document** stringrequired
Owner document number.
**name** stringrequired
Owner name.
**trade\_name** string
Company's trade name.
**end\_to\_end\_id** stringrequired
**ispb** stringrequired
Bank ISPB.
**bank\_name** stringrequired
Bank name.
{ "id": "d5e0bec8-8695-4557-b0dd-021788cd83ef", "type": "EMAIL", "person_type": "LEGAL_PERSON", "key": "string", "document": "string", "name": "string", "trade_name": "string", "end_to_end_id": "string", "ispb": "string", "bank_name": "string"}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Dismiss Pix Key
](/baas/endpoints/v-2-dismiss-by-id-pix-key-rest-controller-execute-v-2)[
Next
Create Decoded QR Code
](/baas/endpoints/v-2-create-decoded-qr-code-rest-controller-execute-v-2)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
Create P2P Transfer | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Create P2P Transfer](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Get P2P Transfer by ID](/baas/endpoints/v-1-get-p-2-p-transfer-by-id-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Operations | P2P Transfers
- Create P2P Transfer
# Create P2P Transfer
POST
## /v1/operations/p2p-transfers
Initiate a peer-to-peer (P2P) fund transfer within your organization, allowing transfers between Master Account and Sub-account wallets. Specify the UUID of the wallet you are transferring funds from in the "x-wallet-uuid" header. If the "x-wallet-uuid" param is omitted, your default wallet will be used. Provide the destination wallet and transaction details in the request body and execute to complete the transaction.
## Request[](#request "Direct link to Request")
### Header Parameters
**x-include-replay-protection-schema** string
The replay-protection-schema allows the user to choose between 3 options:
- If there's no value: The default protection checks that the values in this request are equal: **{ method, params, path, query, body, userId }.** This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and **{ method, params, path, query, body, userId }** value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and **{ method, params, path, query, body, userId }** value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and **{ method, params, path, query, body, userId }** are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
**x-transaction-uuid** stringrequired
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
- application/json
### Body
**required**
**destination\_wallet\_id** string
Destination wallet UUID.
**amount\_currency** stringrequired
Transfer currency amount symbol.
**amount** numberrequired
Transfer amount in cents.
**fee** numberrequired
Transfer fee in cents.
**description** string
Transfer description.
**merchant\_id** string
User defined payment merchant ID.
## Responses[](#responses "Direct link to Responses")
- 201
- 400
- 401
- 422
Transfer response.
- application/json
- Schema
- Example (from schema)
**Schema**
**id** stringrequired
Transfer UUID.
**operation\_id** stringrequired
Transfer Operation UUID.
**amount\_currency** stringrequired
Transfer currency amount.
**amount** numberrequired
Transfer amount in cents.
**fee** numberrequired
Transfer fee in cents.
**description** stringnullable
Transfer description.
**created\_at** date-timerequired
Transfer created at.
{ "id": "f6e2e084-29b9-4935-a059-5473b13033aa", "operation_id": "f6e2e084-29b9-4935-a059-5473b13033aa", "amount_currency": "BRL", "amount": 1299, "fee": 10, "description": "string", "created_at": "2026-03-26T14:02:58.521Z"}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Create a New Permission Type
](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)[
Next
Get P2P Transfer by ID
](/baas/endpoints/v-1-get-p-2-p-transfer-by-id-rest-controller-execute-v-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
List Wallets | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [List Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Create Wallet](/baas/endpoints/v-1-create-wallet-rest-controller-execute-v-1)
- [Get Wallet by ID](/baas/endpoints/v-1-get-wallet-by-id-rest-controller-execute-v-1)
- [Update Wallet Name](/baas/endpoints/v-1-update-wallet-rest-controller-execute-v-1)
- [Delete Wallet](/baas/endpoints/v-1-delete-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Operations | Wallets
- List Wallets
# List Wallets
GET
## /v1/operations/wallets
Retrieve a list of the user's wallets. You can include any of the filter parameters below to refine your search.
## Request[](#request "Direct link to Request")
### Query Parameters
**owner** string
**Possible values:** \[`USER`, `OTHER`, `ADMIN`\]
User wallet owner type.
### Header Parameters
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
## Responses[](#responses "Direct link to Responses")
- 200
- 400
- 401
- 422
The wallets returned successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
- Array \[
**id** stringrequired
Wallet id.
**name** stringrequired
Wallet name.
**default** booleanrequired
Wallet default flag.
**state** stringrequired
**Possible values:** \[`pending`, `active`, `deactivate`, `blocked`\]
Wallet state.
**permission\_types** string\[\]required
Wallet permission type that defines what the user can do.
**owner\_id** stringrequired
Wallet owner id.
**owner\_name** stringrequired
Wallet owner name.
**created\_at** date-timerequired
Wallet created at.
- \]
[ { "id": "f6e2e084-29b9-4935-a059-5473b13033aa", "name": "BTC", "default": false, "state": "active", "permission_types": [ "CLIENT" ], "owner_id": "f6e2e084-29b9-4935-a059-5473b13033aa", "owner_name": "James Bond", "created_at": "2026-03-26T14:02:59.116Z" }]
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
Create SPOT Quotation
](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)[
Next
Create Wallet
](/baas/endpoints/v-1-create-wallet-rest-controller-execute-v-1)
Tool: webfetch
Input:
{
"url": "https://coinwise-io.github.io/zrobank-doc-api/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1",
"format": "markdown",
"timeout": 60
}
Output:
List Operations | Z.ro Bank
[Skip to main content](#__docusaurus_skipToContent_fallback)
[
](/)[Overview](/overview/introduction)[Banking as a Service](/baas/api-overview/introduction)[Crypto as a Service](/caas/api-overview/introduction)[Gateway](/gateway/api-overview/introduction)[Pix as a Service](/paas/api-overview/introduction)
[Payments Gateway](https://docs-international.zrobank.io)
- [API Overview](/baas/api-overview/introduction)
- [Guides](/baas/guides/legal-person-onboarding)
- [Endpoints](/baas/endpoints/zro-global-baas-api)
- [Introduction](/baas/endpoints/zro-global-baas-api)
- [Authentication](/baas/endpoints/v-1-login-auth-rest-controller-execute-v-1)
- [Pix | Keys](/baas/endpoints/v-1-get-all-pix-key-rest-controller-execute-v-1)
- [Pix | Payments](/baas/endpoints/v-1-create-decoded-pix-key-rest-controller-execute-v-1)
- [Pix | Devolutions](/baas/endpoints/v-1-create-pix-devolution-rest-controller-execute-v-1)
- [Pix | Deposits](/baas/endpoints/v-1-get-all-pix-deposit-rest-controller-execute-v-1)
- [Otc | Conversions](/baas/endpoints/v-1-create-conversion-rest-controller-execute-v-1)
- [Quotations | Conversions](/baas/endpoints/v-1-get-quotation-rest-controller-execute-v-1)
- [Operations | Wallets](/baas/endpoints/v-1-get-all-wallet-rest-controller-execute-v-1)
- [Permissions | Permission Types](/baas/endpoints/create-permission-type-rest-controller-execute-v-1)
- [Operations | P2P Transfers](/baas/endpoints/v-1-create-p-2-p-transfer-rest-controller-execute-v-1)
- [Operations | Wallet Accounts](/baas/endpoints/v-1-get-all-wallet-account-rest-controller-execute-v-1)
- [Operations | Currency](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)
- [Operations | Operation](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [List Operations](/baas/endpoints/v-1-get-all-operations-rest-controller-execute-v-1)
- [Get Operation by ID](/baas/endpoints/v-1-get-operation-by-id-rest-controller-execute-v-1)
- [Get Receipt by Operation ID](/baas/endpoints/v-1-get-operation-receipt-by-id-rest-controller-execute-v-1)
- [Request Receipt PDF Generation by Operation ID](/baas/endpoints/v-1-generate-operation-receipt-pdf-by-user-and-wallet-and-id-rest-controller-execute-v-1)
- [Get Pending Balance](/baas/endpoints/get-pending-sum-by-wallet-account-rest-controller-execute-v-1)
- [Banking](/baas/endpoints/v-1-get-all-banking-ted-received-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposits](/baas/endpoints/v-1-create-banking-billet-pix-deposit-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Template](/baas/endpoints/v-1-create-banking-billet-pix-deposit-template-rest-controller-execute-v-1)
- [Banking | Bank Billet | Payments](/baas/endpoints/v-1-get-banking-billet-payment-by-id-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-rest-controller-execute-v-1)
- [Banking | Bank Billet | Pix Deposit Batch Item](/baas/endpoints/v-1-create-banking-billet-pix-deposit-batch-item-rest-controller-execute-v-1)
- [Utils | User Withdraw Settings](/baas/endpoints/v-1-get-all-user-withdraw-setting-rest-controller-execute-v-1)
- [Health](/baas/endpoints/health-controller-execute)
- [Reports](/baas/endpoints/v-3-generate-pix-statement-export-rest-controller-execute-v-3)
- [Storage](/baas/endpoints/v-1-get-all-files-rest-controller-execute-v-1)
- [Users | User Account](/baas/endpoints/v-1-delete-user-account-rest-controller-execute-v-1)
- [Users | User Bank Account](/baas/endpoints/v-1-get-user-bank-account-by-wallet-rest-controller-execute-v-1)
- [Users | Legal Person](/baas/endpoints/v-1-get-all-legal-person-onboarding-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding](/baas/endpoints/v-1-create-onboarding-rest-controller-execute-v-1)
- [Users | Legal Representative](/baas/endpoints/v-2-get-all-legal-representative-rest-controller-execute-v-2)
- [Users | Company Document](/baas/endpoints/v-1-upload-company-document-rest-controller-execute-v-1)
- [Users | Natural Person Onboarding | Occupation](/baas/endpoints/v-1-get-all-occupation-rest-controller-execute-v-1)
- [Users | Shareholder](/baas/endpoints/v-1-create-shareholder-rest-controller-execute-v-1)
- [Users | Merchant Onboarding](/baas/endpoints/v-1-create-merchant-onboarding-rest-controller-execute-v-1)
- [Users | Company Registration](/baas/endpoints/v-1-create-company-registration-rest-controller-execute-v-1)
- [Card](/baas/endpoints/v-1-create-virtual-card-rest-controller-execute-v-1)
- [Card | Onboarding](/baas/endpoints/v-1-get-terms-of-use-rest-controller-execute-v-1)
- [Pix | Scheduled Payments](/baas/endpoints/get-all-pix-scheduled-payment-rest-controller-execute-v-1)
- [Pix | Automatic Receiver Limits](/baas/endpoints/create-pix-automatic-receiver-limit-rest-controller-execute-v-1)
- [Open Finance | Participants](/baas/endpoints/v-1-get-all-open-finance-participants-rest-controller-execute-v-1)
- [Open Finance | Payment Consents](/baas/endpoints/v-1-create-open-finance-payment-consent-by-pix-key-rest-controller-execute-v-1)
- [Open Finance | Payments](/baas/endpoints/v-1-create-open-finance-payment-rest-controller-execute-v-1)
- [Crossborder | Clients](/baas/endpoints/v-1-create-client-rest-controller-execute-v-1)
- [Crossborder | Client Documents](/baas/endpoints/v-1-upload-client-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Accounts](/baas/endpoints/v-1-create-client-account-rest-controller-execute-v-1)
- [Crossborder | Client Wallets](/baas/endpoints/v-1-create-client-wallet-rest-controller-execute-v-1)
- [Crossborder | Client Wallet Documents](/baas/endpoints/v-1-upload-client-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Client Account Documents](/baas/endpoints/v-1-upload-client-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Quotes](/baas/endpoints/v-1-upload-quote-document-file-rest-controller-execute-v-1)
- [Crossborder | Rates](/baas/endpoints/v-1-get-rate-rest-controller-execute-v-1)
- [Crossborder | Deposits](/baas/endpoints/v-1-get-deposit-info-by-quote-rest-controller-execute-v-1)
- [Crossborder | Counterparties](/baas/endpoints/v-1-create-counterparty-rest-controller-execute-v-1)
- [Crossborder | Counterparty Documents](/baas/endpoints/v-1-upload-counterparty-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Accounts](/baas/endpoints/v-1-create-counterparty-account-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallets](/baas/endpoints/v-1-create-counterparty-wallet-rest-controller-execute-v-1)
- [Crossborder | Counterparty Wallet Documents](/baas/endpoints/v-1-upload-counterparty-wallet-document-file-rest-controller-execute-v-1)
- [Crossborder | Counterparty Account Documents](/baas/endpoints/v-1-upload-counterparty-account-document-file-rest-controller-execute-v-1)
- [Crossborder | Stream Quotations](/baas/endpoints/v-1-get-stream-quotation-by-filter-rest-controller-execute-v-1)
- [Schemas](/baas/endpoints/schemas/v-1-authenticaterestrequest)
- [](/)
- Endpoints
- Operations | Operation
- List Operations
# List Operations
GET
## /v1/operations
Retrieve a list of the user's operations.
## Request[](#request "Direct link to Request")
### Query Parameters
**page** number
**Default value:** `1`
Page number.
**size** number
**Possible values:** `<= 100`
**Default value:** `20`
Page size. Max size is 100.
**sort** string
**Possible values:** \[`created_at`\]
Page sort attribute.
**order** string
**Possible values:** \[`asc`, `desc`\]
**Default value:** `asc`
Page order.
**currency\_symbol** string
Operation currency symbol.
**transaction\_tag** string
Operation Transaction tag.
**created\_at\_start** date-time
Operation Created at start.
**created\_at\_end** date-time
Operation Created at end.
### Header Parameters
**x-wallet-uuid** string
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
**nonce** stringrequired
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
**x-lang** string
**Possible values:** \[`pt-BR`, `en-US`\]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
**x-product-uuid** string
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
**x-product-target-user-uuid** string
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
## Responses[](#responses "Direct link to Responses")
- 200
- 400
- 401
- 422
The operations returned successfully.
- application/json
- Schema
- Example (from schema)
**Schema**
**page** numberrequired
Page number.
**page\_size** numberrequired
Page size.
**page\_total** numberrequired
Page total.
**total** numberrequired
Total of elements.
**data** object\[\]required
Operations data.
- Array \[
**id** stringrequired
Operation id.
**fee** number
Operation fee in cents.
**state** stringrequired
**Possible values:** \[`accepted`, `declined`, `undone`, `pending`, `reverted`, `waiting_accept`, `waiting_revert`, `waiting_ledger`, `waiting_credit`, `waiting_debit`, `waiting_accept_credit`\]
Operation state.
**description** stringrequired
Operation description.
**value** number
Operation value in cents.
**created\_at** date-timerequired
Operation created at.
**reverted\_at** date-time
Operation reverted at.
**currency\_id** numberrequired
Currency Id.
**currency\_symbol** stringrequired
Currency symbol.
**transaction\_id** numberrequired
Transaction id.
**transaction\_tag** stringrequired
Transaction tag.
**owner\_wallet\_uuid** string
Operation owner wallet.
**beneficiary\_wallet\_uuid** string
Operation beneficiary wallet uuid.
**operation\_ref\_id** string
Operation ref id.
**chargeback\_id** string
Operation chargeback id.
- \]
{ "page": 1, "page_size": 20, "page_total": 20, "total": 100, "data": [ { "id": "f6e2e084-29b9-4935-a059-5473b13033aa", "fee": 0, "state": "accepted", "description": "string", "value": 1880000, "created_at": "2026-03-26T14:02:58.523Z", "reverted_at": "2026-03-26T14:02:58.523Z", "currency_id": 2, "currency_symbol": "R$", "transaction_id": 2, "transaction_tag": "BRL", "owner_wallet_uuid": "f6e2e084-29b9-4935-a059-5473b13033aa", "beneficiary_wallet_uuid": "f6e2e084-29b9-4935-a059-5473b13033aa", "operation_ref_id": "f6e2e084-29b9-4935-a059-5473b13033aa", "chargeback_id": "f6e2e084-29b9-4935-a059-5473b13033aa" } ]}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.
Loading...
[
Previous
List Currencies
](/baas/endpoints/v-1-get-all-currency-rest-controller-execute-v-1)[
Next
Get Operation by ID
](/baas/endpoints/v-1-get-operation-by-id-rest-controller-execute-v-1)
Assistant (Plan · GPT-5.4 · 148.7s)
Thinking:
Analyzing Z.ro Bank Docs
The user is looking at Z.ro Bank for potential services, so I need to go over their documentation to identify what’s necessary for our product. Since we’re in read-only mode, I won’t make edits, but I’ll create a thorough analysis based on my research. I’ll map out what’s essential versus optional, highlighting any limitations. It could be helpful to specify APIs, onboarding flows, and perhaps ask if they want a comparison with other services.
Thinking:
Finalizing Requirements for Z.ro
I need to summarize our next steps based on both the repository docs and the user’s request. Since we’re a documentation-first startup, I’ll synthesize our current product requirements with Z.ro's capabilities. It’s important to deeply examine all findings. Our phase 1 product includes payment-linked commission calculations, instant access to earned balances, partner-led custody, Pix instant transfers, dashboards, and an internal ledger. We’ll use payment events as our source of truth and start in Brazil, considering cards later. Now I'll analyze Z.ro's documentation.
Thinking:
Considering payment integration
I’m weighing the option of gateway and merchant onboarding to make Z.ro the payment acceptance source of truth. That feels like a significant decision. For version one, maybe this isn't essential since we could just take payment events from the employers' existing processor. However, if we want to proceed with Z.ro for acceptance, we’ll likely need to focus on merchant onboarding, gateway integrations like QR codes, and webhooks, possibly considering Dock acquiring if cards are involved.
Thinking:
Evaluating payment solutions
I’m considering a Brazil-first approach with Pix-based earnings access, possibly starting without merchant acceptance. Using Z.ro for collection is optional for version one. If we want payment-linked truth via Pix, a PaaS split QR code could route sales directly to the employer and employee. However, I realize that relying on Z.ro for split payments as the commission ledger might introduce challenges, such as complexity in commission logic and conflicts with reserves. So, we’ll need our own engine and internal ledger.
Thinking:
Assessing initial payment structure
I may consider using split payments for simple cases later, but likely not for the initial core of the project. It's important to note what Z.ro cannot replace, including the commission rules engine, internal ledger for financial tracking, employer analytics, product UI/UX, and workflows for disputes and adjustments. We should evaluate the necessity of using full employee bank accounts from day one, as BaaS allows for onboarding and bank account retrieval for employees. Having employee wallets at Z.ro might be beneficial for our model, especially for instant payout access.
Thinking:
Exploring payout models
I'm considering a couple of payout models. One option is to have employer funds in a master settlement account; when the commission is available, we transfer funds to employee sub-wallets through an internal P2P transfer, allowing employees to withdraw via Pix. The second option involves direct Pix payouts from the employer or platform account to the employee’s external Pix key without setting up Z.ro accounts for employees. I need to confirm what Z.ro supports regarding these BaaS Pix payments and whether I can execute actions on behalf of users.
Thinking:
Considering Z.ro architecture options
I'm looking at the recommended architecture and thinking about using Z.ro BaaS as our main partner for various functions like onboarding and wallet issuance. Z.ro PaaS might be optional unless we want specific features like Pix collection APIs or dynamic QR codes at scale. As for Z.ro Gateway, it would only be necessary if we want them to handle our payment acceptance. However, for version 1, we might not need it since we can use existing processors.
Thinking:
Mapping onboarding processes
I need to clearly outline the exact endpoints and processes for each onboarding module, focusing on KYB and KYC. For example, there are distinct steps for both legal person and natural person onboarding, including creating user accounts and uploading necessary documents.
I should also mention document requirements, such as file types and size limits. Additionally, the user is looking for specific details on required artifacts, so I want to make sure I provide a thorough and clear list.
Thinking:
Clarifying product requirements
I need to clarify the role of x-product-uuid in our endpoints, as it's either required or optional. It seems to relate to the Z.ro concept for white-labeling, which is key for provisioning products on our platform. We should also be using x-product-target-user-uuid to manage actions on behalf of employers or employees.
It's important to mention the provisioning necessities, including sandbox and production setups, master accounts, webhooks, and sub-account capabilities. Lastly, I need to confirm with Z.ro how the white-label product and sub-account model function, especially regarding fund ownership.
Thinking:
Examining webhook options and transactions
I'm looking into webhook authentication options for BaaS and PaaS. I see they mention optional credentials, and Gateway supports OAuth2 client credentials.
Next, I’m curious about how refunds and chargebacks are represented and whether funds can be frozen or held. I also need to figure out the production base URL, which isn’t public.
Further, I’ll consider fees, settlement arrangements, and if the split QR feature can support dynamic adjustments or holds. Lastly, I wonder about the payment processing roles for employers and Z.ro. These seem like contract questions not really answered in the docs.
Thinking:
Evaluating API options
I’ve already looked at the decode endpoint. It seems like we might not need anything more. I’m thinking the direct creation using the pix key endpoint could clarify requirements. However, it might be enough as is. I could mention the decode step and then the create payment endpoint, but I’m also considering whether that's really necessary in the final output. It's all about balancing what adds value without overcomplicating things!
Thinking:
Exploring financial infrastructure needs
I need to clarify that Z.ro can cover "most regulated money movement pieces" rather than "most product pieces." I think I might phrase it as: "Z.ro could be our main financial infrastructure partner for v1 if we retain our commission logic and ledger." Specifically, we would require BaaS first, with Gateway and PaaS as optional. I should cite the exact endpoints, but without overwhelming details. It's also important to mention "Dock" in the context of merchant onboarding.
Thinking:
Analyzing card issuance requirements
I should consider that card issuance might involve third parties, which is useful to know if we're looking for a simpler vendor structure or direct control. I need to highlight the distinction between "What Z.ro docs explicitly expose" and "what docs do not prove." For example, public documents lack details on settlement schedules, fee tables, and other critical information, which requires diligence. Also, I think it's important to mention using their split QR only for straightforward commission disbursements and not as the sole source of truth.
Thinking:
Structuring insights for Z.ro
I've identified some important insights. I think it’s necessary to mention concepts like "automatic receiver limits" or "scheduled payments," but they might not be crucial.
The potential structure could be a top-line conclusion followed by specific needs from Z.ro. This includes setting up a BaaS product, onboarding legal and natural persons, establishing a wallet/account model, and integrating specific functionalities like Pix rails and reporting endpoints. Additionally, if Z.ro is to handle payments, we’d need aspects like merchant onboarding and QR generation. Lastly, I should note gaps or unknowns to confirm with Z.ro before moving forward.
Thinking:
Listing onboarding requirements
I should create a clear list of documents required for onboarding and necessary data fields. Under "Required from us," I’d note steps for Z.ro commercial onboarding like registering for API access, obtaining API credentials, and configuring webhooks. For each employer's KYB process, I’m thinking of what details to collect, such as CNPJ, address, revenue, and shareholder information, alongside KYC and AML policies. Each employee would need similar documentation for KYC too.
It seems important to separate "What we need from them" and "What we need on our side." The user wants complete clarity, so I’ll make sure to provide both sets of requirements.
Thinking:
Planning wallet/card roadmap
I’m thinking about the wallet/card roadmap and it looks good overall. I see that Pix payments and deposits are confirmed if the funds live at Z.ro, and internal P2P transfers are fine as long as they stay between master and sub-wallets. Also, payment acceptance via Gateway/PaaS is optional for v1, while card endpoints can be delayed for later. I aim for a structured but concise document, targeting around 800 to 1200 words, possibly with bold headers and no nested bullets. I might not need extensive code references or citations.
Thinking:
Considering account structure nuances
I’m thinking about the possibility of using a master account with an internal ledger to track employer balances, which might eliminate the need for individual employer accounts. However, having separate accounts could improve employer control and auditability. It seems essential to clarify whether employer KYB is required if using a pooled master account. I shouldn't exaggerate, so I’ll mention that it likely depends on the custody model for onboarding employers and employees.
Thinking:
Evaluating employee onboarding requirements
I’m considering the situation where we only want one-off Pix payouts to external accounts. I need to ask Z.ro if we can handle the end-recipient KYC ourselves, since the documentation doesn't clarify that. However, our roadmap indicates that employee onboarding through partner KYC is planned for months 2-5, so it seems necessary from a product standpoint. I can confirm that employee onboarding is indeed recommended for version 1 of the product, but maybe not from day one.
Thinking:
Evaluating excluded modules
I'm listing the excluded modules like Crypto as a Service and Cross-border/eFX, while noting that Open Finance won't be available on day one. The white-label app might be an option to speed up UI later. It’s useful to mention that the API is strong but more geared towards partners than individual users, indicating some vendor dependency.
I need to consider regulatory implications, including their payment institution license which could assist with Pix and digital accounts. However, we must handle our own labor and tax mapping for commissions. Z.ro deals with banking rails, not payroll issues.
Thinking:
Highlighting product requirements
I should note that the BaaS documentation includes judicial block webhooks, which is important if we hold user accounts, as court orders can block them. We need our product to manage these events, though it might be a bit advanced to dive into under risks.
Additionally, API requests need nonce and x-transaction-uuid for mutating endpoints, so we’ll need our own request-id/idempotency layer as part of engineering requirements.
I could outline what we need from Z.ro in three areas: the commercial package, APIs/features, and data/docs from our users. In short, Z.ro can cover much of the regulated money movement stack for our Brazil v1.
Thinking:
Considering BaaS setup
I'm thinking about the need for BaaS in this project. We might only require Gateway/PaaS if we want Z.ro to serve as the collection and payment acceptance source of truth. That's a key consideration. Additionally, I realize I have to build the commission engine, internal ledger, reserve logic, employer analytics, and the app itself. There’s quite a bit of groundwork to lay out!
Thinking:
Outlining Z.ro requirements
I'm organizing the must-haves for Z.ro and I see several essential components. First, there's the BaaS product setup with white-labeling and necessary API credentials. Then, the custody/account layer for partner-led models needs to be established. Onboarding flows for employers and employees, along with Pix payout rails for payments, are also crucial. After that, internal funds movement and reconciliation processes must be built. If we want Z.ro to collect payments, the Gateway/PaaS will be needed too. Lastly, I'll have to develop the payment commission rules and the dashboard.
Thinking:
Evaluating product requirements
I’m considering the need for "product_uuid," which seems required for certain endpoints if an authenticated user has multiple products. For the BaaS decode pix key endpoint, it’s definitely needed. It’s good to keep in mind that many endpoints mention "x-product-uuid" as optional, but we should probably use it frequently.
Also, I’m curious about whether gateway webhooks can help with fraud signals by including payer KYC data. However, since it's not central, maybe it's not essential.
I’ll double-check if PaaS supports dynamic split payments because the documentation only references static ones.
Thinking:
Assessing document details
I can mention that the public docs show a static Pix split QR endpoint, but it only allows for percent or absolute account splits rather than earned, available, or settled logic. That’s nice to note! I should also mention that merchant onboarding requires registering a legal person as a commercial establishment at Dock Acquiring; this adds another dependency beyond Z.ro.
While they do have a white-label application and internet banking, I think we might prefer our own employee/employer UX and commission logic. It could be a fallback for a faster MVP, but probably not the primary option.
Z.ro can likely cover most of the regulated rails for our Brazil v1, but not the core commission product.
| Need | Z.ro coverage | Required now? |
|---|---|---|
| Partner-led custody, accounts, wallets | BaaS |
Yes |
| Employer KYB / legal entity onboarding | BaaS legal-person onboarding |
Yes if employers will have Z.ro-backed accounts/wallets |
| Employee KYC / user onboarding | BaaS natural-person onboarding |
Yes for our current roadmap |
Instant payout via Pix |
BaaS Pix payments / deposits / devolutions |
Yes |
| Internal money movement between wallets | BaaS P2P transfers |
Yes |
| Balance, ops, reconciliation, statements | BaaS operations / reports / balance webhooks |
Yes |
| Customer payment collection via Pix/cards | Gateway or PaaS |
Optional for v1 |
| Split collection at payment time | PaaS static split Pix QR |
Optional, not a ledger substitute |
| Cards / stored balance spend | BaaS card endpoints |
Later |
| Commission rules engine, ledger, reserves, analytics | Not provided by Z.ro | We build this |
What we need from Z.ro
- A
BaaSproduct setup for our white-label product, including sandbox access, production access,API ID,API Key, and theproduct_uuidtheir APIs expect. - A custody/account model: ideally one master product plus employer/employee users and wallets, using
x-product-uuid,x-product-target-user-uuid, andx-wallet-uuid. - Employer onboarding flow:
POST /users/accountsPOST /users/onboarding/legal-person- shareholders
- legal representatives
- representative documents
- company documents
- finalize onboarding
- Employee onboarding flow:
POST /users/accountsPOST /users/onboardings- document upload
- onboarding status / webhook handling
- Outbound
Pixpayout flow for employee cash-out. - Internal wallet transfer flow via
POST /v1/operations/p2p-transfers. - Reconciliation and operations visibility via wallet, operations, statements, and webhook events.
- Webhook registration with their team for onboarding status, deposits, payments, devolutions, and balance updates.
What we need to provide
- Our company onboarding to Z.ro and commercial setup.
- For each employer:
- CNPJ
- address and revenue
- shareholders
- legal representatives
- representative docs: selfie, ID, qualification declaration
- company docs: social contract and balance sheet or revenue statement
- For each employee:
- CPF
- address
- nationality / PEP info
- selfie
- RG/CNH or digital identity
- Engineering work:
- HTTPS webhook endpoints
- bearer-token auth flow from
API ID+API Key nonceandx-transaction-uuidgeneration- idempotent webhook/event processing
What we do not need from Z.ro now
- Crypto
- Cross-border / eFX
- Open Finance
- White-label app
- Card issuance on day one
When we would also need Gateway or PaaS
- If we want Z.ro to also be the payment-acceptance layer, not just the payout/custody layer.
- If we want employers to collect customer payments through Z.ro Pix QR or card acquiring.
- If we want their payment webhooks to become the sale/payment source of truth.
Important constraint
- Their public docs do show a split Pix QR endpoint in
PaaS, but it is a simple account split on a static QR. - That is not enough for our core model.
- We still need our own commission engine and internal ledger with
earned,available, andsettled, plus reserves, clawbacks, disputes, and employer analytics.
Best fit recommendation
- Use Z.ro as a
BaaS-firstpartner. - Contract for:
- KYB/KYC
- wallets/accounts
- internal transfers
Pixpayouts- reconciliation webhooks
- Treat
Gateway/PaaSas optional unless we explicitly want to own payment collection from day one.
Questions to resolve with Z.ro before committing
- Can one master product hold funds and create segregated employer/employee wallets, or must every employer have its own full legal-person account?
- Can employees cash out via
Pixwithout a full Z.ro account, or is user onboarding mandatory for our use case? - What are production limits, fees, payout SLAs, and webhook guarantees?
- How do refunds/devolutions interact with already-moved employee balances?
- If we use Gateway, does each employer need separate merchant onboarding at Dock Acquiring?
If useful, I can turn this into a Z.ro diligence checklist or compare this setup directly against Dock, QI Tech, and Celcoin.
User
compare this setup with other potential partners like Dock and Celcoin. The idea I envisioned at first was just using their BaaS and maybe their PaaS.
Assistant (Plan · GPT-5.4 · 16.9s)
Thinking:
Exploring partner comparisons
I need to help the user compare their setup with potential partners like Dock and Celcoin. They mentioned initially considering their BaaS and possibly PaaS. Since I’m in plan mode, I probably should research the public documentation for Dock and Celcoin to compare it with Z.ro.
I’m thinking about using webfetch and perhaps Context7 for any relevant documents. It might be useful to execute multiple webfetch calls to gather the necessary information. I’ll check the docs in the repository for additional insights as well.
Thinking:
Comparing service capabilities
I’m considering using webfetch to gather public documentation for potential partners like Dock and Celcoin. It’s essential to identify their capabilities for BaaS/PaaS, KYB/KYC, and other services. I want to compare the user’s setup, likely Z.ro’s BaaS and possibly PaaS, against these partners.
It seems important to tailor this to our product needs, including commission infrastructure in Brazil. I might also need to check if QI Tech is relevant here, though the focus should remain on Dock and Celcoin. I’ll start by researching their documentation and product pages.
Thinking:
Analyzing BaaS and PaaS capabilities
I need to note the user’s idea of utilizing their BaaS and possibly PaaS. It’s important to analyze whether this combination is sufficient for each partner and what additional components we might need to develop. I want to identify if Dock offers Banking as a Service along with Pix, card capabilities, and accounts. On the other hand, Celcoin provides BaaS, APIs, and Pix/payment collection.
I’m wondering if Z.ro is less mature in comparison with Dock and Celcoin, so I'll need to research this more thoroughly and keep the user updated on my findings before moving forward.
Comparing Z.ro against Dock and Celcoin on the specific stack we need: BaaS first, optional payment acceptance layer, and how much of the commission-flow infrastructure we still have to build ourselves.
Tool: webfetch
Input:
{
"url": "https://dock.tech/en/",
"format": "markdown",
"timeout": 60
}
Output:
Dock - Spread financial power
[Dock](https://dock.tech/en/)
[Dock](#!) [Solutions](#!) [Developers](https://developers.dock.tech/) [Content](https://dock.tech/en/fluid/) [Contact](#!)
[](# "click to search")
**Dock**
Over 25 years dedicated to democratizing access to financial services.
[About](https://dock.tech/en/about/)
We’re reshaping the financial landscape to empower society.
[Career in Dock](https://dock.tech/en/career/)
Maximize your potential without borders; create innovative solutions for leading brands.
[Press room](https://dock.tech/en/press-room/)
Communicating our true impact and commitment to financial inclusion. Access news and official resources.
**Solutions**
Leverage Brazil's largest portfolio of financial solutions to expand and strengthen your business.
[Banking](https://dock.tech/en/solution/banking)
Create your own digital bank and offer payment solutions like Pix.
[Cards & Credit](https://dock.tech/en/solution/cards-credit)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Acquiring](https://dock.tech/en/solution/acquiring)
End-to-end white-label acquiring solutions to transform your business.
[Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
Authentication, detection, and risk prevention throughout your customer journey.
[Dock One](https://dock.tech/en/dock-one/)
A comprehensive platform to scale your operations with global reach.
[LATAM Solutions](https://dock.tech/en/solutions-dock-latam/)
Drive innovation and grow your business.
[Solutions Brazil](#!)
Discover the most complete portfolio of financial services.
[Dock One platform](https://dock.tech/en/dock-one/)
A complete platform to scale your operations with global reach.
[Banking](https://dock.tech/en/solution/banking)
Create your own digital bank and offer payment solutions like Pix.
[Cards & Credit](https://dock.tech/en/solution/cards-credit)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Acquiring](https://dock.tech/en/solution/acquiring)
End-to-end white-label acquiring solutions to transform your business.
[Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
Authentication, detection, and risk prevention throughout your customer journey.
[Dock One](https://dock.tech/en/dock-one/)
A comprehensive platform to scale your operations with global reach.
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/multi-benefit-card/) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado) [Tokenization](https://dock.tech/en/tokenization/)
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
[LATAM Solutions](https://dock.tech/en/solutions-dock-latam/) [Dock Colombia](https://dock.tech/en/countries/colombia/) [Dock Mexico](https://dock.tech/en/countries/mexico/)
[Banking](https://dock.tech/en/solution/banking) [Cards & Credit](https://dock.tech/en/solution/cards-credit) [Acquiring](https://dock.tech/en/solution/acquiring) [Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/multi-benefit-card/) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado) [Tokenization](https://dock.tech/en/tokenization/)
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
**Contact**
We are prepared to serve you in the best possible way.
[Speak to the salesperson](https://dock.tech/en/#contato)
To get in touch with our sales team, click here and complete the form.
[Customer service](https://dock.tech/en/sac/)
For frequently asked questions and customer service, click here.
[Media Inquiries](https://dock.tech/en/press-room/#contato-imprensa)
Please reach out to our communications team.
[Dock](https://dock.tech/en/)
[
](#!)
[Dock](#!) [Solutions](#!) [Developers](https://developers.dock.tech/) [Content](https://dock.tech/en/fluid/) [Contact](#!)
[Dock](#!)
Over 25 years dedicated to democratizing access to financial services.
[About](https://dock.tech/en/about/)
We’re reshaping the financial landscape to empower society.
[Career in Dock](https://dock.tech/en/career/)
Maximize your potential without borders; create innovative solutions for leading brands.
[Press room](https://dock.tech/en/press-room/)
Communicating our true impact and commitment to financial inclusion. Access news and official resources.
[Solutions](#!)
Leverage Brazil's largest portfolio of financial solutions to expand and strengthen your business.
[Banking](#!) [Cards & Credit](#!) [Acquiring](#!) [Fraud Prevention](#!) [Discover our platform](#!) [LATAM Solutions](#!) [Solutions Brazil](#!) [Dock One platform](#!) [Banking](#!) [Cards & Credit](#!) [Acquiring](#!) [Fraud Prevention](#!) [Discover our platform](#!)
[LATAM Solutions](#!)
Drive innovation and grow your business.
[LATAM Solutions](https://dock.tech/en/es/solutions-dock-latam/)
[Solutions Brazil](#!)
Discover the most complete portfolio of financial services.
[Banking](https://dock.tech/en/solution/banking) [Cards & Credit](https://dock.tech/en/solution/cards-credit) [Acquiring](https://dock.tech/en/solution/acquiring) [Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
[Banking](#!)
Create your own digital bank and offer payment solutions like Pix.
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Cards & Credit](#!)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/#cartao-multibeneficio) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado)
[Acquiring](#!)
End-to-end white-label acquiring solutions to transform your business.
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Fraud Prevention](#!)
Authentication, detection, and risk prevention throughout your customer journey.
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[our platform](#!)
A comprehensive platform to scale your operations with global reach.
DOCK ONE **Our layered solutions**
Robust high-tech platform, totalmente personalized and modular thanks to our APIs, in addition to taking care of all the bureaucracy, IT, products, regulatory, licensing and prevention of fraude.
[LEARN MORE](https://dock.tech/en/dock-one)
[Contact](#!)
We are prepared to serve you in the best possible way.
[Talk to Commercial](https://dock.tech/en/#contato)
To get in touch with our sales team, click here and complete the form.
[Customer Service](https://dock.tech/en/sac/)
For frequently asked questions and customer service, click here.
[Media Inquiries](https://dock.tech/en/press-room/#contato-imprensa)
Please reach out to our communications team.
# The most complete financial services infrastructure
for your business
Offer digital accounts, cards with your brand and innovate in payment method services with Pix and acquisition. All with security and prevention fraude.
[LEARN MORE](#contato "click to access")
Your browser does not support the video tag.
## Spread financial power
Be part of the greatest transformation ever seen in financial services and boost your business by spreading financial power around the world.
### Dock One platform
Explore our cloud-native platform, the largest and most comprehensive in Latin America, and discover our solutions.
[Learn more](https://dock.tech/en/dock-one/ "Click and learn more")
### Banking
Elevate the customer experience and increase your profitability with financial solutions integrated into your core business.
[Learn more](https://dock.tech/en/solution/banking/ "Click and learn more")
### Cards & Credit
Offer personalized cards with your brand from major networks, while we take care of the entire operation.
[Learn more](https://dock.tech/en/solution/cards-credit "Click and learn more")
### Acquiring
Have your own white-label acquiring solution using our technology to ensure simplicity and speed in your go-to-market.
[Learn more](https://dock.tech/en/solution/acquiring "Click and learn more")
### Fraud Prevention
Reduce end-to-end risk in your banking, cards, or acquiring business model through solutions that cover everything - from customer onboarding to transaction monitoring.
[Learn more](https://dock.tech/en/solution/fraud-prevention/ "Click and learn more")
### Leader in financial technology in Latin America.
If part of the biggest revolution ever seen in financial services, discover how our integrated solutions can boost your business.
[Discover our solutions](https://dock.tech/en/solutions-dock-latam/ "Click and learn more")
### Dock One platform
Explore our cloud native platform, the largest and most complete in Latin America, and discover our solutions.
[LEARN MORE](https://dock.tech/en/es/dock-one/ "Click and learn more")
Your browser does not support the video tag.
### Dock One platform
Explore our cloud-native platform, the largest and most comprehensive in Latin America, and discover our solutions.
[Learn more](https://dock.tech/en/dock-one/ "Click and learn more")
### Banking
Elevate the customer experience and increase your profitability with financial solutions integrated into your core business.
[Learn more](https://dock.tech/en/solution/banking/ "Click and learn more")
### Cards & Credit
Offer personalized cards with your brand from major networks, while we take care of the entire operation.
[Learn more](https://dock.tech/en/solution/cards-credit "Click and learn more")
### Acquiring
Have your own white-label acquiring solution using our technology to ensure simplicity and speed in your go-to-market.
[Learn more](https://dock.tech/en/solution/acquiring "Click and learn more")
### Fraud Prevention
Reduce end-to-end risk in your banking, cards, or acquiring business model through solutions that cover everything - from customer onboarding to transaction monitoring.
[Learn more](https://dock.tech/en/solution/fraud-prevention/ "Click and learn more")
## Rely on over 20 years of experience from the true one-stop shop in financial services
CARDS **R$ 1,4 trillion**
processed annually.
CARDS
Issuer of **credit, debit and
prepaid cards**
COMPLETE PLATFORM **56**
is the number of financial transactions processed by Dock while you read this card
DIGITAL ACCOUNT **70**
million active accounts in the last 30 days
DOCK **Present in 11 countries**
---
**IP regulada e participante direto Pix** (código bancário #301)
**Regulated PI and direct participant in Pix** (bank code #301)
**La evolución de la tecnología financiera en América Latina.**
PIX **1,3**
billion Pix carried out in the last 12 months
---
DOCK **400+**
Market-leading companies trust Dock
ACQUIRING **30+**
certified networks: Visa ... + 30 networks
---
BANKING
**Provider** Infrastructure provider for payments and banking
**Provider** Infrastructure provider for payments and banking
**Proveedor** de infraestructura de pagos con un conjunto completo de soluciones.
DOCK ONE **Our layered solutions**
Robust high-tech platform, totalmente personalized and modular thanks to our APIs, in addition to taking care of all the bureaucracy, IT, products, regulatory, licensing and prevention of fraude.
ACQUIRING **30+**
certified networks: Visa ... + 30 networks
---
BANKING **Provider**
Infrastructure provider for payments and banking
DOCK ONE **Our layered solutions**
Robust high-tech platform, totalmente personalized and modular thanks to our APIs, in addition to taking care of all the bureaucracy, IT, products, regulatory, licensing and prevention of fraude.
PIX **1,3**
billion Pix carried out in the last 12 months
CARDS **R$ 1,4 trillion**
processed annually.
CARDS
Issuer of **credit, debit and prepaid**
COMPLETE PLATFORM **56**
is the number of financial transactions processed by Dock while you read this card
DIGITAL ACCOUNT **70**
million active accounts in the last 30 days
DOCK **Present in 11 countries**
---
**IP regulada e participante direto Pix** (código bancário #301)
**Regulated PI and direct participant in Pix** (bank code #301)
**La evolución de la tecnología financiera en América Latina.**
**
DOCK **400**
Customers approximately
**
**
## Reliability and security for your transactions
When you choose Dock, you're not just selecting a service; you're choosing a partner dedicated to driving your success.
### Regulated Payment Institution and Direct Pix Participant
Peace of mind knowing your payments are in good hands, with full security and legal backing.
### VISA, MasterCard, Elo Licenses
Accept the leading card networks in the market and offer more options to your customers.
### Adaptable Global Payment Platform
Reach customers worldwide and tailor the experience to meet their needs.
### Comprehensive Infrastructure
A complete solution for online payments, including gateway, fraud prevention, and risk management.
### Recognized Certifications
Commitment to security, quality, and international compliance across all our operations.
### Fraud Prevention
Data and transactions protected with the best tools on the market.
##### Check out the companies that trust our solutions
## Explore Embedded Finance with Dock
Transform your company into a leader in the digital financial market, offering a revolutionary experience for your customers.
### Why choose Dock?
Our expertise and technology enable your company to **promote financial inclusion**, turning customers into active participants and empowering the global economy. We are ready to help **transform your business and make a positive impact**.
### What is Embedded Finance?
Imagine your company not only offering its usual products but also **integrated financial services**. Your platform becomes a financial hub, providing everything from payments to loans, **all within the digital environment**.
[LEARN MORE](https://conteudo.dock.tech/embedded-finance "Click and learn more")
[LEARN MORE](https://conteudo.dock.tech/embedded-finance-en "Click and learn more")
[LEARN MORE](https://conteudo.dock.tech/embedded-finance-es "Click and learn more")
### How does Dock drive this transformation?
Dock leads in financial services, providing the **infrastructure for companies to expand their business**. With our integrated and white-label platform, we help launch customized financial solutions, with seamless integration and agile deployment, combining **innovation and efficiency**.
## Content and events to go further
Discover our exclusive content and events that will unlock even more business potential.
## Content and events to go further
Discover our exclusive content and events that will unlock even more business potential.
## Contents and events to go further
Discover our exclusive content and events that will unlock even more of your business potential.
[
](https://dock.tech/en/fluid/blog/cards-et-credit/alternative-data/ "Alternative data: how new sources of information are transforming the financial system and credit analysis.")
[
Cards & Credit
## Alternative data: how new sources of information are transforming the financial system and credit analysis.
](https://dock.tech/en/fluid/blog/cards-et-credit/alternative-data/ "Alternative data: how new sources of information are transforming the financial system and credit analysis.")[LEARN MORE](https://dock.tech/en/fluid/blog/cards-et-credit/alternative-data/)
[
](https://dock.tech/en/fluid/blog/financial/fintechs-in-Mexico/ "Fintechs in Mexico: trends, opportunities, and challenges in one of the most dynamic scenarios in Latin America.")
[
Financial Universe
## Fintechs in Mexico: trends, opportunities, and challenges in one of the most dynamic scenarios in Latin America.
](https://dock.tech/en/fluid/blog/financial/fintechs-in-Mexico/ "Fintechs in Mexico: trends, opportunities, and challenges in one of the most dynamic scenarios in Latin America.")[LEARN MORE](https://dock.tech/en/fluid/blog/financial/fintechs-in-Mexico/)
[
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")
[
Banking
## How to stand out in the financial services sector in a context of multi-banking.
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/multi-banking/)
[
](https://dock.tech/en/fluid/blog/cards-et-credit/card-processing/ "Card processing and payment methods: what are the trends and how to offer the best customer experience?")
[
Cards & Credit
## Card processing and payment methods: what are the trends and how to offer the best customer experience?
](https://dock.tech/en/fluid/blog/cards-et-credit/card-processing/ "Card processing and payment methods: what are the trends and how to offer the best customer experience?")[LEARN MORE](https://dock.tech/en/fluid/blog/cards-et-credit/card-processing/)
[
...29159 bytes truncated...
The tool call succeeded but the output was truncated. Full output saved to: /home/alex/.local/share/opencode/tool-output/tool_d6250e0070012Wb0Zf6aFXFuV8
Use the Task tool to have explore agent process this file with Grep and Read (with offset/limit). Do NOT read the full file yourself - delegate to save context.
Tool: webfetch
Input:
{
"url": "https://www.celcoin.com.br/en/",
"format": "markdown",
"timeout": 60
}
Output:
Infraestrutura financeira: Banking, Credit, Payments, Regulatory | Celcoin
[](https://www.celcoin.com.br)
- Soluções
Close Soluções Open Soluções
cel\_bricks Plataformas mybenk Open Finance
[cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
Saiba mais como o Embedded Finance da Celcoin pode apoiar o seu negócio.
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [BaaS](https://www.celcoin.com.br/cel_banking/banking-as-a-service/)
- [Banco Liquidante](https://www.celcoin.com.br/cel_banking/banco-liquidante/)
- [Cartão White Label](https://www.celcoin.com.br/cel_banking/cartao-white-label/)
- [Compartilhamento de Dados](https://www.celcoin.com.br/cel_banking/compartilhamento-de-dados/)
- [Core Banking](https://www.celcoin.com.br/cel_banking/core-banking/)
- [Open Insurance](https://www.celcoin.com.br/cel_banking/open-finance-insurance/)
- [Regulatório](https://www.celcoin.com.br/cel_banking/regulatorio/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [Débito Veicular](https://www.celcoin.com.br/cel_payments/debito-veicular/)
- [Débito Veicular White Label](https://www.celcoin.com.br/cel_payments/debito-veicular-white-label/)
- [Gateway de Pagamento](https://www.celcoin.com.br/cel_payments/gateway-de-pagamento/)
- [ITP](https://www.celcoin.com.br/cel_payments/open-finance-itp/)
- [Pagamento de contas](https://www.celcoin.com.br/cel_payments/pagamento-de-contas/)
- [Pix](https://www.celcoin.com.br/cel_payments/pix/)
- [Recargas](https://www.celcoin.com.br/cel_payments/recargas/)
- [Saque e Depósito](https://www.celcoin.com.br/cel_payments/saque-e-deposito/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [CCB](https://www.celcoin.com.br/cel_credit/ccb/)
- [Consignado as a Service](https://www.celcoin.com.br/cel_credit/consignado-as-a-service/)
- [Conta Escrow](https://www.celcoin.com.br/cel_credit/conta-escrow/)
- [Core Credit](https://www.celcoin.com.br/cel_credit/core-credit/)
- [Gestão de Carteira e Cobrança](https://www.celcoin.com.br/cel_credit/gestao-de-carteira-e-cobranca/)
- [Nota Comercial](https://www.celcoin.com.br/cel_credit/nota-comercial/)
[Plataforma de Antecipações](https://www.celcoin.com.br/plataforma-de-antecipacoes/)
Uma plataforma moderna para antecipação de recebíveis com toda a infraestrutura regulatória, tecnológica e operacional da Celcoin.
[Ver solução](https://www.celcoin.com.br/plataforma-de-antecipacoes/)
[mybenk](https://www.celcoin.com.br/mybenk/)
Saiba mais como o mybenk pode apoiar a transformar o universo financeiro interno. Uma solução completa para todos seus stakeholders.
[Ver solução](https://www.celcoin.com.br/mybenk/)
[Open Finance](https://www.celcoin.com.br/open-finance/)
Todas as oportunidades do Open Finance para o seu negócio.
- [ITP](https://www.celcoin.com.br/cel_payments/open-finance-itp/)
- [Pix Automático](https://www.celcoin.com.br/open-finance/pix-automatico/)
- [Pix Inteligente](https://www.celcoin.com.br/open-finance/pix-inteligente/)
- [Pix por Aproximação](https://www.celcoin.com.br/open-finance/pix-por-aproximacao/)
- [Pix Biometria](https://www.celcoin.com.br/open-finance/pix-biometria/)
- [Pix Recorrente](https://www.celcoin.com.br/open-finance/pix-recorrente/)
- [Financial Data](https://www.celcoin.com.br/open-finance/financial-data/)
- [Cadastro Expresso](https://www.celcoin.com.br/open-finance/cadastro-expresso/)
- [Detentora de Conta](https://www.celcoin.com.br/open-finance/detentora-de-conta/)
- Desenvolvedores
Close Desenvolvedores Open Desenvolvedores
Comece a integrar as soluções da Celcoin
[Explorar soluções](https://www.celcoin.com.br/developers/)
Developer
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
- Empresa
Close Empresa Open Empresa
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
[](https://www.celcoin.com.br/partners/)
- Conteúdos
Close Conteúdos Open Conteúdos
CONTEÚDOS
- [Eventos](https://www.celcoin.com.br/eventos/)
- [Insights](https://www.celcoin.com.br/insights/)
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Últimas novidades
[ETFs: como funcionam e o que avaliar antes de investir](https://www.celcoin.com.br/news/investimento-em-etf/)
20 de March de 2026
[Celcoin conquista certificação PCI DSS e reforça segurança como diferencial competitivo no mercado financeiro](https://www.celcoin.com.br/news/celcoin-recebe-certificacao-de-seguranca-pci-dss/)
19 de March de 2026
[Mais de 60% dos consumidores abandonam suas compras após uma experiência negativa](https://www.celcoin.com.br/news/novo-comportamento-do-consumidor-no-varejo/)
19 de March de 2026
[Entrar](#Login)
Qual o seu painel na **Celcoin?**
Cada painel tem sua credencial distinta.
Não tem acesso? **Fale com um especialista**
- cel\_bricks
Acesse o Painel do Cliente para obter relatórios e simplificar a gestão financeira da sua empresa.
- cel\_credit (escrow)
Gerencie sua conta escrow com eficiência e praticidade.
- Gateway de Pagamentos
Gerencie suas finanças com eficiência e praticidade.
Ainda não possui uma conta? **Cadastre-se**
Qual o seu painel na **Celcoin?**
Cada painel tem sua credencial distinta.
- cel\_bricks
- cel\_credit (escrow)
- Gateway de Pagamento
Não tem acesso?
- Criar conta Celcoin (contratar)
- Criar conta Gateway de Pagamento
[Contratar](https://www.celcoin.com.br/contato-celcoin/)
The best service for growth
# Infratech financeira para potencializar negócios
Oferecemos uma infraestrutura completa e pioneira para conectar empresas de todos os segmentos a oportunidades do mercado financeiro, com soluções incorporadas às necessidades de seus clientes. A partir de um novo conceito de Embedded Finance, tudo é feito de uma forma simples, rápida e sem burocracias, deixando toda a parte regulatória com a gente. Isso é Celcoin.
[Fale com um especialista](https://www.celcoin.com.br/contato-celcoin/)
cel\_bricks
## Infraestrutura modularizada com soluções para alavancar seu negócio
### cel\_banking
BaaS, Banco Liquidante, Cartão White Label, Compartilhamento de Dados, Open Insurance e Regulatório.
### cel\_credit
CCB, Conta Escrow, Gestão de Carteira e Cobrança, Nota Comercial e Onboarding.
### cel\_payments
Débito Veicular, Gateway de Pagamento, ITP, Pagamento de Contas, Pix, Recargas e Saque e Depósito.
Clientes
Praticidade
## Experiência financeira mais integrada aos seus clientes e fluxos de receita
- Integração completa com as diferentes plataformas de sua empresa e características.
- Iniciador e detentor de contas de Open Finance e Participante Direto do Pix.
- Licença do Banco Central (BC) para atuar como Instituição de Pagamento.
- Infraestrutura de onboarding, compliance e regulatório.
- Soluções Regulatórias para Instituições de Pagamento (IP) e Sociedades de Crédito Direto (SCD).
Diferenciais Celcoin
## Capacitando o crescimento acelerado no ecossistema financeiro
Aceleração
### Lançamento Rápido
Módulos plug and play e arquitetura SaaS reduzem a complexidade do desenvolvimento e aceleram o lançamento de novos produtos financeiros, melhorando o tempo de geração de receita e a competitividade.
### Arquitetura Modular em APIs
Uma base ampla e a alta qualidade das nossas APIs garantem integrações mais rápidas, reduzindo custos de desenvolvimento e acelerando o go-to-market.
### Experiência e Suporte ao Desenvolvedor
Documentação clara, SDKs e ambientes de sandbox tornam a integração simples e ágil, encurtando ciclos de implementação e reduzindo custos de engenharia.
Segurança
### Prevenção de Fraudes e Controles de Risco
Monitoramento inteligente em tempo real, com uso de IA e autenticação forte, garantindo segurança, reduzindo fraudes e mitigando riscos de compliance.
### Compliance Nativo
KYC, AML e relatórios regulatórios já integrados à infraestrutura reduzem riscos, simplificam auditorias e garantem conformidade total com as normas do Banco Central.
Confiabilidade
### Escalabilidade e Alta Disponibilidade
Infraestrutura cloud-native, estável e de alta performance para sustentar picos de volume com segurança e confiança.
### Ecossistema de Parceiros
Uma rede sólida de bancos, redes de pagamento e fintechs amplia a cobertura de funcionalidades e acelera o acesso a novas oportunidades de negócio.
Expansão
### Distribuição White-Label e Embutida
Nossa infraestrutura white-label permite que empresas ofereçam produtos financeiros com sua própria marca, ampliando a distribuição e reduzindo custos de aquisição de clientes.
### Acesso e Personalização de Dados
Dados do Open Finance e ferramentas de analytics possibilitam ofertas personalizadas, aumentando a conversão e a fidelização de clientes.
### Cobertura dos Meios de Pagamento Locais
Soluções que combinam pagamentos e crédito ampliam conversão, ARPU e fidelização, com total aderência às redes nacionais.
[Conheça todos os diferenciais](https://www.celcoin.com.br/diferenciais-celcoin/)
mybenk
## Solução completa de banking e crédito para todos seus stakeholders
### Aplicativo white label e internet banking
Plataforma completa para todos os casos de usos de seus stakeholders com a marca de sua empresa e totalmente personalizável, garantindo acesso fácil a sua aplicação pela plataforma web ou app.
[Saiba mais](https://www.celcoin.com.br/mybenk/)
Plataforma completa para todos os casos de usos de seus stakeholders com a marca de sua empresa e totalmente personalizável, garantindo acesso fácil a sua aplicação pela plataforma web ou app.
[Saiba mais](https://www.celcoin.com.br/mybenk/)
### Painel backoffice
Gerencie o seu ecossistema diretamente com nosso Painel do Cliente, com todos os relatórios necessários para checar a evolução do seu negócio.
[Saiba mais](https://www.celcoin.com.br/mybenk/)
Nossos números
## A Celcoin no mercado
### +6 mil
Clientes entre bancos digitais, fintechs, instituições financeiras e demais empresas.
### +R$30 Bi
Movimentados mensalmente.
### +400 MM
De transações mensais.
Indústrias
## Soluções financeiras para todos os segmentos
Transformamos operações financeiras em estratégias de crescimento para sua indústria. Oferecemos tecnologia integrada e adaptável para modernizar processos, aumentar a eficiência e gerar novas oportunidades de receita.
[Saiba mais](https://www.celcoin.com.br/industrias/)
## Potencialize seu negócio com o Embedded Finance da Celcoin
Aumente agora seu potencial de negócio com nossa infraestrutura exclusiva para você.
[Fale com um especialista](https://www.celcoin.com.br/contato-celcoin/)
- [](https://www.linkedin.com/company/celcoin-financial-hub/)
- [](https://www.instagram.com/celcoin_/)
- [](https://x.com/celcoinbr)
- [](https://www.youtube.com/channel/UCOz8tQnZl3cV4cI0beQ5pYw)
Soluções
- [cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [mybenk](https://www.celcoin.com.br/mybenk/)
[Indústrias](https://www.celcoin.com.br/industrias/)
- [E-commerce e Marketplace](https://www.celcoin.com.br/industrias/marketplace/)
- [Mercado de Capitais](https://www.celcoin.com.br/industrias/mercado-de-capitais/)
- [Varejo](https://www.celcoin.com.br/industrias/varejo/)
- ERP
- Insurance
- Instituições financeiras
- Utilities
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
Recurso
- [Canal de Denúncias](https://www.celcoin.com.br/canal-de-denuncias/)
- [Compliance e Regulatório](https://www.celcoin.com.br/compliance-e-regulatorio/)
- [Ouvidoria](https://www.celcoin.com.br/ouvidoria/)
- [Seja um parceiro](https://www.celcoin.com.br/partners/)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
Conteúdos
- [Eventos](https://www.celcoin.com.br/eventos/)
- [Insights](https://www.celcoin.com.br/insights/)
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Developers
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
Atendimento Celcoin
De segunda a sexta-feira: das 09h às 18h
Telefone
[(11) 5070-8153](tel:1150708153)
Whatsapp
[(11) 4765-5043](https://wa.me/551147655043)
Suporte
Suporte especializado para ajudar você a extrair o máximo das soluções Celcoin
[Enviar uma solicitação](https://suporte.celcoin.com.br/hc/pt-br/requests/new)
Ouvidoria
De segunda a sexta-feira: das 09h às 17h
Telefone
[0800 591 1852](tel:08005911852)
Soluções
- [cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [mybenk](https://www.celcoin.com.br/mybenk/)
Indústrias
- [E-commerce e marketplace](https://www.celcoin.com.br/industrias/marketplace/)
- [Mercado de capitais](https://www.celcoin.com.br/industrias/mercado-de-capitais/)
- [Varejo](https://www.celcoin.com.br/industrias/varejo/)
- ERP
- Insurance
- Instituições financeiras
- Utilities
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
Recurso
- [Canal de Denúncias](https://www.contatoseguro.com.br/)
- [Compliance e Regulatório](https://www.celcoin.com.br/compliance-e-regulatorio/)
- [Ouvidoria](https://www.celcoin.com.br/ouvidoria/)
- [Seja um parceiro](https://www.celcoin.com.br/partners/)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
Conteúdos
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Developer
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
### Atendimento Celcoin
De segunda a sexta-feira: das 09h às 18h
## Telefone
[0800 591 1457](tel:5070-8153)
## Whatsapp
[(11) 4765-5043](https://wa.me/551147655043)
[Enviar uma solicitação](https://suporte.celcoin.com.br/hc/pt-br/requests/new)
### Ouvidoria
De segunda a sexta-feira: das 09h às 17h
## Telefone
[0800 591 1852](tel:08005911852)
Celcoin Instituição de Pagamento S.A - 13.935.893/0001-09
Al. Xingu, 350 – Conj 1604 – Alphaville Industrial Barueri – SP – 06455-030
[
Configuração de cookies
](https://www.celcoin.com.br/compliance-e-regulatorio/)[
Privacidade e termos
](https://www.celcoin.com.br/compliance-e-regulatorio/)
Tool: webfetch
Input:
{
"url": "https://dock.tech/en/financial-services/banking/",
"format": "markdown",
"timeout": 60
}
Error:
Request failed with status code: 404
Tool: webfetch
Input:
{
"url": "https://www.celcoin.com.br/produtos/banking/",
"format": "markdown",
"timeout": 60
}
Output:
Image fetched successfully
Assistant (Plan · GPT-5.4 · 20.5s)
Thinking:
Comparing setups with partners
I need to help the user compare this setup with other potential partners like Dock and Celcoin. It seems the initial idea was to use their BaaS and maybe PaaS. I’m thinking it’s essential to analyze their documentation and see how our Z.ro setup matches up. While we're in plan mode and can only read, I might need to fetch developer docs for Dock and Celcoin, and maybe even use context7 to gather more insights.
Thinking:
Comparing Z.ro with partners
I should search relevant pages, possibly using multi_tool_use.parallel to gather information. I think webfetch will be suitable for developer pages, while context7 can help with partner documentation. I need to compare our Z.ro BaaS and PaaS setup with Dock and Celcoin, looking at factors like BaaS quality, payment acceptance, compliance, and developer experience.
It's worth noting that if we only use Z.ro's PaaS, customer payment acceptance might not be fully covered, unlike the broader offerings from Dock and Celcoin, who seem more proven in their infrastructure.
Thinking:
Citing public metrics carefully
I need to be cautious about making unsupported claims and stick to what's in the documentation. For Dock, I can mention that they have around 70 million active accounts, are a direct Pix participant, and have 400+ customers with 1.3 billion Pix transactions in 12 months. For Celcoin, they have over 6,000 clients, R$30 billion monthly, and 400 million transactions monthly, also being a direct Pix participant. Z.ro has an A-level Central Bank ranking, a payment institution license, and has transacted 50 billion reals through 100 million transactions.
Comparing the infrastructure layers now: developer surface, regulated rails, payment acceptance breadth, and whether each provider matches a BaaS-first launch without forcing us into a full neobank build.
Tool: webfetch
Input:
{
"url": "https://developers.dock.tech/",
"format": "markdown",
"timeout": 60
}
Output:
ReadMe
Tool: webfetch
Input:
{
"url": "https://developers.celcoin.com.br/docs",
"format": "markdown",
"timeout": 60
}
Output:
Uma breve introdução
[Jump to Content](#content)
[](/)
[Documentação](/docs)[Recipes](/recipes)[API](/reference)[Ask AI](javascript:window.Kapa.open\(\))v2.0.0v2.0.1
---
[Status Page](/page/status-page)[Suporte](https://suporte.celcoin.com.br/hc/pt-br/requests/new?ticket_form_id=4553742630939)[](/)
Documentação
Search
[Status Page](/page/status-page)[Suporte](https://suporte.celcoin.com.br/hc/pt-br/requests/new?ticket_form_id=4553742630939)
v2.0.0
[Documentação](/docs)[Recipes](/recipes)[API](/reference)[Ask AI](javascript:window.Kapa.open\(\))
Uma breve introdução
All
Pages
###### Start typing to search…
## Introdução
- [Uma breve introdução](/docs/bem-vindo-à-api-da-rede-celcoin)
- [Credenciais de acesso](/docs/obtendo-acesso-às-apis)
- [Segurança da API](/docs/segurança-da-api)
- [Idempotência das APIs](/docs/idempotência-das-apis)
- [Certificado mTLS](/docs/mtls)
- [Controle de taxa (rate-control)](/docs/controle-de-taxa-rate-control)
- [Faça sua primeira consulta](/docs/tutorial-de-uso-da-api)
- [Arquivo de movimentação via SFTP](/docs/arquivo-de-movimentação-via-sftp)
- [Servidor MCP da Celcoin](/docs/use-nosso-mcp-server)
## Homologação
- [Instruções para homologar](/docs/homologacao-celcoin)
## cel\_banking - BaaS & Core
- [Sobre o BaaS & Core Banking](/docs/sobre-o-baas)
- [Follow the Money (Antifraude e PLD)](/docs/follow-the-money-ftm)
- [Abertura de Contas (KYC)](/docs/utilizacao-do-onboarding-celcoin)
- [Criação de Contas (Onboarding)](/docs/utilizacao-do-onboarding-celcoin)
- [Informações financeiras](/docs/informações-financeiras-1)
- [Webhooks Onboarding](/docs/webhooks-onboarding)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/categories/26054953034011-Onboarding-KYC)
- [Gestão de Contas](/docs/gestão-de-contas)
- [Criar Conta - Apenas Core Banking](/docs/criar-conta)
- [Informações financeiras](/docs/informações-financeiras)
- [Atualizar Dados do Cliente](/docs/atualizar-dados-da-conta)
- [Desativar / Encerrar uma Conta](/docs/desativar-excluir-a-conta)
- [Listar Contas](/docs/listar-contas)
- [Tabela de erros Gestão de Contas](/docs/tabela-de-erros-gestão-de-contas)
- [Número de contas](/docs/numero-de-contas)
- [Bloqueios Judiciais](/docs/bloqueio-judiciais)
- [Atualização de Status de Conta](/docs/atualização-de-status-de-conta)
- [Adicionar Saldo (em sandbox)](/docs/gerar-lançamento)
- [Relatórios](/docs/relatórios-2)
- [Consultar Saldo](/docs/consultar-saldo-1)
- [Saldo Dia & Movimentações Diárias Consolidadas](/docs/consultar-saldo-do-dia)
- [Consultar Extrato](/docs/consultar-extrato-1)
- [Consultar Extrato Detalhado](/docs/consultar-extrato-copy)
- [Consultar Transações do Extrato](/docs/consultar-transacoes-extrato)
- [Pix](/docs/sobre-o-pix)
- [Sobre o Pix](/docs/sobre-o-pix)
- [Implantação](/docs/pix-implantação)
- [Cash-in (Receber)](/docs/pix-cash-in-receber)
- [Receber um Pix Cash-in por Agência e Conta](/docs/receber-um-pix-cash-in-agencia-e-conta)
- [Receber um Pix Cash-in por Chave Aleatória](/docs/receber-um-pix-cash-in-por-chave-aleatoria)
- [Receber um Pix Cash-in por Chaves Individualizadas](/docs/receber-um-pix-cash-in-por-chaves-individualizadas)
- [Receber um Pix Cash-in por Cobrança estática](/docs/receber-um-pix-cash-in-por-cobranca-estatica)
- [Receber um Pix Cash-in por QR Code dinâmico (immediate)](/docs/receber-um-pix-cash-in-por-qr-code-dinamico-immediate)
- [Receber um Pix Cash-in por QR Code dinâmico(duedate)](/docs/receber-um-pix-cash-in-por-qr-code-dinamico-duedate)
- [Bloqueio Cautelar - Recebimento Pix](/docs/bloqueio-cautelar-recebimento-pix)
- [Consulta de recebimentos Pix](/docs/redirecionamento-consulta-de-recebimentos-pix)
- [Devolver um Pix Cash-in](/docs/realizar-devolução-de-recebimento-pix)
- [Modelo Webhook](/docs/webhook-cash-in)
- [Split Pix](/docs/split-pix)
- [Split de Pix Cash-in por QR Code dinâmico(duedate)](/docs/split-de-pix-cash-in-por-qr-code-dinâmicoduedate)
- [Split de Pix Cash-in por QR Code dinâmico (immediate)](/docs/split-de-pix-cash-in-por-qr-code-dinâmico-immediate)
- [Cash-out (Pagamento)](/docs/pix-cash-out-pagamento)
- [DICT](/docs/dict-2)
- [Consultar Chaves Pix Externa (DICT)](/docs/consultar-chaves-pix-externa-dict)
- [Realizar um Pix Cash-Out por Agência e Conta](/docs/realizar-um-pix-cash-out)
- [Realizar um Pix Cash-Out por Chaves Pix](/docs/realizar-um-pix-cash-out-por-chaves-pix)
- [Realizar um Pix Cash-Out por QR Code Estático](/docs/realizar-um-pix-cash-out-por-qr-code-estático)
- [Realizar um Pix Cash-Out por QR Code Dinâmico](/docs/realizar-um-pix-cash-out-por-qr-code-dinâmico)
- [Consultar transferências, pagamentos e devoluções de Pix-Out](/docs/verifica-o-status-de-uma-transação-pix)
- [Modelo Webhook](/docs/modelo-webhook-cash-out)
- [Gerenciamento de Chaves](/docs/pix-gerenciamento-de-chaves)
- [Cadastrar uma Chave Pix](/docs/cadastrar-uma-chave-pix)
- [Excluir Chaves Pix de uma Conta](/docs/excluir-chaves-pix-de-uma-conta)
- [Consultar Chaves Pix de uma Conta](/docs/consultar-chaves-pix-de-uma-conta-copy)
- [Alteração de nome em uma chave Pix](/docs/alterar-chaves-pix)
- [Portabilidade e Reivindicação de Chaves](/docs/portabilidade-reivindicacao-de-chaves-pix)
- [Primeiros passos para Portabilidade e Reivindicação de Chaves Pix](/docs/primeiros-passos-para-portabilidade-e-reivindicação-de-chaves-pix)
- [Solicitar Portabilidade de Chave Pix](/docs/solicitar-portabilidade-de-chave-pix)
- [Responder Portabilidade de Chave Pix](/docs/responder-portabilidade-de-chave-pix)
- [Consultar pedidos de Portabilidade ou Reivindicação](/docs/consultar-pedidos-de-portabilidade-ou-reinvindicacao)
- [Tabela de erros portabilidade PIX](/docs/tabela-de-erros-portabilidade-pix)
- [Pix Automático](/docs/pix-automático-baas)
- [Jornada Pagadora](/docs/jornada-pagadora-baas)
- [Autorização - Visão Geral](/docs/autorização-pagador-baas)
- [Autorização - Jornada 1](/docs/autorização-jornada-1-baas)
- [Autorização - Jornada 2](/docs/autorização-jornada-2-baas)
- [Autorização - Jornada 3](/docs/autorização-jornada-3-baas)
- [Autorização - Jornada 4](/docs/autorização-jornada-4-baas)
- [Agendamento](/docs/agendamento-pagador-baas)
- [Liquidação](/docs/liquidação-pagador-baas)
- [Cancelamento do Consentimento](/docs/cancelamento-pagador-baas)
- [Cancelamento de agendamento](/docs/cancelamento-do-consentimento-copy)
- [Consultas - Visão Pagador](/docs/consultas-visão-pagador)
- [Jornada Recebedora](/docs/jornada-recebedora)
- [Autorização - Jornada 1](/docs/recebedora-jornada-1)
- [Autorização - Jornada 2](/docs/recebedora-jornada-2-baas)
- [Autorização - Jornada 3](/docs/recebedora-jornada-2-copy)
- [Autorização - Jornada 4](/docs/recebedora-jornada-3-copy)
- [Envio de Agendamento](/docs/recebedora-envio-de-agendamento)
- [Liquidação](/docs/recebedora-envio-de-agendamento-copy)
- [Retentativas de Recebimento](/docs/recebedora-retentativas-de-recebimento)
- [Cancelamento de Agendamento](/docs/recebedora-cancelamento-de-agendamento-baas)
- [Cancelamento de Recorrência](/docs/recebedora-cancelamento-de-pix-automático)
- [Motivos de rejeição pelo participante pagador](/docs/motivos-de-rejeição-pelo-participante-pagador)
- [Pix Inteligente - Sweeping Accounts](/docs/pix-inteligente-sweeping-accounts)
- [Listar marcas do Diretório de Participantes](/docs/copy-of-listar-marcas-no-diretório-de-participantes-do-open-finance)
- [Criar consentimento](/docs/copy-of-criar-consentimento)
- [Callback do Consentimento](/docs/copy-of-callback-do-consentimento)
- [Cancelamento de consentimento](/docs/copy-of-cancelamento-de-consentimento)
- [Listar Consentimentos](/docs/copy-of-listar-consentimentos)
- [Buscar informações de um consentimento](/docs/copy-of-buscar-informações-de-um-consentimento)
- [Criar um Pix inteligente recorrente](/docs/copy-of-pix-inteligente)
- [Pix Indireto](/docs/sobre-o-pix-indireto-baas)
- [Sobre o Pix Indireto](/docs/sobre-o-pix-indireto-baas)
- [Pré-requisitos do Participante](/docs/pré-requisitos-do-participante-baas)
- [Fases do processo de adesão do Participante Indireto](/docs/fases-do-processo-de-adesão-do-participante-indireto-baas)
- [DICT (Diretório de Identificadores de Contas Transacionais)](/docs/gestão-de-chaves-pix-baas)
- [Gestão de Chaves Pix](/docs/gestão-de-chaves-pix-baas)
- [Portabilidade e Reivindicação](/docs/portabilidade-e-reivindicação-baas)
- [Infrações](/docs/infrações-baas)
- [Mecanismo Especial de Devoluções (MED)](/docs/mecanismo-especial-de-devoluções-med-baas)
- [Agendador de Transação Pix](/docs/agendador-de-transacoes)
- [Agendar uma transação Pix](/docs/agendar-uma-transação-pix)
- [Consultar Pix agendado](/docs/consultar-pix-agendado)
- [Cancelar um Pix agendado](/docs/cancelar-pix-agendado)
- [Consultar Lista de Transações agendadas](/docs/consultar-transacoes-agendadas)
- [Emissão de Boletos](/docs/cobrancas-avulsas)
- [Emitir Boleto/Cobrança](/docs/criar-uma-cobrança-avulsa)
- [Emitir Boleto/Cobrança com Split de Pagamento](/docs/criar-uma-cobrança-avulsa-com-split)
- [Criar um PDF para uma Cobrança](/docs/criar-um-pdf-para-uma-cobrança)
- [Consultar Boleto Emitido](/docs/consultar-cobranca-avulsa)
- [Consultar Boletos por Período](/docs/consultar-cobrança-periodo)
- [Cancelar Boleto Emitido](/docs/cancelar-uma-cobrança-avulsa)
- [CNAB](/docs/modulo-cnab-baas)
- [Processar, Consultar e Baixar CNAB](/docs/processar-um-arquivo-cnab)
- [Subadquirência e AaaS (Acquiring as a Service)](/docs/subadquirencia)
- [Credenciamento na Subadquirência](/docs/credenciamento-sub-adquirência)
- [Validação de Status da Conta](/docs/listar-conta)
- [Cobrança avulsa no Cartão de Crédito](/docs/cobrança-avulsa-cartão-de-crédito)
- [Criar Cobrança Avulsa](/docs/criar-cobrança-avulsa)
- [Listar Cobranças Avulsas](/docs/listar-cobrança-avulsa)
- [Editar Cobrança Avulsa](/docs/editar-cobrança-avulsa)
- [Retentar Cobrança Avulsa](/docs/retentar-cobrança-avulsa)
- [Estornar Cobrança Avulsa](/docs/estornar-cobrança-avulsa)
- [Cancelar Cobrança Avulsa](/docs/cancelar-cobrança-avulsa)
- [Disputas e Chargebacks](/docs/gestão-de-chargebacks)
- [Listar Chargebacks](/docs/listar-chargebacks)
- [Enviar Documentação de Defesa do Chargeback](/docs/enviar-documentação-de-defesa-do-chargeback)
- [Desistir da Disputa dos Chargeback](/docs/desistir-da-disputa-dos-chargeback)
- [Cadastrar Webhooks de Chargeback](/docs/cadastro-de-webhooks-de-chargeback)
- [Clientes](/docs/clientes)
- [Criar Cliente](/docs/criar-cliente)
- [Listar Clientes](/docs/listar-clientes)
- [Editar Cliente](/docs/editar-cliente)
- [Excluir Cliente](/docs/excluir-cliente)
- [Planos](/docs/planos)
- [Criar Plano](/docs/criar-plano)
- [Listar Planos](/docs/listar-planos)
- [Editar Plano](/docs/editar-plano)
- [Excluir Plano](/docs/excluir-plano)
- [Cartões](/docs/cartões)
- [Criar Cartão](/docs/criar-cartão)
- [Listar Cartões](/docs/listar-cartões)
- [Inativar Cartão](/docs/inativar-cartão)
- [Assinaturas e Contratos](/docs/assinaturas-e-contratos)
- [Criar Assinatura/Contrato Manual](/docs/criar-assinaturacontrato-manual)
- [Adicionar Transação](/docs/adicionar-uma-transação)
- [Webhooks](/docs/configurar-webhooks)
- [Tokenização de Cartão via JS](/docs/tokenização-de-cartão-via-js)
- [Pagamento de boletos](/docs/pagamento-de-boletos-tributos)
- [Realizar um pagamento de boletos](/docs/realizar-um-pagamento-de-boletos)
- [Consultar Status de uma pagamento de Boleto](/docs/consultar-status-de-pagamento-de-boleto)
- [Transferência entre contas](/docs/transferencia-entre-contas)
- [Transferência entre contas internas](/docs/transferência-entre-contas-baas)
- [Consulta status da uma transferência entre contas](/docs/consultar-status-de-um-transferência-entre-contas-baas)
- [TED](/docs/transferencia-ted)
- [Recebendo Transferências TED na sua Conta BaaS](/docs/receber-uma-transferência-ted)
- [Realizar uma Transferência via TED](/docs/realizar-uma-transferência-via-ted)
- [Consultar status de um transferência TED](/docs/consultar-status-de-um-transferência-ted)
- [Modelos Webhooks](/docs/webhooks-2)
- [Débito Veicular](/docs/debito-veicular-baas)
- [Consultar Débitos Veiculares](/docs/consultar-débitos-veiculares)
- [Efetivar Pagamento de Débitos Veiculares](/docs/efetivar-pagamento-de-débitos-veiculares)
- [Débitos Dependentes, Distintos e Obrigatórios](/docs/débitos-dependentes-distintos-e-obrigatórios-baas)
- [Massa de Testes Débito Veicular](https://docs.google.com/spreadsheets/d/1y_vPJ6_yOIm6JRsXIz9On6HUBMKyFxrm/edit?usp=sharing&ouid=111561115532951179309&rtpof=true&sd=true)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/categories/26366884684571-D%C3%A9bito-Veicular)
- [Recargas](/docs/recarga)
- [Consulta de operadoras e valores](/docs/consulta-de-operadoras-e-valores)
- [Realizar uma recarga](/docs/realizar-uma-recarga)
- [SLC (domicílio de arranjo de cartões)](/docs/recebimento-de-cartoes-slc)
- [Recebimento de liquidações do arranjo de cartões via SLC (Domicílio Bancário)](/docs/recebimento-de-cartoes-slc)
- [Informe de Rendimentos](/docs/informe-de-rendimentos)
- [Informe de Rendimentos PF](/docs/informe-de-rendimentos-pf)
- [Informe de Rendimentos PJ](/docs/informe-de-rendimentos-pj)
- [Iniciador de Transação de Pagamento (ITP)](/docs/open-keys-itp-copy)
- [Portal de configurações do Open Keys](/docs/portal-de-configurações-do-open-keys-copy)
- [Dashboard](/docs/dashboard-copy)
- [Lista de Transações](/docs/lista-de-transações-copy)
- [Relatório de Transações](/docs/relatório-de-transações)
- [Configurações da jornada de pagamentos](/docs/configurações-da-jornada-de-pagamentos-copy)
- [Demo das Jornadas de Pagamento](/docs/demo-das-jornadas-de-pagamento-copy)
- [Demo da Área de Gestão](/docs/demo-da-área-de-gestão-copy)
- [Jornadas White Label](/docs/jornadas-white-label-copy)
- [Iniciação de Pagamento Instantâneo](/docs/iniciação-de-pagamento-instantâneo-copy)
- [Gestão de Pagamentos Instantâneos](/docs/gestão-de-pagamentos-instantâneos-copy)
- [Iniciação de Pagamento Agendado](/docs/iniciação-de-pagamento-agendado-copy)
- [Gestão de Pagamentos Agendados](/docs/gestão-de-pagamentos-agendados-copy)
- [Iniciação de Pagamento sem Redirecionamento](/docs/iniciação-de-pagamento-sem-redirecionamento-copy)
- [Gestão de Contas Salvas (Vínculos)](/docs/gestão-de-contas-salvas-vínculos-copy)
- [FAQ Open Keys](/docs/faq-open-keys-copy)
- [Pix por Aproximação](/docs/pix-por-aproximação-copy)
- [Jornada Pay by Link](/docs/jornada-pay-by-link-copy)
- [Documentação técnica](/docs/documentação-técnica-copy)
- [Status e respostas: Máquina de estados](/docs/status-e-respostas-máquina-de-estados-copy)
- [Status e respostas: Códigos de resposta HTTP](/docs/status-e-respostas-códigos-de-resposta-http-copy)
- [Status e respostas: Possíveis erros de pagamentos](/docs/status-e-respostas-possíveis-erros-de-pagamentos-copy)
- [Diagrama de sequência: Jornada com Redirecionamento](/docs/diagrama-de-sequência-jornada-com-redirecionamento-copy)
- [Diagrama de sequência: Jornada sem Redirecionamento](/docs/diagrama-de-sequência-jornada-sem-redirecionamento-copy)
- [Webhook](/docs/webhook-copy)
- [APIs](/docs/apis-copy)
- [🚀 ITP – Jornada de Pagamento com Redirecionamento](/docs/itp-jornada-de-pagamento-com-redirecionamento)
- [Open Finance as a Service](/docs/marcas-no-open-finance)
- [Marcas no Open Finance](/docs/marcas-no-open-finance)
- [Listar marcas no Diretório de Participantes do Open Finance](/docs/listar-marcas-no-open-finance)
- [Obter detalhes de marcas no Open Finance](/docs/obter-detalhes-de-marcas-no-open-finance)
- [Uso e disponibilização de logotipos](/docs/copy-of-instituições-no-open-finance)
- [Termos e Condições de uso](/docs/copy-of-uso-e-disponibilização-de-logotipos)
- [Recepção de Dados](/docs/copy-of-fluxo-de-utilização-da-api-de-dados-1)
- [Webhooks](/docs/webhooks-baas)
- [Cadastrar e Gerenciar Webhooks](/docs/gerenciamento-de-webhook)
- [Reenvio de Webhook](/docs/reenvio-de-webhook)
- [Templates de Webhooks do BaaS](/docs/templates-de-webhooks-do-baas)
- [Bloqueio/desbloqueio de saldo por infração](/docs/bloqueiodesbloqueio-de-saldo-por-infração)
- [Tabela de erros BaaS](/docs/tabela-de-erros-mapeados)
## cel\_banking - cards
- [Sobre cel\_card](/docs/cel_card)
- [Comece a Emitir Cartões](/docs/comece-a-emitir-cartões)
- [Gestão de Conta Cartão](/docs/onboarding)
- [Criar uma Conta Cartão (Onboarding)](/docs/copy-of-criar-conta-cartão-onboarding)
- [Atualizando Dados Cadastrais da Conta Cartão](/docs/onboarding-copy)
- [Consultando dados de uma Conta Cartão](/docs/copy-of-consultando-dados-de-uma-conta-cartão)
- [Limites da Conta Cartão](/docs/limites-da-conta-cartão)
- [Cancelamento de conta e cartão](/docs/copy-of-bia-consultando-fatura-4)
- [Endereços](/docs/endereço)
- [Cria um novo endereço para uma conta](/docs/cria-um-novo-endereço-para-uma-conta)
- [Alteração de endereço de entrega](/docs/alteração-de-endereço-de-entrega)
- [Listar endereços de uma conta](/docs/listar-endereços-de-uma-conta)
- [Emissão de Cartões](/docs/emissão-de-cartões)
- [Emissão/Geração de Cartão](/docs/emissão-de-cartão-físico)
- [Emissão de 2ª via de cartão](/docs/emissão-de-2a-via-de-cartão)
- [Rastreio de Cartões](/docs/rastreio-de-cartões)
- [Consulta de rastreio](/docs/consulta-de-rastreio)
- [Simulação de Rastreio do Cartão](/docs/simulação-de-rastreio-do-cartão)
- [Gestão de Cartões](/docs/gestão-de-cartão)
- [Ativação](/docs/ativação)
- [Listagem de Cartões](/docs/listagem-de-cartões)
- [Configuração de contactless (NFC)](/docs/configuração-de-contactless)
- [Gestão de senha](/docs/gestão-de-senha)
- [Alteração de Senha do Cartão - Pin Online e Pin Offline](/docs/copy-of-pin-on-line-e-pin-off-line)
- [Visualização dos dados do cartão](/docs/visualização-dos-dados-do-cartão)
- [Simulador de Transações](/docs/simulador-de-transacao)
- [Webhooks](/docs/webhooks-cartoes)
- [Cadastrar e Gerenciar Webhooks](/docs/cadastrar-e-gerenciar-webhooks)
- [Template de Webhooks](/docs/modelo-de-webhooks)
- [Reenvio de Webhook Pendente](/docs/reenvio-de-webhook-1)
- [Entendendo a Fatura](/docs/copy-of-bia-consultando-fatura-5)
- [Consultando dados de fatura](/docs/bia-consultando-fatura)
## cel\_credit
- [Autenticação](/docs/autenticação)
- [Produtos](/docs/produtos)
- [Variáveis Personalizadas](/docs/variáveis-personalizadas)
- [Pessoas](/docs/pessoas)
- [Campos da Pessoa](/docs/campos-da-pessoa)
- [Empresas](/docs/empresas)
- [Campos Empresa](/docs/campos-empresa)
- [Responsáveis Legais](/docs/responsáveis-legais)
- [Documentos](/docs/documentos)
- [Solicitações](/docs/solicitações)
- [Campos de Solicitação](/docs/campos-de-solicitação)
- [Simulações](/docs/simulações)
- [Status de Solicitação](/docs/status-de-solicitacao)
- [Tabela de Erros de Geração de Boleto](/docs/tabela-de-erros-de-geração-de-boleto)
- [Assinatura](/docs/assinatura)
- [Modalidades](/docs/modalidades)
- [Clicksign](/docs/clicksign)
- [UNICO](/docs/unico)
- [ZapSign](/docs/zapsign)
- [Webhooks](/docs/webhooks-1)
- [Consignado Crédito Trabalhador](/docs/consignado-crédito-trabalhador)
- [Modalidade com Leilão Interno](/docs/modalidade-com-leilão-interno)
- [Solicitação de Proposta & Distribuição aos Originadores](/docs/solicitação-de-proposta-distribuição-aos-originadores)
- [Oferta, Leilão, Devolutiva & Emissão](/docs/envio-da-oferta-leilão-interno-devolutiva)
- [Modalidade sem Leilão](/docs/modalidade-sem-leilao)
- [Solicitação & Consentimento do Tomador](/docs/solicitação-consentimento-do-tomador)
- [Consulta de Margem & Simulação de Crédito](/docs/consulta-de-margem-simulação-de-crédito)
- [Cadastro do Tomador, Emissão & Cancelamento](/docs/cadastro-do-tomador-emissão-cancelamento-1)
- [Guia rápido consignado](/docs/guia-rápido-consignado)
- [Falhas de Averbação – Integração Dataprev](/docs/erros-de-averbação-integração-dataprev)
- [Status da Operação](/docs/status-da-operação)
- [Consultas, Escriturações e Repasses](/docs/consultas-escriturações-e-repasses)
- [Empréstimo Consignado Servidores do Exército](/docs/empréstimo-consignado-servidores-do-exército)
- [Autenticação](/docs/autenticação-3)
- [Consulta de margem](/docs/consulta-de-margem-2)
- [Simulação da CCB](/docs/simulação-da-ccb-1)
- [Criação do tomador](/docs/criação-do-tomador)
- [Compra com troco](/docs/compra-com-troco)
- [Status da Operação](/docs/status-da-operação-3)
- [Conta escrow](/docs/conta-escrow)
- [Onboarding conta escrow](/docs/onboarding-conta-escrow)
- [Fluxo essencial](/docs/fluxo-essencial)
- [Depósitos](/docs/depósitos)
- [Destinatários e Cobranças (Charges)](/docs/destinatários-e-cobranças-charges)
- [Permissões](/docs/permissões)
- [Portabilidade de Crédito](/docs/portabilidade-de-crédito)
- [Portabilide de Crédito do Trabalhador](/docs/portabilide-de-crédito-do-trabalhador)
- [Portabilidade no ambiente do originador](/docs/portabilidade-no-ambiente-do-originador)
- [Simulação de portabilidade de crédito do trabalhador](/docs/simulação-de-portabilidade-de-crédito-do-trabalhador-1)
- [Autorização de consulta & consulta de vículo empregatício](/docs/autorização-de-consulta-consulta-de-vículo-empregatício)
- [Cadastro do tomador & emissão da CCB de portabilidade](/docs/cadastro-do-tomador-emissão-da-ccb-de-portabilidade)
- [Proposta de portabilidade e resposta a proposta](/docs/proposta-de-portabilidade-e-retorno-da-proposta)
- [Averbação por portabilidade & envio de contrato](/docs/averbação-por-portabilidade)
## cel\_banking - embedded solutions
- [Conta Celcoin](/docs/conta-celcoin)
- [DDA](/docs/sobre-dda)
- [Sobre DDA](/docs/sobre-dda)
- [Tabela de erros](/docs/tabela-de-erros-2)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/sections/26051983538971-D%C3%A9bito-Direto-Autorizado-DDA)
- [Débitos Veiculares](/docs/sobre-a-api-de-auto)
- [Sobre a API de Débito Veicular](/docs/sobre-a-api-de-auto)
- [Enriquecimento de Placas](/docs/enriquecimento-de-placas-debito-veicular)
- [Débitos Dependentes, Distintos e Obrigatórios](/docs/débitos-dependentes-distintos-e-obrigatórios)
- [Cadastro de Webhook com Autenticação Via Token - JWT](/docs/cadastro-de-webhook-com-autenticação-via-token-jwt)
- [Idempotencia](/docs/idempotencia)
- [Tabela de erros](/docs/tabela-de-erros-3)
- [Massa de Testes Débito Veicular](https://docs.google.com/spreadsheets/d/1y_vPJ6_yOIm6JRsXIz9On6HUBMKyFxrm/edit?usp=sharing&ouid=111561115532951179309&rtpof=true&sd=true)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/categories/26366884684571-D%C3%A9bito-Veicular)
- [Emissão de Nota Fiscal de Serviço (NFs-e)](/docs/sobre-a-api-de-emissão-nfse)
- [Sobre a API de Emissão de Nota Fiscal de Serviços (NFs-e)](/docs/sobre-a-api-de-emissão-nfse)
- [Tabela de Erros](/docs/tabela-de-erros-nfse)
- [Emissão de Boletos - Conta Única (Direto)](/docs/emissao-de-boletos)
- [Gestão de Beneficiários](/docs/gestao-beneficiario-direto)
- [Gestão de Carteiras](/docs/gestao-de-carteiras-direto)
- [Gestão de Emissão de Boletos](/docs/gestao-de-emissao-boletos)
- [Gestão de Baixa de Boletos](/docs/gestao-de-baixa-boletos)
- [Tabelas de Erros - Emissão Celcoin](/docs/tabela-erros-emissao-de-boletos-celcoin)
- [Pagamento de contas](/docs/pagamento-de-contas-1)
- [Sobre as APIs de Pagamento de Contas](/docs/pagamento-de-contas-1)
- [Devolução de pagamento de conta](/docs/devolução-de-pagamento-de-conta)
- [Massa de dados para testes](/docs/massa-de-dados-para-teste)
- [Tabelas de erros das APIs](/docs/tabelas-de-erros)
- [Lista de Convênios](https://developers.celcoin.com.br/page/conv%C3%AAnios-pagamento-contas)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/categories/26051936372763-Pagamento-de-contas-e-DDA)
- [Pix](/docs/pix-avulso)
- [Pix - Avulso](/docs/pix-avulso)
- [Recargas](/docs/sobre-recargas-nacionais)
- [Sobre recargas nacionais](/docs/sobre-recargas-nacionais)
- [Termos de uso](https://docs.google.com/spreadsheets/d/e/2PACX-1vR8XRItuBRRxO4ioui90L-NRLuRRORzFoFoHVDKZvwDeZDqeyx2OokgVJMzv3otlA/pubhtml)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/categories/26344423891867-Recargas)
- [Saques e depósitos físicos](/docs/saques-e-depósitos)
- [Sobre Saques e depósitos](/docs/saques-e-depósitos)
- [TED](/docs/sobre-as-transferências)
- [Sobre as transferências via TED](/docs/sobre-as-transferências)
- [Tabela de erros ao realizar uma TED](/docs/tabela-de-erros)
- [Conciliação](/docs/redirecionamento-api-para-conciliacao)
- [APIs para Conciliação](/docs/redirecionamento-api-para-conciliacao)
## CEL\_BRICKS WEBHOOKS
- [Webhook Manager](/docs/celbricks-cadastrar-e-gerenciar-webhooks)
- [Cadastrar e Gerenciar Webhooks](/docs/celbricks-cadastrar-e-gerenciar-webhooks)
- [Reenvio de Webhook](/docs/celbricks-reenvio-de-webhook)
## cel\_open
- [Jornada Com redirecionamento](/docs/jornada-com-redirecionamento)
- [Documentação Técnica - API](/docs/documentação-técnica-api)
- [Criar Iniciação de Pagamento](/docs/criar-iniciação-de-pagamento-1)
- [Callback da Iniciação de Pagamento](/docs/callback-da-iniciação-de-pagamento)
- [PIX](/docs/pix-1)
- [Documentação Técnica - WL](/docs/criar-jornada-de-pagamento-1)
- [Criar Jornada de Pagamento](/docs/criar-jornada-de-pagamento-1)
- [Listar Jornadas de Pagamento](/docs/listar-jornadas-de-pagamento-1)
- [Buscar Jornada de Pagamento](/docs/buscar-jornada-de-pagamento-1)
- [Jornada Sem Redirecionamento](/docs/jornada-sem-redirecionamento)
- [Criar vínculo](/docs/criar-vínculo)
- [Pagamento](/docs/pagamento)
- [Documentação Técnica - API](/docs/documentação-técnica-1)
- [Criar Vínculo](/docs/criar-vínculo-1)
- [Callback do Vínculo](/docs/callback-do-vínculo)
- [FIDO Registration Options](/docs/fido-registration-options)
- [FIDO Registration](/docs/fido-registration)
- [Criar Iniciação de Pagamento](/docs/criar-iniciação-de-pagamento)
- [FIDO Sign Options](/docs/fido-sign-options)
- [Autorização FIDO](/docs/autorização-fido)
- [PIX](/docs/pix)
- [Documentação Técnica - WL](/docs/criar-jornada-de-vínculo)
- [Criar Jornada de Vínculo](/docs/criar-jornada-de-vínculo)
- [Listar Jornadas de Vínculo](/docs/listar-jornadas-de-vínculo)
- [Buscar Jornada de Vínculo](/docs/buscar-jornada-de-vínculo)
- [Criar Jornada de Pagamento](/docs/criar-jornada-de-pagamento)
- [Listar Jornadas de Pagamento](/docs/listar-jornadas-de-pagamento)
- [Buscar Jornada de Pagamento](/docs/buscar-jornada-de-pagamento)
- [Brick Bank](/docs/sobre-o-bricks)
- [Receptora de Dados](https://developers.finansystech.com.br/docs/receptora-de-dados-do-brick-bank)
- [Transmissora de Dados](https://developers.finansystech.com.br/docs/transmissora-de-dados-do-brick-bank)
- [Detentora de Contas](https://developers.finansystech.com.br/docs/detentora-de-contas)
- [Brick Insurance](/docs/brick-bank-copy)
- [Receptora de Dados (Open Insurance)](https://developers.finansystech.com.br/docs/receptora-de-dados-do-brick-insurance)
- [Transmissora de Dados (Open Insurance)](https://developers.finansystech.com.br/docs/transmissora-de-dados-do-brick-insurance)
- [Open Plus](/docs/open-plus)
- [Portal](/docs/portal)
- [Cadastro e acesso](/docs/cadastro-e-acesso)
- [Hall Open Plus](/docs/hall-open-plus)
- [Gestão de aplicações](/docs/gestão-de-aplicações)
- [Catálogo de produtos](/docs/catálogo-de-produtos)
- [Gestão de membros da equipe](/docs/gestão-de-membros-da-equipe)
- [Menu de usuário](/docs/menu-de-usuário)
- [Painel de gestão da aplicação](/docs/painel-de-gestão-da-aplicação)
- [Painel de gestão do produto](/docs/painel-de-gestão-do-produto)
- [Documentação de produto](/docs/documentação-de-produto)
- [Credenciais e usuário de teste](/docs/credenciais-e-usuário-de-teste)
- [Subir em produção](/docs/subir-em-produção)
- [Portal Configurações](/docs/portal-configurações)
- [Plataforma de Iniciação (ITP)](/docs/solução-de-pagamentos-itp)
- [Portal de configurações do Open Keys](/docs/portal-de-configurações-do-open-keys)
- [Dashboard](/docs/dashboard)
- [Lista de Transações](/docs/lista-de-transações)
- [Lista de Vínculos de Conta](/docs/lista-de-vínculos-conta)
- [Relatórios](/docs/relatórios-4)
- [Configurações da jornada de pagamentos](/docs/configurações-da-jornada-de-pagamentos)
- [Demo das Jornadas de Pagamento](/docs/demo-das-jornadas-de-pagamento)
- [Demo da Área de Gestão](/docs/demo-da-área-de-gestão)
- [Jornadas White Label](/docs/jornadas-white-label)
- [Iniciação de Pagamento Instantâneo](/docs/iniciação-de-pagamento-instantâneo)
- [Gestão de Pagamentos Instantâneos](/docs/gestão-de-pagamentos-instantâneos)
- [Iniciação de Pagamento Agendado](/docs/iniciação-de-pagamento-agendado)
- [Gestão de Pagamentos Agendados](/docs/gestão-de-pagamentos-agendados)
- [Iniciação de Pagamento sem Redirecionamento](/docs/iniciação-de-pagamento-sem-redirecionamento)
- [Gestão de Contas Salvas (Vínculos)](/docs/gestão-de-contas-salvas-vínculos)
- [Iniciação de Pagamento Automático](/docs/iniciação-de-pagamento-automático)
- [Gestão de Pagamentos Automáticos](/docs/gestão-de-pagamentos-automáticos)
- [FAQ Open Keys](/docs/faq-open-keys)
- [Jornada Pay by Link](/docs/perguntas-frequentes)
- [Pix por Aproximação](/docs/pix-por-aproximacao)
- [Documentação técnica](/docs/documentação-técnica)
- [Status e respostas: Máquina de estados](/docs/status-e-respostas-máquina-de-estados)
- [Status e respostas: Códigos de resposta HTTP](/docs/status-e-respostas-códigos-de-resposta-http)
- [Status e respostas: Possíveis erros de pagamentos](/docs/status-e-respostas-possíveis-erros-de-pagamentos)
- [Diagrama de sequência: Jornada com Redirecionamento](/docs/diagrama-de-sequência-jornada-com-redirecionamento)
- [Diagrama de sequência: Jornada sem Redirecionamento](/docs/diagrama-de-sequência-jornada-sem-redirecionamento)
- [Webhook](/docs/webhook-itp)
- [APIs](/docs/apis-itp)
- [Massa de Testes](/docs/massa-de-testes)
- [Validar SUCESSO no valor máximo dentro do permitido no vínculo do pix](/docs/jsr-lim-001)
- [Validar SUCESSO no valor máximo dentro do permitido no vínculo do pix e no limite diário](/docs/jsr-lim-001-1)
- [Validar FALHA no valor que excede o limite](/docs/jsr-lim-002)
- [Validar FALHA por saldo insuficiente](/docs/jsr-sal-003)
- [Validar qual erro prevalece quando ambas as condições, valor limite excedido e saldo insuficiente, falham](/docs/jsr-mix-004)
- [Validar FALHA por exceder o limite diário configurado pelo cliente](/docs/jsr-limd-005)
- [Validar FALHA por exceder o limite noturno](/docs/jsr-limn-006)
- [Validar FALHA quando o consentimento (autorização do cliente) está EXPIRADO](/docs/jsr-cons-007)
- [Validar FALHA quando o consentimento é REVOGADO pelo cliente na Instituição Detentora](/docs/jsr-cons-008)
- [Validar FALHA se o vínculo for REJEITADO por tempo limite de espera](/docs/jsr-fido-011)
- [Transferências inteligentes (Sweeping Accounts)](/docs/sweeping-accounts)
- [Criar consentimento](/docs/sweeping-accounts-criar-consentimento)
- [Callback do Consentimento](/docs/sweeping-accounts-callback-do-consentimento)
- [Cancelamento de consentimento](/docs/sweeping-accounts-cancelamento-de-consentimento)
- [Listar Consentimentos](/docs/sweeping-accounts-listar-consentimentos)
- [Buscar informações de um consentimento](/docs/sweeping-accounts-buscar-informações-de-um-consentimento)
- [Criação de uma sessão de jornada](/docs/sweeping-accounts-criação-de-uma-sessão-de-jornada)
- [Listar sessões de jornada](/docs/sweeping-accounts-listar-sessões-de-jornada)
- [Buscar informações de uma sessão de jornada](/docs/sweeping-accounts-buscar-informações-de-sessao-de-jornada)
- [Pix inteligente](/docs/pix-inteligente)
## Pix Indireto
- [Sobre o Pix Indireto](/docs/sobre-o-pix-indireto)
- [Introdução](/docs/pré-requisitos-do-participante)
- [Pré-requisitos do Participante](/docs/pré-requisitos-do-participante)
- [Fases do processo de adesão do Participante Indireto](/docs/fases-do-processo-de-adesão-do-participante-indireto)
- [DICT (Diretório de Identificadores de Contas Transacionais)](/docs/gestão-de-chaves-pix)
- [Gestão de Chaves Pix](/docs/gestão-de-chaves-pix)
- [Listar todas as chaves pix de um cliente](/docs/listar-chaves-pix-de-um-cliente)
- [Portabilidade e Reivindicação](/docs/portabilidade-e-reivindicação-1)
- [Infrações e MED](/docs/infrações)
- [Infrações](/docs/infrações)
- [Mecanismo Especial de Devoluções (MED)](/docs/mecanismo-especial-de-devoluções-med)
- [Marcação de fraude](/docs/marcação-de-fraude)
- [MED 2.0](/docs/med-20)
- [Criação recuperação de valores](/docs/criar-recuperação-de-valores)
- [Consulta recuperação de valores](/docs/consulta-recuperação-de-valores)
- [Cancela recuperação de valores](/docs/cancela-recuperação-de-valores)
- [Cria solicitação de devolução em recuperação de valores](/docs/cria-solicitação-de-devolução-em-recuperação-de-valores)
- [Consulta grafo de recuperação de valores](/docs/consulta-grafo-de-recuperação-de-valores)
- [Atualizar a recuperação de valores](/docs/atualizar-a-recuperação-de-valores)
- [Status da Recuperação de Valores](/docs/webhook-de-status-da-recuperação-de-valores)
- [Fechar uma Recuperação de valores](/docs/fechar-uma-recuperação-de-valores)
- [Fechar devolução em recuperação de valores](/docs/fechar-devolução-em-recuperação-de-valores)
- [Autorização do CashIn](/docs/autorização)
- [Autorização](/docs/autorização)
- [QR Code](/docs/acesso-às-apis-de-integração)
- [Receber com Pix (Pix Cash-in Indireto)](/docs/acesso-às-apis-de-integração)
- [Transferências](/docs/transferências-e-pagamentos-com-pix-pix-cash-out-para-indiretos)
- [Pagamentos (Pix cash-out para Indiretos)](/docs/transferências-e-pagamentos-com-pix-pix-cash-out-para-indiretos)
- [Recebimentos (Pix Cashin)](/docs/recebimentos-pix-cashin)
- [Devolução de recebimentos Pix](/docs/devolução-de-recebimentos-pix-copy)
- [Transações fora do SPI - Reporte Bacen](/docs/transações-fora-do-spi-reporte-bacen)
- [Pix Saque/Troco](/docs/pix-saquetroco)
- [Tabela de erros para participantes Indiretos do Pix](/docs/tabela-de-erros-pix-indireto)
- [Pix Automático](/docs/pix-automático-copy-1)
- [Jornada Pagadora](/docs/jornada-pagadora-copy)
- [Autorização - Visão Geral](/docs/autorização-visão-geral-copy)
- [Autorização - Jornada 1](/docs/autorização-jornada-1-copy-3)
- [Autorização - Jornada 2](/docs/autorização-jornada-2-copy-3)
- [Autorização - Jornada 3](/docs/autorização-jornada-3-copy-3)
- [Autorização - Jornada 4](/docs/autorização-jornada-4-copy-3)
- [Agendamento](/docs/agendamento-copy-1)
- [Liquidação](/docs/liquidação-copy-3)
- [Cancelamento do Consentimento](/docs/cancelamento-do-consentimento-copy-2)
- [Cancelamento de agendamento](/docs/cancelamento-de-agendamento-copy-3)
- [Consultas - Visão Pagador](/docs/consultas-visão-pagador-copy-1)
- [Jornada Recebedora](/docs/jornada-recebedora-copy)
- [Autorização - Jornada 1](/docs/autorização-jornada-1-copy-2)
- [Autorização - Jornada 2](/docs/autorização-jornada-2-copy-2)
- [Autorização - Jornada 3](/docs/autorização-jornada-3-copy-2)
- [Autorização - Jornada 4](/docs/autorização-jornada-4-copy-2)
- [Envio de Agendamento](/docs/envio-de-agendamento-copy-1)
- [Liquidação](/docs/liquidação-copy-2)
- [Retentativas de Recebimento](/docs/retentativas-de-recebimento-copy-1)
- [Cancelamento de Agendamento](/docs/cancelamento-de-agendamento-copy-2)
- [Cancelamento de Recorrência](/docs/cancelamento-de-recorrência-copy-1)
- [Webhooks](/docs/modelos-de-webhooks-do-pix-indireto)
- [Modelos de webhooks do Participante Indireto Pix](/docs/modelos-de-webhooks-do-pix-indireto)
## Pix - Avulso
- [Sobre o Pix](/docs/sobre-pix)
- [Receber com Pix (cash-in)](/docs/criar-cobrancas-com-pix-cashin)
- [Cobrança imediata com QR Code dinâmico (immediate)](/docs/cobranca-imediata-com-qrcode-dinamico)
- [Cobrança com vencimento com QR Code dinâmico (duedate)](/docs/qrcode-de-cobranca-com-vencimento)
- [Cobrança estática](/docs/cobranca-com-qrcode-estatico)
- [Consulta de recebimentos Pix](/docs/consultar-recebimentos-pix)
- [Devolução de recebimentos Pix](/docs/devolução-de-um-recebimento-pix)
- [Transferências e pagamentos com Pix (cash-out)](/docs/pagar-e-transferir-com-pix-cashout)
- [DICT](/docs/dict-1)
- [Balde de Fichas](/docs/balde-de-fichas)
- [Transferência Pix a partir de dados bancários](/docs/transferencia-pix-com-dados-bancarios)
- [Transferência Pix a partir de uma chave](/docs/transferencia-para-uma-chave-pix)
- [Pagamento de um QR Code Estático](/docs/pagamento-de-um-qrcode-estatico)
- [Pagamento de um QR Code Dinâmico](/docs/pagamento-de-um-qrcode-dinamico)
- [Pix entre contas (Pix Interno)](/docs/pagamento-de-um-qr-code-dinâmico-copy)
- [Consultar transferências, pagamentos e devoluções de Pix-Out](/docs/consultar-status-de-um-pagamento-pix)
- [Pagamento de um QR Code (estático ou dinâmico)](/docs/pagamento-de-um-qr-code-estatico-ou-dinamico)
- [Pix Automático](/docs/pix-automático-copy-copy)
- [Jornada Pagadora](/docs/jornada-pagadora-copy-copy)
- [Autorização - Visão Geral](/docs/autorização-visão-geral-copy-copy)
- [Autorização - Jornada 1](/docs/autorização-jornada-1-copy-5)
- [Autorização - Jornada 2](/docs/autorização-jornada-2-copy-5)
- [Autorização - Jornada 3](/docs/autorização-jornada-3-copy-5)
- [Autorização - Jornada 4](/docs/autorização-jornada-4-copy-5)
- [Agendamento](/docs/agendamento-copy-2)
- [Liquidação](/docs/liquidação-copy-5)
- [Cancelamento do Consentimento](/docs/cancelamento-do-consentimento-copy-3)
- [Cancelamento de agendamento](/docs/cancelamento-de-agendamento-copy-5)
- [Consultas - Visão Pagador](/docs/consultas-visão-pagador-copy-2)
- [Jornada Recebedora](/docs/jornada-recebedora-copy-copy)
- [Autorização - Jornada 1](/docs/autorização-jornada-1-copy-4)
- [Autorização - Jornada 2](/docs/autorização-jornada-2-copy-4)
- [Autorização - Jornada 3](/docs/autorização-jornada-3-copy-4)
- [Autorização - Jornada 4](/docs/autorização-jornada-4-copy-4)
- [Envio de Agendamento](/docs/envio-de-agendamento-copy-2)
- [Liquidação](/docs/liquidação-copy-4)
- [Retentativas de Recebimento](/docs/retentativas-de-recebimento-copy-2)
- [Cancelamento de Agendamento](/docs/cancelamento-de-agendamento-copy-4)
- [Cancelamento de Recorrência](/docs/cancelamento-de-recorrência-copy-2)
- [Tabela de erros Pix](/docs/tabela-de-erros-pix)
- [FAQs](https://suporte.celcoin.com.br/hc/pt-br/sections/11326535846427-Pix)
- [Webhook](/docs/modelos-de-webhooks-do-pix)
- [Modelos de webhooks do Pix](/docs/modelos-de-webhooks-do-pix)
## Conciliação
- [API para Conciliação](/docs/sobre-api-de-conciliação)
- [Sobre API de Conciliação](/docs/sobre-api-de-conciliação)
- [API para Extrato Consolidado](/docs/sobre-api-de-extrato-consolidado)
- [Sobre API de Extrato Consolidado](/docs/sobre-api-de-extrato-consolidado)
- [Tabela de Erros](/docs/tabela-de-erros-conciliacao)
## Suporte
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [SLA de atendimento](/docs/sla-de-atendimento)
## PAINEL DO CLIENTE
- [Listagem de Tickets](/docs/listagem-de-tickets)
Powered by [](https://readme.com?ref_src=hub&project=celcoin)
1. Introdução
# Uma breve introdução
**Seja bem-vindo(a)!**
Aqui você encontrará tudo que precisa para ter sua melhor integração possível com as nossas APIs. Venha conosco e conduza seu negócio ao próximo nível! 🚀
> 👍
>
> ###
>
> Procurando por alguma informação específica?
>
> [](#procurando-por-alguma-informação-específica)
>
> Temos uma função de pesquisa muito prática. Basta pressionar Command+K (MacOS) ou Ctrl+K (Windows) e digitar o que você está procurando!
##
O que é a Celcoin?
[](#o-que-é-a-celcoin)
A Celcoin, fundada em 2016, é uma infratech financeira para potencializar negócios.
Através do cel\_bricks, sua solução Embedded Finance, ela fornece infraestrutura de tecnologia completa para empresas reguladas e não reguladas, dos mais diversos segmentos de atuação, e disponibiliza soluções modulares para banking, crédito, Open Finance, cash management, retail, onboarding e emissão de cartão.
Pioneira no mercado, a Celcoin é também a vanguarda de mais uma transformação no segmento com o mybenk: solução de banking completa para todos os stakeholders de um ecossistema. Um bank com e de Endofinance!
Estão conectadas à plataforma da Celcoin cerca de 600 bancos digitais, unicórnios e fintechs, mais de 6 mil médias e grandes empresas e 40 mil pontos de varejo, que, juntos, processam mensalmente mais de R$ 40 bilhões.
Seu reconhecimento também está em conquistas como prêmios de “Melhor Startup do Brasil” pela Seedstars, “Melhor Fintech do País” pelo BBVA Open Talent, “The Inclusive Fintech 50”, “100 Startups to Watch” pela Pequenas Empresas & Grandes Negócios, aporte financeiro da Summit Partners com participação da Innova Capital, assim como certificados “Great Place to Work (GPTW)” e “Empresa B”. Foi ainda uma das grandes vencedoras do “Prêmio Banking Transformation”, organizado pela Cantarino Brasileiro, na categoria Open Banking.
Para fortalecer sua equipe e seu escopo de atuação, também realizou as aquisições das empresas Galax Pay, focada em soluções de cobrança recorrente, Flow Finance, que fornece infraestrutura de crédito, Finansystech, startup líder em soluções de Open Finance, e Regulatório+, de soluções regulatórias.
Seja qual for o seu segmento de atuação, é simples oferecer serviços financeiros e bancários aos seus clientes. Isso é Celcoin. The best service for growth.
##
Plataforma multicanal
[](#plataforma-multicanal)
Nossos clientes utilizam nossas soluções para ofertarem diversos serviços envolvendo transações financeiras, acessarem dados via Open Banking e se conectarem a uma rede com milhares de pontos físicos. Assim, construímos uma conexão única entre a Celcoin, nossos clientes e milhões de clientes finais espalhados por todo o Brasil, que usufruem de experiências inovadoras.
##
Reconhecimento do mercado
[](#reconhecimento-do-mercado)
Nossas propostas e atuações são reconhecidas com alguns dos prêmios mais expressivos no cenário corporativo, conquistando também o apoio de grandes empresas em nossa jornada pela democratização dos serviços financeiros.
Updated about 1 month ago
---
What’s Next
- [Obtenha suas credenciais de acesso](/docs/obtendo-acesso-às-apis)
Ask AI
© 2026 Celcoin - Todos os direitos reservados
Celcoin.com.br
SOLUÇÕES
Auto
[
Débito Veicular
](https://www.celcoin.com.br/solucoes/auto/debito-veicular/)
Cobrança
[
Cobrança com Pix
](https://www.celcoin.com.br/solucoes/cobranca/cobranca-com-pix/)[
Cobrança Recorrente
](https://www.celcoin.com.br/solucoes/cobranca/cobranca-recorrente/)
[Crédito](https://www.celcoin.com.br/solucoes/credit-platform/)
Pagamento de contas
[
Boletos e concessionárias
](https://www.celcoin.com.br/solucoes/pagamento-de-contas/boletos-e-concessionarias/)
Saques e Depósitos
[
Pix Saque e Pix Troco
](https://www.celcoin.com.br/solucoes/saques-e-depositos/pix-saque-e-pix-troco/)[
Rede Banco24Horas
](https://www.celcoin.com.br/solucoes/saques-e-depositos/rede-banco24horas/)
[Banking as a Service](https://www.celcoin.com.br/solucoes/banking-as-a-service/)
[Corban as a Service](https://www.celcoin.com.br/solucoes/corban-as-a-service/)
Open Banking
[
Compartilhamento de Dados
](https://www.celcoin.com.br/solucoes/open-banking/compartilhamento-de-dados/)[
Iniciação de pagamentos
](https://www.celcoin.com.br/solucoes/open-banking/iniciacao-de-pagamentos/)
Recargas
[
Gift Cards
](https://www.celcoin.com.br/solucoes/recargas/gift-cards/)[
Recarga de celular
](https://www.celcoin.com.br/solucoes/recargas/recarga-de-celular/)[
Recarga de streaming e TV pré-pago
](https://www.celcoin.com.br/solucoes/recargas/streaming-e-tv-pre-pago/)[
Recarga para 150 países
](https://www.celcoin.com.br/solucoes/recargas/recarga-para-150-paises/)
Transferências
[
Pix Cash-out
](https://www.celcoin.com.br/solucoes/transferencias/pix-cash-out/)
EMPRESA
[Sobre Nós](https://www.celcoin.com.br/sobre-a-celcoin/) [News](https://news.celcoin.com.br/) [Trabalhe Conosco](https://jobs.kenoby.com/celcoin) [Demonstrações Financeiras](https://www.celcoin.com.br/demonstracoes-financeiras/)
DEVELOPER
[Por onde começar](https://developers.celcoin.com.br/docs) [Referências](https://developers.celcoin.com.br/reference/integrando-na-celcoin) [Suporte](https://suporte.celcoin.com.br/hc/pt-br/requests/new?ticket_form_id=4553742630939) [Status da API](https://developers.celcoin.com.br/page/status-page)
RECURSOS
[Suporte](https://suporte.celcoin.com.br/hc/pt-br/requests/new?ticket_form_id=4553742630939) [Contato](https://www.celcoin.com.br/contato-celcoin/) [Ouvidoria](https://www.celcoin.com.br/ouvidoria/)
POLÍTICAS & COMPLIANCE
[
Política de Gerenciamento de Riscos
](https://www.celcoin.com.br/politica-de-gerenciamento-de-riscos-operacionais-e-liquidez/)[
Política de Prevenção à Lavagem
](https://www.celcoin.com.br/politica-de-prevencao-a-lavagem-de-dinheiro-e-ao-financiamento-do-terrorismo-pld-ft/)[
Política de Segurança da Informação
](https://www.celcoin.com.br/politica-de-seguranca-da-informacao-e-seguranca-cibernetica/)[
Canal de Denúncia
](https://www.contatoseguro.com.br/)
[CASO DE USO](https://www.celcoin.com.br/casos-de-uso/)
Celcoin Instituição de Pagamento S.A – 13.935.893/0001-09
Al. Xingu, 350 – Conj 1604 – Alphaville Industrial Barueri – SP – 06455-030
[
Configurações de cookies
](https://www.celcoin.com.br/politica-de-cookies/)[
Privacidade e termos
](https://www.celcoin.com.br/privacidade-e-termos/)[](https://www.linkedin.com/company/celcoin-financial-hub/)
Tool: webfetch
Input:
{
"url": "https://www.celcoin.com.br/cel_payments/pix/",
"format": "markdown",
"timeout": 60
}
Output:
cel\_payments – Pix | Celcoin
[](https://www.celcoin.com.br)
- Soluções
Close Soluções Open Soluções
cel\_bricks Plataformas mybenk Open Finance
[cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
Saiba mais como o Embedded Finance da Celcoin pode apoiar o seu negócio.
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [BaaS](https://www.celcoin.com.br/cel_banking/banking-as-a-service/)
- [Banco Liquidante](https://www.celcoin.com.br/cel_banking/banco-liquidante/)
- [Cartão White Label](https://www.celcoin.com.br/cel_banking/cartao-white-label/)
- [Compartilhamento de Dados](https://www.celcoin.com.br/cel_banking/compartilhamento-de-dados/)
- [Core Banking](https://www.celcoin.com.br/cel_banking/core-banking/)
- [Open Insurance](https://www.celcoin.com.br/cel_banking/open-finance-insurance/)
- [Regulatório](https://www.celcoin.com.br/cel_banking/regulatorio/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [Débito Veicular](https://www.celcoin.com.br/cel_payments/debito-veicular/)
- [Débito Veicular White Label](https://www.celcoin.com.br/cel_payments/debito-veicular-white-label/)
- [Gateway de Pagamento](https://www.celcoin.com.br/cel_payments/gateway-de-pagamento/)
- [ITP](https://www.celcoin.com.br/cel_payments/open-finance-itp/)
- [Pagamento de contas](https://www.celcoin.com.br/cel_payments/pagamento-de-contas/)
- [Pix](https://www.celcoin.com.br/cel_payments/pix/)
- [Recargas](https://www.celcoin.com.br/cel_payments/recargas/)
- [Saque e Depósito](https://www.celcoin.com.br/cel_payments/saque-e-deposito/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [CCB](https://www.celcoin.com.br/cel_credit/ccb/)
- [Consignado as a Service](https://www.celcoin.com.br/cel_credit/consignado-as-a-service/)
- [Conta Escrow](https://www.celcoin.com.br/cel_credit/conta-escrow/)
- [Core Credit](https://www.celcoin.com.br/cel_credit/core-credit/)
- [Gestão de Carteira e Cobrança](https://www.celcoin.com.br/cel_credit/gestao-de-carteira-e-cobranca/)
- [Nota Comercial](https://www.celcoin.com.br/cel_credit/nota-comercial/)
[Plataforma de Antecipações](https://www.celcoin.com.br/plataforma-de-antecipacoes/)
Uma plataforma moderna para antecipação de recebíveis com toda a infraestrutura regulatória, tecnológica e operacional da Celcoin.
[Ver solução](https://www.celcoin.com.br/plataforma-de-antecipacoes/)
[mybenk](https://www.celcoin.com.br/mybenk/)
Saiba mais como o mybenk pode apoiar a transformar o universo financeiro interno. Uma solução completa para todos seus stakeholders.
[Ver solução](https://www.celcoin.com.br/mybenk/)
[Open Finance](https://www.celcoin.com.br/open-finance/)
Todas as oportunidades do Open Finance para o seu negócio.
- [ITP](https://www.celcoin.com.br/cel_payments/open-finance-itp/)
- [Pix Automático](https://www.celcoin.com.br/open-finance/pix-automatico/)
- [Pix Inteligente](https://www.celcoin.com.br/open-finance/pix-inteligente/)
- [Pix por Aproximação](https://www.celcoin.com.br/open-finance/pix-por-aproximacao/)
- [Pix Biometria](https://www.celcoin.com.br/open-finance/pix-biometria/)
- [Pix Recorrente](https://www.celcoin.com.br/open-finance/pix-recorrente/)
- [Financial Data](https://www.celcoin.com.br/open-finance/financial-data/)
- [Cadastro Expresso](https://www.celcoin.com.br/open-finance/cadastro-expresso/)
- [Detentora de Conta](https://www.celcoin.com.br/open-finance/detentora-de-conta/)
- Desenvolvedores
Close Desenvolvedores Open Desenvolvedores
Comece a integrar as soluções da Celcoin
[Explorar soluções](https://www.celcoin.com.br/developers/)
Developer
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
- Empresa
Close Empresa Open Empresa
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
[](https://www.celcoin.com.br/partners/)
- Conteúdos
Close Conteúdos Open Conteúdos
CONTEÚDOS
- [Eventos](https://www.celcoin.com.br/eventos/)
- [Insights](https://www.celcoin.com.br/insights/)
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Últimas novidades
[ETFs: como funcionam e o que avaliar antes de investir](https://www.celcoin.com.br/news/investimento-em-etf/)
20 de March de 2026
[Celcoin conquista certificação PCI DSS e reforça segurança como diferencial competitivo no mercado financeiro](https://www.celcoin.com.br/news/celcoin-recebe-certificacao-de-seguranca-pci-dss/)
19 de March de 2026
[Mais de 60% dos consumidores abandonam suas compras após uma experiência negativa](https://www.celcoin.com.br/news/novo-comportamento-do-consumidor-no-varejo/)
19 de March de 2026
[Entrar](#Login)
Qual o seu painel na **Celcoin?**
Cada painel tem sua credencial distinta.
Não tem acesso? **Fale com um especialista**
- cel\_bricks
Acesse o Painel do Cliente para obter relatórios e simplificar a gestão financeira da sua empresa.
- cel\_credit (escrow)
Gerencie sua conta escrow com eficiência e praticidade.
- Gateway de Pagamentos
Gerencie suas finanças com eficiência e praticidade.
Ainda não possui uma conta? **Cadastre-se**
Qual o seu painel na **Celcoin?**
Cada painel tem sua credencial distinta.
- cel\_bricks
- cel\_credit (escrow)
- Gateway de Pagamento
Não tem acesso?
- Criar conta Celcoin (contratar)
- Criar conta Gateway de Pagamento
[Contratar](https://www.celcoin.com.br/contato-celcoin/)
- [Celcoin](https://www.celcoin.com.br/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- Pix
# Ofereça transferências e pagamentos instantâneos com o Pix
Conte com a expertise da infratech que processa mais de 250 milhões de transações de Pix por mês. A Celcoin possui a tecnologia mais robusta e escalável do mercado, com nota A na ANS (Acordo de Níveis de Serviço) do BC.
[Fale com um especialista](javascript:void\(0\))
Potencialize seu negócio com as soluções da Celcoin
[Ver documentação](https://www.celcoin.com.br/developers/)
[](https://www.celcoin.com.br)
- Produtos
Close Produtos Open Produtos
cel\_payments
Soluções para todas as etapas da jornada do seu cliente.
- [Débito veicular](https://www.celcoin.com.br/cel_payments/debito-veicular/)
- [Débito veicular white label](https://www.celcoin.com.br/cel_payments/debito-veicular-white-label/)
- [Gateway de pagamento](https://www.celcoin.com.br/cel_payments/gateway-de-pagamento/)
- [ITP](https://www.celcoin.com.br/cel_payments/open-finance-itp/)
- [Pagamento de contas](https://www.celcoin.com.br/cel_payments/pagamento-de-contas/)
- [Pix](https://www.celcoin.com.br/cel_payments/pix/)
- [Recargas](https://www.celcoin.com.br/cel_payments/recargas/)
- [Saque e Depósito](https://www.celcoin.com.br/cel_payments/saque-e-deposito/)
[Fale com um especialista](javascript:void\(0\))
Potencialize seu negócio com as soluções da Celcoin
Mais autonomia para sua empresa
## Pix com autonomia e tecnologia avançada para sua empresa
Com a Celcoin, você tem acesso à melhor tecnologia de pagamentos instantâneos, aliada à segurança e escalabilidade necessárias para garantir eficiência e conformidade em todas as transações.
### Alta escalabilidade
Nossa infraestrutura garante que você possa processar um grande volume de transações com rapidez e segurança.
### Flexibilidade operacional
Seja com a Embedded Solution de Pix ou através da licença de Pix Indireto, você tem total autonomia para gerenciar as operações de pagamentos e recebimentos, além de toda a gestão de chaves Pix.
### Suporte completo
Desde a integração até o suporte contínuo, estamos prontos para auxiliar sua empresa em todas as etapas do processo.
### Compliance garantido
A Celcoin cuida de toda a conformidade regulatória com o Banco Central, permitindo que sua empresa se concentre no crescimento.
Pix
## O Pix ainda mais conectado à nossa infratech
A Celcoin oferece duas modalidade para sua empresa operar no arranjo Pix,
dependendo de suas necessidades e estrutura.
Finalidade Funcionalidades Benefícios
Empresas que estão começando no arranjo Pix
Disponibilizamos uma conta semelhante à Conta PI, com controle completo de saldos, extratos e limites transacionais, facilitando a gestão da tesouraria de sua empresa.
Empresas com licença do Banco Central
Se sua empresa já possui a licença do Banco Central, fazer a migração para o Pix Indireto da Celcoin oferecerá uma integração simplificada para que você opere com total autonomia, utilizando nossa infraestrutura robusta e segura, que transaciona mais de 250 milhões de Pix todos os meses.
Operação facilitada de tesouraria
Disponibilizamos uma conta semelhante à Conta PI, com controle completo de saldos, extratos e limites transacionais, facilitando a gestão da tesouraria de sua empresa.
Única integração para todo o ciclo de vida
Com apenas uma integração, sua empresa pode iniciar como participante indireto e, futuramente, evoluir para participante direto, sem precisar trocar de infraestrutura.
Acesso completo ao Pix e cabine de gestão
Oferecemos uma cabine de gestão completa, onde sua empresa pode monitorar o fluxo financeiro, gerenciar infrações e devoluções, e visualizar dados estatísticos em tempo real.
Privacidade das chaves DICT
Sua empresa terá controle total sobre a privacidade das chaves Pix, com proteção garantida e sem vínculo com o participante direto.
Alto desempenho e segurança
Com nossa infraestrutura de alto desempenho, sua empresa opera com segurança e escalabilidade, protegendo os dados a nível bancário.
- **Gestão completa de chaves Pix:** Controle total sobre a criação, cancelamento e portabilidade das chaves Pix.
- **Conformidade garantida:** A Celcoin oferece suporte integral ao processo de homologação com o Banco Central.
- **Modularidade:** Escolha entre utilizar a arquitetura de contas da sua empresa ou se integrar ao core bancário da Celcoin.
- **Transparência nas operações:** O nome da sua empresa, como participante indireto, será exibido no comprovante, aumentando a transparência e confiabilidade com seus clientes.
- **Autonomia operacional:** Sua empresa terá controle total sobre suas operações financeiras, integrando-se diretamente ao SPI do Banco Central.
- **Suporte 24/7:** Atendimento dedicado para auxiliar sua empresa em todas as etapas, desde o onboarding até a operação contínua, 24 horas por dia, 7 dias por semana.
### Pix Indireto
Tenha acesso a uma solução robusta e escalável, que **permite à sua empresa operar de forma independente como Participante Indireto no arranjo Pix**, sem a necessidade de se conectar diretamente ao Banco Central.
Com isso, você terá maior controle sobre suas operações financeiras, garantindo flexibilidade e eficiência nas transações.
### Pix
O Pix é ideal para empresas que buscam uma forma rápida e fácil de oferecer Pix em suas plataformas, **sem se preocupar com a complexidade regulatória ou operacional**.
Disponibilizamos toda a infraestrutura pronta e simplificada para transações instantâneas.
Funcionalidades Benefícios
Pix Cash-in
Realize cobranças e receba de forma instantânea
- **QR Code dinâmico:** Para cobranças imediatas e cobranças com data de vencimento.
- **QR Code estático:** Para valores que não expiram.
Pix Cash-out
Conte com as melhores alternativas para pagamentos e transferências.
- **Pagamentos via QR Code ou Pix Copia e Cola:** Retorno de todos os dados do QR Code, como identificador, descrição e valor.
- **Transferências com Chave Pix ou dados bancários:** Consulta ao DICT, validação dos dados bancários e, assim, retorno das informações para a transferência ser executada.
- **Devolução Pix:** Permissão para que o valor de uma transação ou pagamento seja devolvido.
- **Rapidez e disponibilidade:** 99% das transações são concluídas em menos de 10 segundos, funcionando 24/7.
- **Segurança:** Total conformidade com as regulamentações do Banco Central, garantindo a segurança das transações.
- **Baixa fricção:** Integração rápida e fácil com um único endpoint, simplificando a operação do Pix em sua plataforma.
- **Praticidade:** A Celcoin cuida de toda a parte regulatória e conformidade com o Banco Central, sem necessidade de sua empresa lidar diretamente com essas obrigações.
- **Contas individualizadas:** Vinculação de chaves Pix com contas exclusivas para cada cliente.
- **Grande volume de transações:** Suporte a um número elevado de transações, com segurança e agilidade.
- **Facilidade de integração:** API fácil de usar, com documentação completa e suporte dedicado.
## Pix Automático
O Pix Automático é a solução ideal para automação de recebimentos de pagamentos recorrentes. Com a autorização do seu cliente, os débitos são feitos automaticamente via Pix.
[Ver caso de uso](https://www.celcoin.com.br/insights/conheca-o-pix-automatico-da-celcoin/)
Developer Hub
## Tudo o que você precisa para integrar com a nossa solução
Nossa solução foi desenvolvida com foco em facilitar a integração para desenvolvedores, garantindo acesso a toda a infraestrutura da Celcoin.
- Guias rápidos de aplicação
- Exemplos e amostras de código
- Webhooks em tempo real
- Documentações completas
- Suporte especializado para auxiliar em todas as etapas
[Acesse nossa documentação](https://www.celcoin.com.br/developers/)
## Potencialize seu negócio com o Pix da Celcoin
Ofereça uma solução completa de pagamentos instantâneos para sua empresa.
[Fale com um especialista](javascript:void\(0\))
Potencialize seu negócio com as soluções da Celcoin
- [](https://www.linkedin.com/company/celcoin-financial-hub/)
- [](https://www.instagram.com/celcoin_/)
- [](https://x.com/celcoinbr)
- [](https://www.youtube.com/channel/UCOz8tQnZl3cV4cI0beQ5pYw)
Soluções
- [cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [mybenk](https://www.celcoin.com.br/mybenk/)
[Indústrias](https://www.celcoin.com.br/industrias/)
- [E-commerce e Marketplace](https://www.celcoin.com.br/industrias/marketplace/)
- [Mercado de Capitais](https://www.celcoin.com.br/industrias/mercado-de-capitais/)
- [Varejo](https://www.celcoin.com.br/industrias/varejo/)
- ERP
- Insurance
- Instituições financeiras
- Utilities
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
Recurso
- [Canal de Denúncias](https://www.celcoin.com.br/canal-de-denuncias/)
- [Compliance e Regulatório](https://www.celcoin.com.br/compliance-e-regulatorio/)
- [Ouvidoria](https://www.celcoin.com.br/ouvidoria/)
- [Seja um parceiro](https://www.celcoin.com.br/partners/)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
Conteúdos
- [Eventos](https://www.celcoin.com.br/eventos/)
- [Insights](https://www.celcoin.com.br/insights/)
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Developers
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
Atendimento Celcoin
De segunda a sexta-feira: das 09h às 18h
Telefone
[(11) 5070-8153](tel:1150708153)
Whatsapp
[(11) 4765-5043](https://wa.me/551147655043)
Suporte
Suporte especializado para ajudar você a extrair o máximo das soluções Celcoin
[Enviar uma solicitação](https://suporte.celcoin.com.br/hc/pt-br/requests/new)
Ouvidoria
De segunda a sexta-feira: das 09h às 17h
Telefone
[0800 591 1852](tel:08005911852)
Soluções
- [cel\_bricks](https://www.celcoin.com.br/cel_bricks/)
- [cel\_banking](https://www.celcoin.com.br/cel_banking/)
- [cel\_credit](https://www.celcoin.com.br/cel_credit/)
- [cel\_payments](https://www.celcoin.com.br/cel_payments/)
- [mybenk](https://www.celcoin.com.br/mybenk/)
Indústrias
- [E-commerce e marketplace](https://www.celcoin.com.br/industrias/marketplace/)
- [Mercado de capitais](https://www.celcoin.com.br/industrias/mercado-de-capitais/)
- [Varejo](https://www.celcoin.com.br/industrias/varejo/)
- ERP
- Insurance
- Instituições financeiras
- Utilities
Empresa
- [Central de ajuda](https://suporte.celcoin.com.br/hc/pt-br)
- [Contato](https://www.celcoin.com.br/contato-celcoin/?formulario_extendido_celcoin=sim)
Recurso
- [Canal de Denúncias](https://www.contatoseguro.com.br/)
- [Compliance e Regulatório](https://www.celcoin.com.br/compliance-e-regulatorio/)
- [Ouvidoria](https://www.celcoin.com.br/ouvidoria/)
- [Seja um parceiro](https://www.celcoin.com.br/partners/)
- [Sobre nós](https://www.celcoin.com.br/sobre-a-celcoin/)
- [Trabalhe conosco](https://www.inhire.com.br/carreiras/celcoin/)
Conteúdos
- [News](https://www.celcoin.com.br/news/)
- [Podcast](https://www.celcoin.com.br/podcast-celcoin/)
Developer
- [APIs](https://developers.celcoin.com.br/reference)
- [Documentação](https://developers.celcoin.com.br/docs)
- [Developers](https://www.celcoin.com.br/developers/)
- [Status da API](https://developers.celcoin.com.br/page/status-page)
### Atendimento Celcoin
De segunda a sexta-feira: das 09h às 18h
## Telefone
[0800 591 1457](tel:5070-8153)
## Whatsapp
[(11) 4765-5043](https://wa.me/551147655043)
[Enviar uma solicitação](https://suporte.celcoin.com.br/hc/pt-br/requests/new)
### Ouvidoria
De segunda a sexta-feira: das 09h às 17h
## Telefone
[0800 591 1852](tel:08005911852)
Celcoin Instituição de Pagamento S.A - 13.935.893/0001-09
Al. Xingu, 350 – Conj 1604 – Alphaville Industrial Barueri – SP – 06455-030
[
Configuração de cookies
](https://www.celcoin.com.br/compliance-e-regulatorio/)[
Privacidade e termos
](https://www.celcoin.com.br/compliance-e-regulatorio/)
Tool: webfetch
Input:
{
"url": "https://dock.tech/en/solution/banking/",
"format": "markdown",
"timeout": 60
}
Output:
Banking - Dock
[Dock](https://dock.tech/en/)
[Dock](#!) [Solutions](#!) [Developers](https://developers.dock.tech/) [Content](https://dock.tech/en/fluid/) [Contact](#!)
[](# "click to search")
**Dock**
Over 25 years dedicated to democratizing access to financial services.
[About](https://dock.tech/en/about/)
We’re reshaping the financial landscape to empower society.
[Career in Dock](https://dock.tech/en/career/)
Maximize your potential without borders; create innovative solutions for leading brands.
[Press room](https://dock.tech/en/press-room/)
Communicating our true impact and commitment to financial inclusion. Access news and official resources.
**Solutions**
Leverage Brazil's largest portfolio of financial solutions to expand and strengthen your business.
[Banking](https://dock.tech/en/solution/banking)
Create your own digital bank and offer payment solutions like Pix.
[Cards & Credit](https://dock.tech/en/solution/cards-credit)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Acquiring](https://dock.tech/en/solution/acquiring)
End-to-end white-label acquiring solutions to transform your business.
[Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
Authentication, detection, and risk prevention throughout your customer journey.
[Dock One](https://dock.tech/en/dock-one/)
A comprehensive platform to scale your operations with global reach.
[LATAM Solutions](https://dock.tech/en/solutions-dock-latam/)
Drive innovation and grow your business.
[Solutions Brazil](#!)
Discover the most complete portfolio of financial services.
[Dock One platform](https://dock.tech/en/dock-one/)
A complete platform to scale your operations with global reach.
[Banking](https://dock.tech/en/solution/banking)
Create your own digital bank and offer payment solutions like Pix.
[Cards & Credit](https://dock.tech/en/solution/cards-credit)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Acquiring](https://dock.tech/en/solution/acquiring)
End-to-end white-label acquiring solutions to transform your business.
[Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
Authentication, detection, and risk prevention throughout your customer journey.
[Dock One](https://dock.tech/en/dock-one/)
A comprehensive platform to scale your operations with global reach.
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/multi-benefit-card/) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado) [Tokenization](https://dock.tech/en/tokenization/)
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
[LATAM Solutions](https://dock.tech/en/solutions-dock-latam/) [Dock Colombia](https://dock.tech/en/countries/colombia/) [Dock Mexico](https://dock.tech/en/countries/mexico/)
[Banking](https://dock.tech/en/solution/banking) [Cards & Credit](https://dock.tech/en/solution/cards-credit) [Acquiring](https://dock.tech/en/solution/acquiring) [Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/multi-benefit-card/) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado) [Tokenization](https://dock.tech/en/tokenization/)
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[Dock One platform](https://dock.tech/en/dock-one) [Data Platform](https://dock.tech/en/data-platform)
**Contact**
We are prepared to serve you in the best possible way.
[Speak to the salesperson](https://dock.tech/en/#contato)
To get in touch with our sales team, click here and complete the form.
[Customer service](https://dock.tech/en/sac/)
For frequently asked questions and customer service, click here.
[Media Inquiries](https://dock.tech/en/press-room/#contato-imprensa)
Please reach out to our communications team.
[Dock](https://dock.tech/en/)
[
](#!)
[Dock](#!) [Solutions](#!) [Developers](https://developers.dock.tech/) [Content](https://dock.tech/en/fluid/) [Contact](#!)
[Dock](#!)
Over 25 years dedicated to democratizing access to financial services.
[About](https://dock.tech/en/about/)
We’re reshaping the financial landscape to empower society.
[Career in Dock](https://dock.tech/en/career/)
Maximize your potential without borders; create innovative solutions for leading brands.
[Press room](https://dock.tech/en/press-room/)
Communicating our true impact and commitment to financial inclusion. Access news and official resources.
[Solutions](#!)
Leverage Brazil's largest portfolio of financial solutions to expand and strengthen your business.
[Banking](#!) [Cards & Credit](#!) [Acquiring](#!) [Fraud Prevention](#!) [Discover our platform](#!) [LATAM Solutions](#!) [Solutions Brazil](#!) [Dock One platform](#!) [Banking](#!) [Cards & Credit](#!) [Acquiring](#!) [Fraud Prevention](#!) [Discover our platform](#!)
[LATAM Solutions](#!)
Drive innovation and grow your business.
[LATAM Solutions](https://dock.tech/en/es/solutions-dock-latam/)
[Solutions Brazil](#!)
Discover the most complete portfolio of financial services.
[Banking](https://dock.tech/en/solution/banking) [Cards & Credit](https://dock.tech/en/solution/cards-credit) [Acquiring](https://dock.tech/en/solution/acquiring) [Fraud Prevention](https://dock.tech/en/solution/fraud-prevention)
[Banking](#!)
Create your own digital bank and offer payment solutions like Pix.
[Digital account](https://dock.tech/en/solution/banking/#conta-digital) [Pix](https://dock.tech/en/solution/banking/#pix) [Bank slips](https://dock.tech/en/solution/banking/#boletos) [Voucher and top-up marketplace](https://dock.tech/en/solution/banking/#marketplace)
[Cards & Credit](#!)
Offer cards with your brand: credit, debit, global, rewards, and more.
[Card Processing](https://dock.tech/en/solution/cards-credit/#processamento) [Brand License](https://dock.tech/en/solution/cards-credit/#bandeiras) [Credit Card](https://dock.tech/en/solution/cards-credit/#cartao-de-credito) [Private-Label Card](https://dock.tech/en/solution/cards-credit/#cartao-private-label) [Multibenefits Card](https://dock.tech/en/solution/cards-credit/#cartao-multibeneficio) [Global Card](https://dock.tech/en/solution/cards-credit/#cartao-global) [Prepaid and Debit Card](https://dock.tech/en/solution/cards-credit/#cartao-pre-debito) [Payroll-Deductible Card](https://dock.tech/en/solution/cards-credit/#cartao-consignado)
[Acquiring](#!)
End-to-end white-label acquiring solutions to transform your business.
[Acquiring as a service](https://dock.tech/en/solution/acquiring)
[Fraud Prevention](#!)
Authentication, detection, and risk prevention throughout your customer journey.
[Biometric Authentication](https://dock.tech/en/solution/fraud-prevention/#biometria) [Background Check](https://dock.tech/en/solution/fraud-prevention/#background-check) [Transactional Anti-Fraud](https://dock.tech/en/solution/fraud-prevention/#antifraude-transacional) [Multichannel Communication](https://dock.tech/en/solution/fraud-prevention/#comunicacao-multicanal)
[our platform](#!)
A comprehensive platform to scale your operations with global reach.
DOCK ONE **Our layered solutions**
Robust high-tech platform, totalmente personalized and modular thanks to our APIs, in addition to taking care of all the bureaucracy, IT, products, regulatory, licensing and prevention of fraude.
[LEARN MORE](https://dock.tech/en/dock-one)
[Contact](#!)
We are prepared to serve you in the best possible way.
[Talk to Commercial](https://dock.tech/en/#contato)
To get in touch with our sales team, click here and complete the form.
[Customer Service](https://dock.tech/en/sac/)
For frequently asked questions and customer service, click here.
[Media Inquiries](https://dock.tech/en/press-room/#contato-imprensa)
Please reach out to our communications team.
# **Solutions Brazil** Create your own digital bank with your brand: no bureaucracy
Boost your core business and unlock the potential of your enterprise by implementing financial services with our banking platform.
[LEARN MORE](#contato "click to access")
## Everything you need in one place
Discover our white-label digital banking platform!
**Digital account**
Offer features like a traditional bank, including a complete digital account, cards, and much more, all personalized with your brand.
[LEARN MORE](#conta-digital)
**Pix**
Leverage the scalability and security of Pix to offer your customers instant and versatile payment methods.
[LEARN MORE](#pix)
**Bank slips**
Provide convenience and security with a widely accepted and easy-to-use payment method, without needing a bank account.
[LEARN MORE](#boletos)
**Voucher Marketplace**
Attract and retain customers with exclusive offers, creating strategic partnerships and expanding your brand's visibility.
[LEARN MORE](#marketplace)
**Digital account**
Offer features like a traditional bank, including a complete digital account, cards, and much more, all personalized with your brand.
[LEARN MORE](#conta-digital)
**Pix**
Leverage the scalability and security of Pix to offer your customers instant and versatile payment methods.
[LEARN MORE](#pix)
**Bank slips**
Provide convenience and security with a widely accepted and easy-to-use payment method, without needing a bank account.
[LEARN MORE](#boletos)
**Voucher Marketplace**
Attract and retain customers with exclusive offers, creating strategic partnerships and expanding your brand's visibility.
[LEARN MORE](#marketplace)
## Digital account
Build your own bank with the white-label Digital Account solution and enjoy the expertise of those who have more than 75 million active accounts.
**White-label digital account**
Offer to your customers a complete experience of a 100% digital account with your brand.
- 
Have your own digital account app.
- 
Convenience in bank transfers via Pix, bill payments and slip payments.
- 
Track movements such as revenue, costs and expenses in one place.
**Debit card with your brand**
Transform your brand identity into a personalized card.
- 
Offer exclusive benefits tied to the card's usage.
- 
Strengthen your brand presence and loyalty.
**Virtual Card for online shopping**
Ensure more convenience and security for your customers' online payments.
- 
Increase convenience in e-commerce shopping.
- 
Dynamic CVV for enhanced transaction security.
**Voucher and mobile top-up marketplace**
Increase your competitive advantage by providing a marketplace for voucher redemption.
- 
Diversify your services by including an option for top-ups and voucher redemption.
- 
Create an alternative revenue stream by receiving a percentage of each voucher sold.
- 
Loyalty tool that uses the marketplace for referral and earn-and-burn campaigns.
[LEARN MORE](#contato)
[LEARN MORE](#contato)
## Pix
Allow your customers to make payments quickly and easily! Integrate Brazil's most widely used payment method into your business model with options that meet your needs:
- 
**Have your own company Pix:** become an Indirect Pix Participant without needing to be a financial institution, with the autonomy for configuration and customization.
- 
**Pix as a payment method:** connect to our API to generate QR Codes (static or dynamic) and keys (copy-and-paste) for payments in physical or virtual environments.
- 
**Pix as a bill payment option:** offer QR Codes across multiple channels to process transactions and instantly increase limits.
- 
**Pix on your bank slip:** connect to an API to generate bank slips (commercial or service invoices) with the Pix QR Code, reducing costs in payment settlement via barcode.
[LEARN MORE ABOUT PIX](#contato)
## Successful businesses are already automating collections with Automatic Pix. And you?
With just one authorization from the payer, debits are processed quickly, securely, and frictionlessly, reducing defaults and optimizing financial management, contributing to your business's cash flow, and more:
[LEARN HOW TO INTEGRATE](/en/solution/banking/pix-automatic/)
- 
**Flexible scheduling:** weekly, monthly, quarterly, semi-annual or annual charges.
- 
**Instant settlement:** values creditdata on time, with full visibility of the operation.
- 
**Low operational cost:** without the need for agreements, as with traditional direct debit.
## Bank slips
Optimize your customers' payments with security and convenience.
- 
Solutions for unbanked customers.
- 
Simple, intuitive, and secure.
- 
Reduction in operational costs.
## Bolepix
Expand choice options by offering the method that combines Brazil's most widely used payment methods - Pix and bank slips (boleto).
- 
Payments processed in seconds - no need to wait 2 days for clearance.
- 
Easy to use for both issuers and users, as both can use barcodes and Pix QR Codes to make payments.
- 
All the operational security that a bank slip and Pix can offer.
## Voucher and top-up marketplace
The best offers in credits and benefits with exclusive vouchers for your company.
- 
**Customer attraction and loyalty:** attract customers interested in benefits such as gift cards, service vouchers, and top-ups.
- 
**Targeted marketing:** conduct marketing campaigns promoting partners and exclusive discounts.
- 
**Strategic partnerships:** collaborate with other businesses in the marketplace and create strategic partnership opportunities, expanding the customer network and brand visibility.
[LEARN MORE](#contato)
### Who trusts in our solutions
## FAQ
What is a white-label digital bank?
A white-label digital bank is a **100% customized bank branded** by a company that partners with a technology provider who develops and supplies the entire financial services infrastructure through APIs. This model enables fintechs and organizations from any sector to have their own bank without needing to build everything from scratch.
How do I get my own white-label digital bank?
To have a white-label digital bank, you need to find a technology provider who offers a banking platform with all the necessary infrastructure, such as Dock. Thanks to the model's flexibility and customization possibilities, the company can have a bank that reflects its visual identity and brand value proposition.
What is Banking as a Service (BaaS)?
Banking as a Service is the solution that allows a company to have its own white-label bank without becoming a bank itself. In BaaS, the infrastructure provider acts as the payment institution and issuer, being responsible not only for technology and security but also for operations, licenses, compliance, and regulatory adherence.
How does a white-label bank work?
A white-label bank works through APIs, which allow the integration of robust services such as digital accounts, card issuance, payment management, etc. It is typically offered in a plug-and-play format, and the company offers its services through the provider's platform, only needing to develop the front-end with its brand.
What are the benefits of a white-label bank?
The benefits of a white-label digital bank include having your own bank without needing to develop infrastructure from scratch, which speeds up implementation and optimizes processes, as the solution is already built, tested, and validated. This also allows the product to be brought to market much faster. Furthermore, a white-label digital bank offers a unique opportunity to expand a company's operations and generate new revenue streams.
What services can a white-label bank offer?
Among the services that a company using the white-label bank model can offer are a complete digital account with different functionalities (Pix, invoice generation, bill payments, top-ups, loans, etc.), its own app, a debit card with its brand, a virtual card for online purchases, and a marketplace for vouchers and top-ups.
Is a banking license required to operate a white-label digital bank?
When operating as a white-label digital bank, the Banking as a Service provider is responsible for both the technical and regulatory aspects, while the contracting party can focus on its core business and on acquiring, engaging, and retaining customers.
What technologies are used in white-label digital banks?
The technologies used in white-label digital banks are based on financial APIs, which function as feature aggregators and are ready to be integrated. The APIs connect the front-end with the digital bank's platform.
How long does it take to launch a white-label digital bank?
The time to launch a white-label digital bank depends on various factors, but it is undoubtedly much shorter than developing a proprietary platform from scratch. Thanks to API technology, Banking as a Service enables a much faster time-to-market for companies that want to have their own bank.
What are the challenges of implementing a white-label digital bank?
Among the challenges of implementing a white-label digital bank is finding the ideal Banking as a Service provider, one that has an adaptable platform and offers everything needed – including treasury, account opening, processing, transaction monitoring, fraud prevention tools, and transactional anti-fraud solutions.
Can I offer Pix in a white-label digital account?
Yes, you can offer Pix in a white-label digital account, allowing users to make transfers and payments quickly and conveniently using the Central Bank's instant payment system.
What are the requirements to offer Pix in a white-label digital account?
To act as an **Indirect Participant of Pix**, you need to be connected to a Direct Participant, like Dock. Furthermore, you need to meet the requirements established by the Central Bank, which include obtaining authorization to act as a financial or payment institution, proving the full subscription and maintenance of at least R$ 5 million in capital, and structuring a minimum compliance program.
How to ensure the security of Pix transactions in a white-label digital account?
Ensuring the security of Pix transactions has been one of the challenges for the Central Bank and the sector as a whole. To minimize risks and protect users and institutions, the CB has been implementing specific measures, such as time restrictions, new device monitoring, and Pix key adjustments. However, institutions must also implement prevention solutions to strengthen protection against fraud.
Is it possible to integrate payment slips (boletos) into a white-label digital account solution?
It is possible to integrate payment slips (boletos) into a white-label digital account solution through specific APIs for this purpose. Dock's Banking solution includes the Boleto functionality, allowing the generation of customized payment slips that include changes to the due date, fines, interest, and discounts.
## Content and events to go further
Discover our exclusive content and events that will unlock even more business potential.
[
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")
[
Banking
### How to stand out in the financial services sector in a context of multi-banking.
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")
[
](https://dock.tech/en/fluid/blog/banking/payment-initiator/ "Payment initiator and PixWhat changes in the user journey with ITP?")
[
Banking
### Payment initiator and PixWhat changes in the user journey with ITP?
](https://dock.tech/en/fluid/blog/banking/payment-initiator/ "Payment initiator and PixWhat changes in the user journey with ITP?")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/payment-initiator/ "Payment initiator and PixWhat changes in the user journey with ITP?")
[
](https://dock.tech/en/fluid/blog/banking/med-2-0/ "MED 2.0: the new era of security. Pix against fraudblows and strikes")
[
Banking
### MED 2.0: the new era of security. Pix against fraudblows and strikes
](https://dock.tech/en/fluid/blog/banking/med-2-0/ "MED 2.0: the new era of security. Pix against fraudblows and strikes")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/med-2-0/ "MED 2.0: the new era of security. Pix against fraudblows and strikes")
[
](https://dock.tech/en/fluid/blog/banking/ITP-Open-Finance/ "ITP Open Finance: How the system is revolutionizing the way Brazilians pay.")
[
Banking
### ITP Open Finance: How the system is revolutionizing the way Brazilians pay.
](https://dock.tech/en/fluid/blog/banking/ITP-Open-Finance/ "ITP Open Finance: How the system is revolutionizing the way Brazilians pay.")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/ITP-Open-Finance/ "ITP Open Finance: How the system is revolutionizing the way Brazilians pay.")
[
](https://dock.tech/en/fluid/blog/banking/pix-installments/ "Pix Central Bank installment plan: everything about this credit option via Pix")
[
Banking
### Pix Central Bank installment plan: everything about this credit option via Pix
](https://dock.tech/en/fluid/blog/banking/pix-installments/ "Pix Central Bank installment plan: everything about this credit option via Pix")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/pix-installments/ "Pix Central Bank installment plan: everything about this credit option via Pix")
[
](https://dock.tech/en/fluid/blog/banking/baas-regulation/ "BaaS Regulation: Central Bank regulates partnerships for offering financial services with Joint Resolution No. 16/2025")
[
Banking
### BaaS Regulation: Central Bank regulates partnerships for offering financial services with Joint Resolution No. 16/2025
](https://dock.tech/en/fluid/blog/banking/baas-regulation/ "BaaS Regulation: Central Bank regulates partnerships for offering financial services with Joint Resolution No. 16/2025")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/baas-regulation/ "BaaS Regulation: Central Bank regulates partnerships for offering financial services with Joint Resolution No. 16/2025")
[
](https://dock.tech/en/fluid/blog/banking/how-to-become-a-payment-institution/ "How to become a Payment Institution in Brazil? Learn how to become a PA")
[
Banking
### How to become a Payment Institution in Brazil? Learn how to become a PA
](https://dock.tech/en/fluid/blog/banking/how-to-become-a-payment-institution/ "How to become a Payment Institution in Brazil? Learn how to become a PA")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/how-to-become-a-payment-institution/ "How to become a Payment Institution in Brazil? Learn how to become a PA")
[
](https://dock.tech/en/fluid/blog/banking/BaaS-Embedded-Finance/ "BaaS and Embedded Finance: understand the connection between the models and how to leverage this potential in business")
[
Banking
### BaaS and Embedded Finance: understand the connection between the models and how to leverage this potential in business
](https://dock.tech/en/fluid/blog/banking/BaaS-Embedded-Finance/ "BaaS and Embedded Finance: understand the connection between the models and how to leverage this potential in business")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/BaaS-Embedded-Finance/ "BaaS and Embedded Finance: understand the connection between the models and how to leverage this potential in business")
## Contents and events to go further
Discover our content and exclusive events that will unlock even more potential in your business.
[
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")
[
Banking
### How to stand out in the financial services sector in a context of multi-banking.
](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/multi-banking/ "How to stand out in the financial services sector in a context of multi-banking.")
[
](https://dock.tech/en/fluid/blog/banking/benefits-of-bre-b/ "Benefits of Bre-B: Colombia's instant payments system has the potential to boost domestic businesses")
[
Banking
### Benefits of Bre-B: Colombia's instant payments system has the potential to boost domestic businesses
](https://dock.tech/en/fluid/blog/banking/benefits-of-bre-b/ "Benefits of Bre-B: Colombia's instant payments system has the potential to boost domestic businesses")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/benefits-of-bre-b/ "Benefits of Bre-B: Colombia's instant payments system has the potential to boost domestic businesses")
[
](https://dock.tech/en/fluid/blog/banking/dimo/ "DiMo and the promise of a revolution in instant payments and financial inclusion in Mexico")
[
Banking
### DiMo and the promise of a revolution in instant payments and financial inclusion in Mexico
](https://dock.tech/en/fluid/blog/banking/dimo/ "DiMo and the promise of a revolution in instant payments and financial inclusion in Mexico")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/dimo/ "DiMo and the promise of a revolution in instant payments and financial inclusion in Mexico")
[
](https://dock.tech/en/fluid/blog/banking/immediate-payments/ "Instant Payments: How Bre-B Brings Innovation and Financial Inclusion to the Colombian Ecosystem")
[
Banking
### Instant Payments: How Bre-B Brings Innovation and Financial Inclusion to the Colombian Ecosystem
](https://dock.tech/en/fluid/blog/banking/immediate-payments/ "Instant Payments: How Bre-B Brings Innovation and Financial Inclusion to the Colombian Ecosystem")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/immediate-payments/ "Instant Payments: How Bre-B Brings Innovation and Financial Inclusion to the Colombian Ecosystem")
[
](https://dock.tech/en/fluid/blog/banking/new-economy/ "The new economy and the strategic role of embedded finance in business transformation.")
[
Banking
### The new economy and the strategic role of embedded finance in business transformation.
](https://dock.tech/en/fluid/blog/banking/new-economy/ "The new economy and the strategic role of embedded finance in business transformation.")[LEARN MORE](https://dock.tech/en/fluid/blog/banking/new-economy/ "The new economy and the strategic role of embedded finance in business transformation.")
[
](https://dock.tech/en/fluid/blog/banking/bre-b/ "Bre-B: instant payment system is inspired by Pix and promises to transform Colombia's financial sector")
[
Banking
...15881 bytes truncated...
The tool call succeeded but the output was truncated. Full output saved to: /home/alex/.local/share/opencode/tool-output/tool_d62512fde001W15W4pu9YDPg0l
Use the Task tool to have explore agent process this file with Grep and Read (with offset/limit). Do NOT read the full file yourself - delegate to save context.
Assistant (Plan · GPT-5.4 · 73.1s)
Thinking:
Analyzing partner setups
I need to help the user compare their setup with other partners like Dock and Celcoin. Their initial idea was just to use BaaS and perhaps PaaS. Right now, we're in a read-only planning mode. I might analyze Dock's docs, but I wonder if it's really necessary since I've already gathered enough from their public documentation. Maybe I should try to find more specific documents from Dock developers, but I could also consider examining the truncated file from earlier.
Thinking:
Exploring Dock documentation
The instructions suggest using the Task to let the explore agent process the truncated file with Grep and Read, so I should follow that. I need to analyze the saved Dock page output to find useful information for comparison since the user wants to enhance evidence. While we might already have enough, I could also consider using webfetch for specific Dock pages, especially if they have better developer documentation. It might help to clarify with the user about their comparison needs to provide the best information.
Thinking:
Comparing BaaS and PaaS options
I want to highlight that if we're looking at just BaaS and possibly PaaS, Celcoin seems like the most suitable option due to its modular BaaS and Pix stack, along with detailed documentation. Z.ro could work too but leans more towards crypto and product focus. However, if we're considering a comprehensive solution like a full white-label bank with cards and acquiring, Dock may be the strongest, though it’s heavier. I think I should separate the analysis for BaaS-only and BaaS+PaaS, and gather more specific details from the Celcoin and Dock documentation as needed.
I have enough to compare the partner shapes. I’m only filling one gap: Dock’s developer and product surface is less public than Celcoin’s, so I’m validating whether we should treat Dock as a fuller white-label bank stack rather than a leaner BaaS/Pix-first partner.
Tool: task
Input:
{
"description": "Inspect Dock docs",
"prompt": "You are comparing Dock versus Z.ro and Celcoin for a Brazil fintech launch focused on partner-led custody, employer/employee onboarding, Pix payouts, and optional payment acceptance. Use read-only tools only. Analyze the truncated Dock outputs saved by the environment if helpful, and search Dock's public developer/docs site if possible. Return a concise summary with: 1) what Dock clearly offers publicly, 2) what is missing or less clear from public docs versus Celcoin/Z.ro, 3) whether Dock appears better suited for a full white-label bank/cards/acquiring stack or a lean BaaS+Pix launch, and 4) any evidence for indirect Pix participation, digital accounts, cards, acquiring, fraud tooling, and developer friendliness. Do not modify files.",
"subagent_type": "explore",
"thoroughness": "medium"
}
Output:
task_id: ses_29dae880bffewOqrZVDMBnOSnS (for resuming to continue this task if needed)
<task_result>
1) Publicly, Dock clearly offers:
- A broad embedded-finance stack: Banking, Cards & Credit, Acquiring, Fraud Prevention, and a platform layer called Dock One.
- Banking modules including Conta Digital, Pix, Boletos, and voucher/recharge marketplace.
- Card issuing/processing: crédito, débito, pré-pago, private label, benefícios, global, consignado, tokenização.
- White-label acquiring.
- Fraud tooling: biometric auth, background check, transaction antifraud, multichannel communication.
- Strong regulatory/scale claims: “IP regulada e participante direto Pix (código bancário #301)”, 70M active accounts, 1.3B Pix in 12 months, 30+ card brands homologated.
2) What is missing / less clear publicly vs Celcoin/Z.ro:
- Dock’s public site is much more marketing-led than Celcoin’s docs.
- I found clear breadth, but less public detail on:
- API structure/endpoints
- auth/security model
- sandbox/homologation flow
- webhooks/events
- KYC/onboarding workflows for employer/employee setup
- explicit Pix indirect-participant support
- By contrast, Celcoin’s public developer docs are much clearer and deeper on:
- account opening/KYC
- Pix cash-in/cash-out
- Pix Automático
- Pix Indireto
- webhooks
- mTLS, idempotency, rate limits, sandbox/homologation
- acquiring/subacquiring APIs
- Z.ro’s public docs are clearer than Dock’s on product surface/navigation, but from what I could fetch they still look lighter than Celcoin in public implementation detail.
3) Best fit:
- Dock appears better suited publicly for a full white-label bank/cards/acquiring stack than for a lean BaaS+Pix launch.
- Reason: its strongest public message is “one-stop-shop” breadth across banking + cards + acquiring + fraud + regulatory handling.
- For a lean Brazil BaaS+Pix launch, Celcoin looks easier to validate from public docs because the operational/API details are more explicit.
4) Evidence by category:
- Indirect Pix participation:
- Dock: no public evidence found for indirect participation; public claim is direct Pix participant.
- Celcoin: explicit public docs for “Pix Indireto.”
- Digital accounts:
- Dock: explicit “Conta Digital.”
- Cards:
- Dock: very strong evidence; multiple card products and processing/licensing claims.
- Acquiring:
- Dock: explicit “Acquiring as a service,” white-label acquiring, 30+ brands homologated.
- Fraud tooling:
- Dock: explicit fraud-prevention suite and onboarding-to-transaction monitoring language.
- Developer friendliness:
- Dock: some positive signals (“APIs”, developer portal, modular platform), but public self-serve technical depth is less clear than Celcoin.
- Celcoin: strongest public developer-friendliness evidence.
- Z.ro: decent public docs presence, but less evidence than Celcoin from what I could fetch.
Bottom line:
- Dock looks credible and strong for a broad, enterprise-grade embedded-finance stack.
- If your near-term launch is partner-led custody + onboarding + Pix payouts first, Celcoin is easier to underwrite from public docs.
- Dock becomes more attractive if you expect to add cards, acquiring, and fraud tooling relatively early.
Local sources checked:
- /home/alex/projects/payroll/sessions/session-ses_2f39.md
- /home/alex/.local/share/opencode/tool-output/tool_d6251a3a10019GnQn8F2QdOtdz
If you want, I can turn this into a tighter Dock vs Celcoin vs Z.ro decision table for your exact launch scope.
</task_result>
Assistant (Plan · GPT-5.4 · 155.3s)
Thinking:
Comparing setup options
I need to answer the user's request to compare our setup with potential partners like Dock and Celcoin. The initial idea was to use their BaaS and possibly their PaaS. There's a system reminder that we're in read-only mode, so no edits are allowed. I’ll focus on a comparative analysis and mention that our evaluation should target our specific needs. I'll highlight evidence from docs while noting the limitations due to public documentation, especially around Dock.
Thinking:
Providing decision matrix
I need to create a decision matrix and a recommendation for our BaaS and PaaS launch. From what I've gathered, Celcoin seems like the best fit, followed by Z.ro, with Dock in third place. I want to make sure I consider all the information thoroughly. Our internal documents specify needs like partner-led custody, KYC, and payment acceptance. Celcoin has extensive developer docs, while Dock has a broad stack but less detailed technical info. I need to present this clearly.
Thinking:
Mapping BaaS and PaaS requirements
I need to define what "BaaS and maybe PaaS" means for our project. For BaaS, that includes regulated custody, user accounts and wallets, KYC/KYB, Pix cash-out, internal transfers, and statements/webhooks. For PaaS, it's about customer payment collection, specifically Pix QR, cards, boletos, and merchant onboarding. I should compare these requirements using this architecture for each partner. It's crucial to clearly outline the specific layers we need to evaluate each potential partner accurately.
Thinking:
Evaluating onboarding options
I'm looking at the onboarding systems for employer/employee setups, focusing on accounts, wallets, and Pix payouts. I think there’s an optional PaaS layer that might include Pix cash-in, merchant onboarding, or even split payments. What we need to actually build includes a commission engine, internal ledgers, and analytics. I should frame this as a "Best use of partner" table, considering whether we really need full neobank features right now or just BaaS/PaaS options. Celcoin seems to be a good fit, and Z.ro could be simpler but less established.
Thinking:
Comparing key dimensions
I need to compare the key dimensions for our options. This includes looking at public API completeness, BaaS coverage, PaaS coverage, flexibility to start small, card acquiring depth, regulatory posture, and what we still need to build ourselves.
For scores, Z.ro is a decent option if we want a single provider for BaaS and Pix. Celcoin appears to be the strongest public fit for our needs with extensive documentation. However, Dock might be the best choice if we're considering a full white-label bank and associated services in the long run.
Thinking:
Evaluating transparency and complexity
I'm noticing that the public docs for some options are less transparent, which could lead to more operational overhead and complexity that might be unnecessary for a lean launch. The user specifically asked about Dock and Celcoin, but I think it could also be beneficial to include Z.ro in the conversation.
I should be careful not to bring in too many other options unless they're relevant. If the user wants, I can also compare QI Tech.
Thinking:
Evaluating payment options
I'm thinking of using BaaS exclusively, with maybe PaaS for some greenfield merchants. If we want a clean payment-linked commission from the start, going with Celcoin's Pix/PaaS or Z.ro PaaS seems easier since they provide a direct event source. I need to clarify what changes by provider if we go BaaS-only with optional PaaS. I should also inspect the Dock developers' documentation, but there's only a "ReadMe" file available.
Thinking:
Evaluating participant requirements
I just noticed the FAQ on the site says that to act as an indirect participant, I must connect to a direct participant like Dock and meet certain requirements. This includes having at least R$5 million in capital and a compliance program. That seems strange since not all customers might need this as indirect participants. It looks like Dock is aiming for partners who already have their own compliance maturity, which raises an important concern.
Thinking:
Considering architecture sense
It sounds like I'm thinking that architecture still holds value, especially with a partner that offers regulated money movement and optional payment acceptance. This means that architecture can effectively integrate with financial services, which is interesting. It seems that ensuring financial regulation and payment options can enhance the overall design and functionality of architectural projects. I'm curious about the implications of this kind of partnership and how it can impact future designs!
Thinking:
Considering BaaS and PaaS options
I think I need to mention that maybe the user’s structure involves their BaaS and PaaS. If we keep BaaS mandatory and make PaaS optional, it seems Celcoin has the clearest modular separation. Z.ro can do something similar, but the features split for PaaS are narrower in the public eye. Dock has more capabilities but could be overkill, making it a heavier option commercially and operationally.
Thinking:
Considering compression strategy
I’m checking the length of the tool outputs, and it seems pretty huge! Compression might be helpful here, particularly since the system suggests using it on closed ranges. Since my previous exploration is all closed off, I think it’s a good idea to compress everything from m0001 to m0014 before finalizing. I really want to create an exhaustive summary with all my findings, so let’s definitely do that!
Thinking:
Analyzing banking features
So, banking here involves digital accounts, various card types, and some fraud detection tools like biometric authentication. Notably, they have impressive stats, like 70 million active accounts and a direct participant code for Pix. The FAQ hints at some regulatory maturity needed for indirect Pix paths. It looks like while their marketing is strong, the public technical documentation isn't as deep compared to competitors like Celcoin. This makes this solution better suited for broader embedded finance rather than a straightforward BaaS+Pix launch.
Thinking:
Exploring modular infratech
I see that the site presents a modular approach to infrastructure technology with various offerings like cel_banking, cel_payments, and cel_credit. They mention having a PI license and are a direct participant in Pix, claiming impressive monthly transaction volumes. The Pix functionality has two modes for different types of companies, providing options from simple to more complex setups. They also emphasize 24/7 support and operational autonomy, with a management console to facilitate easiness in integrating services. It's an interesting setup!
Tool: compress
Input:
{
"topic": "Partner Research",
"content": [
{
"startId": "m0001",
"endId": "m0013",
"summary": "User first asked: \"I was looking at Z.ro bank at they seem to be able to provide most of the services we need to get started, go over their documentation and tell me exactly what we need. https://zrobank.com/en\" The repo context was reviewed before any conclusions: `docs/core-idea.md`, `docs/brazil-market.md`, and `docs/year-one-roadmap.md` establish the product as Brazil-first `commission infrastructure`, not a neobank/payroll/credit-first product. Core assumptions preserved during research: partner-led custody/compliance; `Pix`-based instant access to earned commissions; internal ledger with `earned`/`available`/`settled`; v1 employer and employee onboarding; employer/employee dashboards; reserves and holdbacks for reversals; cards and stored balances later; credit much later.\n\nResearch then pulled Z.ro public website pages and public developer docs.\n\nZ.ro website/public positioning findings:\n- Main site `https://zrobank.com/en` positions Z.ro as a `developer-first bank` with open APIs.\n- Public solution buckets: `Local Payments`, `Cross-border Payments (eFX)`, `Cryptocurrencies`, `Financial Infratech`, plus country pages for Brazil/Argentina/Chile/Peru.\n- Brazil page highlights: Pix send/receive at scale, exchange, card/digital-wallet acceptance, webhooks, reconciliation, scheduling, static/dynamic QR codes, automated refunds/returns, and a multi-currency digital account.\n- Financial Infratech page highlights: BaaS for fintechs/payment providers/ERP/digital platforms; backoffice for sub-account ecosystems; payment gateway; internet banking; white-label application.\n- Local Payments page highlights: cards, digital wallets, conversion, scale, dashboards, automatic reconciliation, personalized reports.\n- Site credibility claims noted from public pages/media references: payment institution license coverage, A-level company in Brazil Central Bank ranking, audited by EY/KPMG, scale claims, and LATAM presence.\n\nZ.ro developer docs findings:\n- Public docs root: `https://coinwise-io.github.io/zrobank-doc-api/`.\n- Productized API families documented publicly:\n - `Banking as a Service` (`/baas/...`)\n - `Pix as a Service` (`/paas/...`)\n - `Gateway` (`/gateway/...`)\n - `Crypto as a Service`\n- API setup/auth:\n - Credentials are `API ID` + `API Key`.\n - Access token generated from `/auth/signin`; Bearer JWT required for API calls.\n - Publicly documented sandbox base URLs exist for BaaS (`https://api-baas-hml.zrobank.xyz/api`), PaaS (`https://paas-hml.zrobank.xyz/api`), and Gateway (`https://payments-api-hml.zrobank.xyz/api/documentation`).\n - HTTPS required.\n - Request model includes `nonce`, `x-transaction-uuid`, replay protection schemas, and idempotence/replay guidance.\n- BaaS public endpoint surface includes:\n - Pix keys/payments/devolutions/deposits\n - wallets, wallet accounts, operations, reports\n - P2P transfers between master/sub-account wallets\n - user bank accounts\n - legal person onboarding, natural person onboarding, shareholders, legal representatives, company docs, merchant onboarding, company registration\n - cards (virtual/physical/activation/blocking/etc.)\n - scheduled Pix, automatic receiver limits, open finance, cross-border modules\n- PaaS public endpoint surface includes:\n - Pix keys, static/dynamic QR codes, split payments, Pix payments, deposits, wallets, operations, cards, scheduled/recurring Pix, open finance\n- Gateway public docs include:\n - payment/withdraw/refund/KYC webhooks\n - customer bank-account allowlisting for deposits/withdrawals\n - payment webhook payloads with payer/receiver/bank account data\n- Z.ro public onboarding guides were detailed enough to map exact requirements:\n - Legal person onboarding flow: create user account (`POST /users/accounts`), create legal-person onboarding, create shareholders, create legal representatives, upload representative docs (`selfie`, identity doc, qualification declaration; optional income/address proof), upload legal-person docs (`SOCIAL_CONTRACT`, plus `BALANCE_SHEET` or `REVENUE_STATEMENT`, optional KYC/AML policy), finalize, then poll or receive webhook status.\n - Natural person onboarding flow: create user account, create onboarding with address/nationality/PEP and optional occupation/income/patrimony, upload selfie + docs or digital identity, poll or receive webhook status.\n- Z.ro public webhook model (BaaS) includes events like `PAYMENT`, `PAYMENT FAILED`, `DEVOLUTION`, `DEVOLUTION FAILED`, `DEVOLUTION RECEIVED`, `DEPOSIT`, `ONBOARDING FINISHED`, `ONBOARDING REJECTED`, `MERCHANT ONBOARDING KYC STATUS`, `WALLET_ACCOUNT_BALANCE_UPDATED`, and judicial block/unblock events. Webhooks are configured through their team and can support optional auth methods.\n- Specific endpoint facts used in analysis:\n - `POST /v1/operations/p2p-transfers` enables internal transfer between master/sub-account wallets.\n - `GET /v1/users/banking/accounts` returns user bank account details.\n - `POST /v1/cards/virtual` creates virtual cards.\n - `POST /split-payments/pix/qr-codes/static` creates static split Pix QR codes with account-level split instructions.\n - Merchant onboarding endpoint explicitly says it registers a legal person as a commercial establishment at `Dock Acquiring`, which implies some payment-acceptance capability may sit on top of Dock rather than being fully native.\n- Z.ro support/env notes gathered:\n - Public docs mention sandbox and production environments and route support/commercial questions to `meajuda@zrobank.com.br` / `comercial@zrobank.com.br` (plus other emails on docs/site).\n\nConclusion delivered to the user from the Z.ro pass:\n- Z.ro appears able to cover much of the regulated money-movement and onboarding stack needed for the Brazil v1, especially if used `BaaS-first`.\n- What Z.ro can likely provide for this product: partner-led custody/accounts/wallets, employer KYB, employee KYC, Pix payouts/cash-outs, wallet/account operations, internal wallet transfers, statements/reports/reconciliation, webhooks, and later cards.\n- Optional/conditional Z.ro modules: PaaS/Gateway if customer payment acceptance is brought in-house from day one.\n- What Z.ro does **not** replace: the startup’s commission rules engine, internal ledger states (`earned`, `available`, `settled`), reserve/holdback logic, disputes/clawbacks, employer analytics, and the product-specific application layer.\n- What would be needed from Z.ro commercially/technically if chosen:\n - BaaS product/program setup with sandbox + production access, `API ID`, `API Key`, and `product_uuid`\n - employer onboarding/KYB under Z.ro’s flow\n - employee onboarding/KYC under Z.ro’s flow\n - Pix payout flow and internal wallet movement flow\n - webhook registration and reconciliation wiring\n - internal implementation of auth/token management, nonce/transaction UUID generation, idempotent webhook processing\n- Specific open diligence questions identified for Z.ro:\n - whether one master program can hold funds and create segregated employer/employee wallets or whether each employer needs full legal-person account structure\n - whether employees can cash out via Pix without a full Z.ro account or if onboarding is mandatory\n - fees, SLAs, production limits, and webhook guarantees\n - how refunds/devolutions interact with already-moved employee balances\n - whether each employer needs separate merchant onboarding if Gateway/acquiring is used\n\nUser then followed up: \"compare this setup with other potential partners like Dock and Celcoin. The idea I envisioned at first was just using their BaaS and maybe their PaaS.\" Plan/read-only mode became active, so only research/analysis continued.\n\nComparison research gathered public evidence for Dock and Celcoin against the intended architecture: use partner `BaaS` for custody/onboarding/payouts and optionally add `PaaS` / payment-acceptance modules, while still building the proprietary commission engine + internal ledger.\n\nCelcoin public site findings:\n- Celcoin positions itself as `infratech financeira` / embedded-finance infrastructure.\n- Public solution groups include:\n - `cel_banking`: BaaS, liquidating bank, white-label cards, core banking, data sharing/open finance, regulatory support\n - `cel_payments`: Pix, payment gateway, bill pay, ITP, recargas, saque/deposito, etc.\n - `cel_credit`: CCB, escrow, core credit, receivables/credit management\n - `mybenk`: white-label app/web + backoffice\n- Public company-scale claims surfaced: PI license, direct Pix participation, Open Finance roles, large transaction volume, many enterprise customers.\n- Celcoin Pix page specifically states:\n - strong scale/ANS claims for Pix processing\n - two modes: simpler Pix offering for companies getting started and `Pix Indireto` for already licensed companies\n - treasury/account-like controls, complete key management, management console, support, and a path to evolve participant model without replatforming\n- Public site strongly emphasizes modularity and white-label/embedded distribution.\n\nCelcoin developer docs findings (important because they were much more detailed than Dock’s public technical surface):\n- Public developer docs are extensive and navigable via `developers.celcoin.com.br`.\n- Clear docs exist for:\n - credentials/access\n - API security\n - idempotency\n - `mTLS`\n - rate control\n - homologation\n- BaaS/Core docs publicly expose a broad operational surface:\n - onboarding/KYC and account opening\n - account management / listing / status updates / judicial blocks\n - balances, statements, consolidated statement data\n - Pix cash-in by account, random key, individualized keys, static and dynamic QR\n - Pix cash-out by bank account, Pix key, static/dynamic QR\n - split Pix on dynamic QR (immediate/duedate)\n - Pix Automático\n - Pix Inteligente / sweeping accounts\n - Pix Indireto\n - internal transfers between accounts\n - boleto issuance, boleto split, CNAB\n - TED and reconciliation\n - webhooks and webhook management\n - subadquirência / Acquiring-as-a-Service and chargebacks if needed\n - cards and card management\n - Open Finance/ITP and many adjacent modules\n- Celcoin docs therefore gave strong public evidence that a modular `BaaS first, PaaS optional` architecture is feasible with them.\n\nDock public-site findings:\n- Dock positions itself as a broad one-stop shop for financial services.\n- Public solution buckets found on site:\n - `Banking`\n - `Cards & Credit`\n - `Acquiring`\n - `Fraud Prevention`\n - `Dock One` platform\n- Public banking/product claims include:\n - white-label digital account\n - Pix\n - boletos / bolepix\n - debit and virtual cards\n - voucher/top-up marketplace\n - automatic Pix\n- Public cards/acquiring/fraud breadth is much heavier than Z.ro’s publicly visible stack:\n - credit, debit, prepaid, private-label, global, multibenefits, payroll-deductible cards, tokenization\n - white-label acquiring / multiple networks\n - fraud tools such as biometric auth, background check, transaction antifraud, multichannel comms\n- Public scale/regulatory claims include:\n - regulated PI and direct Pix participant (#301)\n - very large account and Pix volume claims\n - 30+ networks / 400+ customers / multi-country presence\n- Important nuance from Dock’s public banking/Pix pages and FAQ:\n - Dock strongly frames itself as a provider for a full white-label bank stack.\n - Some public FAQ language about acting as an `Indirect Participant of Pix` references BC authorization, minimum capital, and compliance requirements, which makes Dock’s public framing feel more enterprise/regulatory-heavy than the lightest outsourced model.\n- Dock’s public developer and API details were much less clear from accessible public pages than Celcoin’s; available public material was far more marketing-led than implementation-led.\n\nState of comparison at the end of this compressed range:\n- The architecture the user described (`BaaS` and maybe `PaaS`) was preserved as the evaluation frame.\n- Preliminary comparison direction based on public materials alone:\n - `Celcoin` appeared strongest for a modular, API-heavy `BaaS first / optional PaaS later` launch because the public technical surface is broad and explicit.\n - `Z.ro` appeared plausible as a leaner one-partner BaaS/Pix option with decent public docs and explicit onboarding/wallet/Pix primitives, but with lighter public breadth than Celcoin and some payment-acceptance signs pointing to Dock underneath.\n - `Dock` appeared strongest as a full embedded-finance / white-label bank + cards + acquiring + fraud stack, but less clearly optimized for the narrowest launch and less transparent publicly on API/onboarding/webhook specifics."
}
]
}
Output:
Compressed 13 messages into [Compressed conversation section].
User
▣ DCP | -146.9K removed, +3.1K summary
│⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿███████│ ▣ Compression #1 -146.9K removed, +3.1K summary → Topic: Partner Research → Items: 13 messages and 40 tools compressed
Assistant (Plan · GPT-5.4 · 83.5s)
Thinking:
Evaluating recommendations and plans
I think we can provide a recommendation with a decision table, outlining what each partner covers and where the risks lie. The plan mode suggests presenting a clear plan and addressing any loose ends. It might help to ask a couple of clarifying questions about the user's priorities, like whether they care more about speed, breadth, or enterprise considerations. I want to offer analysis first to inform our approach. We may not need extra research since our context is already built.
Thinking:
Drafting a comparison and diligence plan
I should provide a concise comparison and a diligence plan, then ask which direction the user wants to pressure-test next. I may want to check if any documents in the repository mention partner evaluation, like “docs/ideas-for-review” or any relevant market memo. I’ll make sure to keep it simple with flat lists and no nested bullets. The final answer will include sections like Bottom Line, Comparison, What Each Partner Covers, Recommended Path, and Diligence Questions. I might note that Celcoin seems strongest for BaaS and PaaS, followed by Z.ro and Dock.
Thinking:
Considering product components
I think I need to mention that our core product requires certain internal components, regardless of our partnerships. This includes things like a commission rules engine, internal ledger states for earnings, and tools for reconciliation.
I'm reflecting on how I might present this information. A decision matrix could work, and while a markdown table is an option, simple bullet points might be more concise. I’m weighing whether to include headers or keep it straightforward without nested bullets. A table could help compare three vendors easily.
Thinking:
Clarifying questions and evaluating options
I need to consider asking the user some clarifying questions. I could end with two questions: “Do you want to optimize for the fastest v1 with external payment event ingestion, or for owning payment acceptance from day one?” and “Do you expect card support soon?” Since the user wants a comparison, I might provide options first and then ask. I’ll evaluate Dock, Celcoin, and Z.ro based on implementation risk, public evidence, and scope creep, keeping the startup concept in mind.
Thinking:
Evaluating partner options for employee experience
I realize employee experience is crucial, so I need a partner for accounts, wallets, onboarding, and Pix payouts. If we explore PaaS and acquiring, we’ll require payment acceptance features, like QR codes and possibly split payments, but that’s not essential at the start. When comparing partners, I’ll consider two launch modes: payout-first and acceptance-led. Celcoin stands out for both modes, Z.ro works well for payout-first, and Dock excels in acceptance-led but may be overkill initially.
Thinking:
Ranking partner options for API and onboarding
When considering public API due diligence, I would rank the partners as follows: Celcoin first, Z.ro second, and Dock third. For onboarding clarity and webhooks, I again have Celcoin as the top choice, Z.ro second, and Dock as uncertain. If I'm looking for simplicity and a leaner partner relationship, Z.ro could be first or second. However, if Z.ro relies on Dock for merchant onboarding, that could complicate things if acceptance is needed right away.
Thinking:
Considering payment acceptance strategy
I’m thinking about how payment acceptance may partly depend on Dock. First, I should clarify the topology and fees. The Dock offers a full embedded-finance stack, including digital accounts and fraud management, but its public implementation detail is weaker, potentially making it heavier for a version 1 launch.
For the architecture recommendation, I suggest starting with a BaaS-only version unless payment acceptance is crucial. I could also explore using specific partners and considering various paths depending on requirements, based on speed, coverage, and vendor preferences.
Thinking:
Identifying essential modules
I need to outline exactly what’s necessary, regardless of the partner involved. First, I could list essential modules like KYB for the employer's legal entity and KYC for each employee receiving funds.
The program model might be a master account with segregated balances, and I should consider Pix cash-out options and internal transfers. Other important features would include webhooks, reconciliation, statement exports, and refund handling. If I decide on PaaS, I’ll need to think about merchant onboarding, Pix collections, and chargeback rules for any card transactions.
Thinking:
Formulating open questions for the user
I need to consider some open questions to ask the user. For instance, do they need to own payment acceptance from the start, or can they begin with employer-provided payment events?
Also, do they want employee cards or stored balances in the first year, or is that unnecessary for now? I'm curious whether they’re prioritizing a quick launch, a broad platform, or minimizing partner concentration risk. Depending on their answers, I might suggest Celcoin and Z.ro or include Dock. I should also outline due diligence steps to follow, like running a 12-question diligence pack and requesting account diagrams.
Bottom Line
For the setup you described, Celcoin looks like the best public-fit partner for BaaS first, PaaS optional.
My current ranking, based on public docs and positioning:
BaaS-first payout launch:Celcoin>Z.ro>DockBaaS + payment acceptance from day one:Celcoin>Dock>Z.roFull white-label bank/cards/acquiring roadmap soon:Dock>Celcoin>Z.ro
Why
Celcoinhas the clearest public technical surface for the exact stack you want: onboarding, accounts, balances, Pix in/out, internal transfers, webhooks, split Pix, homologation, idempotency,mTLS, and optional acquiring/cards.Z.rois a credible leaner option forBaaS/Pixfirst. Its public docs are good enough to map real onboarding and wallet flows. Main caution: public breadth is lighter than Celcoin, and some merchant/acquiring flow appears to sit on top ofDock Acquiring.Docklooks strongest as a broad embedded-finance platform, not as the narrowest v1 partner. Great if you want banking + cards + acquiring + fraud relatively early, but the public implementation detail is much thinner.
What You Need From Any Partner
- employer
KYB - employee
KYC - one master program with segregated employer/employee balances or subaccounts
Pixpayout / cash-out- internal balance transfers
- webhooks and reconciliation
- statements / reports
- sandbox / homologation
- reversal / devolution handling
- production limits, SLA, support
- optional
PaaS: Pix collection, QR, split settlement, merchant onboarding
What Matters Most
The real decision is not feature breadth. It is whether the partner can support your balance topology and reversal model:
- employer funds must stay clearly separated
- employee balances need
earned,available,settledtreatment in your own ledger - reversals/refunds cannot break already-released commissions
- reserve / holdback mechanics must be possible
That is where vendor risk actually sits.
Recommended Path
- Start
BaaS-firstunless owning payment acceptance is essential on day one. - Use employer payment events or existing PSP data as the commission trigger if possible.
- Shortlist
CelcoinandZ.rofirst for v1. - Keep
Dockin the process only if cards, acquiring, or fraud tooling may matter in the first 12-18 months.
What You Still Must Build
None of these partners replace your core product:
- commission rules engine
- internal ledger with
earned,available,settled - reserve / clawback logic
- employer controls and analytics
- employee payout UX
- reconciliation and ops workflows
Questions To Ask All Three
- Can one master program support segregated employer and employee balances?
- Is full employee onboarding required before any
Pixpayout? - How do refunds/devolutions work after funds were internally moved or paid out?
- Can reserves / held balances be modeled per employer?
- What webhook auth, retry, and ordering guarantees exist?
- What are the exact homologation steps and production SLAs?
- If we add
PaaS, can the same setup handle merchant onboarding and split settlement?
If you want, I can next turn this into either:
- a weighted vendor scorecard for your exact v1, or
- a diligence questionnaire to send
Celcoin,Z.ro, andDock.