Tamino

White-label payment gateway

Payment infrastructure to build your own financial ecosystem.

Integrate PIX, cards, boletos and multiple providers through a single infrastructure. Choose your partners, configure your rules and run everything under your own brand.

The differential

One API. Multiple providers.

Switch acquirers without rebuilding your integration. Your application's contract stays the same — what changes is what runs behind it.

Universal adapters

Cards, PIX and boletos behind the same domain contract.

Swap without rewriting

Adding or swapping a provider is configuration, not a new integration.

Your brand, your operation

End-to-end white-label — domain, checkout and emails.

Payment Orchestration

The transaction decides the path, not you manually.

Every transaction goes through a routing engine before reaching a provider — by cost, approval rate, priority or availability.

TRANSACTIONROUTING ENGINE
Provider AProvider BProvider C

Smart Routing

Rules that decide in real time.

Cost Optimization

Routes to the lowest-cost provider for each transaction.

Approval Rate

Prioritizes whoever is approving the most at that moment.

Automatic Failover

If a provider fails, the next attempt goes to another.

Provider Priority

Set the preferred order by method or card brand.

Transaction Rules

Rules by amount, brand, BIN or availability.

Load Balancing

Distribute volume across providers by configurable weight.

Checkout

A checkout that looks like yours. Because it is.

Logo, colors, domain, fields, methods, and installments — your buyer never sees the name Tamino, only your own brand.

See White-Label Checkout
admin.tamino.com.br/dashboard

94,2%

Approval rate

1.284

Cards (24h)

3.017

PIX (24h)

412

Boletos (24h)

Active providers

Acquirer AAcquirer BPIX PSP APIX PSP B

Example data — does not reflect real operations.

Tracking and Marketing

Meta Pixel, GA4 and GTM without duplicating conversions.

Client-side and server-side dispatch with deduplication (Pixel + Conversions API), respecting visitor consent.

Fan-out, not pick-one

Several tracking destinations active at once, no extra code.

Consent (LGPD)

Events only fire with recorded consent.

Deduplication

Pixel and Conversions API never count the same conversion twice.

Multi-Tenant

Every tenant, an independent operation.

Brand, active providers and checkout configured per tenant — on the same platform, with no interference between operations.

PLATFORM
Tenant A
Brand
Providers
Checkout
Tenant B
Brand
Providers
Checkout
Tenant C
Brand
Providers
Checkout

API First

One POST. One payment.

Request
POST /v1/payments

{
  "amount": 15000,
  "currency": "BRL",
  "method": "pix"
}
Response
200 OK

{
  "id": "pay_xxxxxxxxx",
  "status": "pending"
}

Webhooks

Signed events, in real time.

payment.createdpayment.processingpayment.approvedpayment.failedpayment.refundedpix.receivedboleto.paidchargeback.created

Architecture

From the customer to the bank, step by step.

CUSTOMER
CHECKOUT / API
hosted, embedded or transparent
PAYMENT GATEWAY
Tamino
PAYMENT ORCHESTRATOR
smart routing, automatic failover
PIX
CARD
BOLETO
PSP
ACQUIRER
BANK
BaaS

Developer Experience

Built for teams who actually integrate.

REST APIWebhooksSDK-readySandboxAPI KeysLogsIdempotency KeysPostman Collection

Integration flow

From sandbox to settlement, the same flow.

01

Connect

A sandbox API key is already enough to see the first payment captured.

02

Configure

Activate the providers that fit your business and set your brand.

03

Route

Routing and failover rules between providers, no extra code.

04

Reconcile

Webhook, statement and receivables already reconciled end to end.

Ready to build your payments ecosystem?

Talk to a specialist and set up a sandbox with the right providers for your business.

Talk to us

Tell us about your operation.