API-first payments

Build payments on top of the Bunne REST API.

A public, tenant-scoped API for tokenizing cards, creating charges, capturing authorized payments and receiving signed webhooks. Built for developers first, with canonical contracts for humans, tools and AI agents.

Explore API Reference OpenAPI 3.1 LLMs.txt

Base URL

Production

https://bunne.com.br/api/v1

What changed

Public payments are Charge-first. There are no public PaymentIntent routes pre-GA. Use POST /charges to charge now or authorize, and POST /charges/:id/capture to capture.

Quickstart

Charge flow

For cards, tokenize first. Then create a charge. For manual capture, capture the authorized charge when the order is ready.

1. Tokenize card

curl -X POST https://bunne.com.br/api/v1/payment-methods/tokenize \  -H "Authorization: Bearer sk_test_xxx" \  -H "Content-Type: application/json" \  -d '{    "card": {      "number": "4242 4242 4242 4242",      "exp_month": 12,      "exp_year": 2030,      "cvv": "123",      "holder_name": "Ada Lovelace"    }  }'

2. Authorize charge

curl -X POST https://bunne.com.br/api/v1/charges \  -H "Authorization: Bearer sk_test_xxx" \  -H "Idempotency-Key: order_123_charge" \  -H "Content-Type: application/json" \  -d '{    "amount": 10990,    "currency": "BRL",    "payment_method": "CREDIT_CARD",    "capture_method": "manual",    "card_token": "tok_xxx"  }'

3. Capture later

curl -X POST https://bunne.com.br/api/v1/charges/ch_xxx/capture \  -H "Authorization: Bearer sk_test_xxx" \  -H "Idempotency-Key: order_123_capture"

API Reference

Implemented endpoints

GET/health

Healthcheck

Returns the public API health envelope.

POST/payment-methods/tokenize

Tokenize payment method

Exchanges raw card data for a `tok_` token. This is the only public endpoint that accepts PAN/CVV. Requires a seller-scoped API key with approved seller KYC.

POST/charges