# Stark Bank

**Canonical:** https://apis.io/providers/stark-bank/  
**Website:** https://www.starkbank.com  
**APIs profiled:** 31

Stark Bank is a regulated Brazilian financial institution (authorized by the Banco Central do Brasil, not a payment service provider) that exposes end-to-end money movement through a single RESTful JSON API. Businesses collect money with Pix Invoices, Pix QR codes, Pix subscriptions, Boletos, card payments and marketplace split receivables, and pay out with Pix/TED Transfers, Boleto, BR Code, utility, tax and DARF payments plus approval-gated Payment Requests. Received funds land directly in the account balance with no wallet or payout step. The v2 OpenAPI 3.1 API (143 operations) authenticates with ECDSA request signing rather than API keys or OAuth, offers a production-identical sandbox, cursor pagination, externalId idempotency and signed webhook events, and ships nine official SDKs (Python, Node, Go, Java, Ruby, PHP, .NET, Elixir, Clojure).

## Kin Score — 50.8 / 100 (developing)

Scored 2026-08-17 under rubric 0.11.0. Trend: flat (+0.0 from 50.8).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 71.7 |
| Governance | 20.8 |
| Operational Transparency | 28.9 |
| Developer Ergonomics | 73.4 |
| Commercial Clarity | 39.5 |

Regulatory layer — **Banking & Open Finance**: 27.8 (matched via tags).

## Agent readiness — 48.9 (agent-native)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | no |
| MCP Server | derived |
| Auth Clarity | yes |
| Idempotency | documented |
| Error Semantics | verified |
| OpenAPI Examples | partial |
| Rate Limit Signal | no |
| Event Surface Described | yes |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Self-serve signup — onboarding: self-serve, pricing: unknown, trial: no (confidence: medium).

## APIs (31)

- **Stark Bank Balance API** — The balance entity holds the total funds available in your workspace and can be calculated as the sum of its transactions (cash-in + cash-out). Therefore, you can also interpret...
- **Stark Bank Boleto API** — A boleto is a method you can use to charge your customers or load your Stark Bank account. Here we will teach you how to create and manage boletos. You can also split a Boleto b...
- **Stark Bank Boleto Holmes API** — Honoring the famous Sherlock Holmes, this feature allows your application to investigate updated boleto status according to CIP in less than an hour. Here we will teach you how ...
- **Stark Bank Boleto Payment API** — Here we will teach you how to create and manage boleto payments.
- **Stark Bank Brcode Payment API** — Here we will teach you how to create and manage brcode payments.
- **Stark Bank Darf Payment API** — Here we will explain how to manually pay DARFs without bar codes.
- **Stark Bank Deposit API** — Deposits represent passive cash-ins received by your account from external transfers or payments. In this section, we will teach you how to manage your Deposits.
- **Stark Bank Dynamic Brcode API** — Note:This is a basic Pix QR Code solution for one time payment. For a complete Pix QR Code receivable, check the Invoice resource. When a Dynamic Brcode is paid, a Deposit is cr...
- **Stark Bank Event API** — Every time a log is created, a corresponding event will be generated and sent to you by webhook, if the appropriate subscription was set. Therefore, the event represents an occu...
- **Stark Bank Event Attempt API** — When an Event delivery fails, an event attempt will be registered. It carries information meant to help you debug event reception issues.
- **Stark Bank Institutions API** — An Institution is used to query institutions registered by the Brazilian Central Bank for Pix and Ted transactions.
- **Stark Bank Invoice API** — The Invoice resource is used to request payments from customers. Your customer can pay it by scanning the Pix QR Code or making a deposit to the indicated account number. You ca...
- **Stark Bank Invoice Pull Request API** — An Invoice Pull Request is a command sent to the payer's bank to trigger the automatic debit of a previously issued invoice linked to an active Invoice Pull Subscription. It con...
- **Stark Bank Invoice Pull Subscription API** — An Invoice Pull Subscription is a recurring payment agreement between a payer and a receiver, authorized through the Pix Automatic infrastructure. Once active, it allows the rec...
- **Stark Bank Merchant Card API** — The Merchant Card resource stores information about cards used in approved purchases. These cards can be used in new purchases without the need to create a new session.
- **Stark Bank Merchant Installment API** — Merchant Installments are created for every installment in a purchase. These resources will track its own due payment date and settlement lifecycle.
- **Stark Bank Merchant Purchase API** — The Merchant Purchase resource can be used to charge customers with credit or debit cards. If a card hasn't been used before, a Merchant Session Purchase must be created and app...
- **Stark Bank Merchant Session API** — The Merchant Session resource can be created by a merchant and used by the card holder in order to collect their card data without having to handle it on the merchant's side. Th...
- **Stark Bank Payment Preview API** — A Payment Preview is used to get information from multiple types of payment to confirm any information before actually paying. If the 'scheduled' parameter is not informed, toda...
- **Stark Bank Payment Request API** — Here we will teach you how to create and manage your payment requests. The payment request is the main element of our approval flow, which can be checked out by logging into our...
- **Stark Bank Pix Key API** — The Pix keys are saved in the DICT (Diretório de Identificadores de Contas Transacionais), the centralized Pix service managed by Bacen (Brazilian Central Bank) that allows you ...
- **Stark Bank Public Key API** — Some of our responses will be signed using our own private key, such as the messages we send by webhook. In order to verify that it was really us that generated the message, you...
- **Stark Bank Split API** — The Split resource is used to split an Invoice or Boleto between different receivers.
- **Stark Bank Split Profile API** — The Split Profile resource is used to configure the behavior of split operations.
- **Stark Bank Split Receiver API** — You can create a Receiver to an Invoice or Boleto split by using the Split Receiver resource.
- **Stark Bank Tax Payment API** — Here we will explain how to create and manage tax payments, such as ISS and DAS.
- **Stark Bank Transaction API** — Since Stark Bank is centralized, we have a private ledger to keep track of all transactions. It's important to understand that every financial operation in Stark Bank generates ...
- **Stark Bank Transfer API** — Transfers are used to send money to any bank account in Brazil using the Ted or Pix systems. Here we will show you how to create and manage them.
- **Stark Bank Utility Payment API** — Here we will teach you how to create and manage utility payments, such as electricity and water bills.
- **Stark Bank Webhook API** — You can create webhook subscriptions to receive events whenever a new log is created. We send the event by making a POST request to your endpoint URL. The event will be delivere...
- **Stark Bank Workspace API** — Workspaces are bank accounts. They have independent balances, statements, operations and permissions. The only property that is shared between your workspaces is the link they h...

## MCP servers (1)

- **stark-bank-mcp.yml**

## Security (3)

- **Stark Bank Authentication** — digitalSignature · 1 scheme
- **Stark Bank Domain Security** — TLSv1.3 · HSTS · DMARC
- **Stark Bank Trust Center** — PCI DSS 4.0.1, SOC 2, ISO 27001, Bacen Pix Grade A

## Tags

Company, Fintech, Banking, Payments, Pix, Boleto, Banking as a Service, Brazil, Financial Services

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/stark-bank/). Scores are computed from the provider's own public artifacts under a published rubric.