Card transaction

Coming soon. Credit card payments are not yet available on Bob. This reference describes the structure the API will return once it launches — for now, use PIX.

To accept credit cards, you do not send the card data to the Bob API. The card number, CVV, and expiration date are collected and tokenized in the browser by Bob’s checkout package (@bobpayments/checkout-sdk) — your application and the API only receive a secure token.

Never send raw card data (PAN, CVV, or expiration date) to the Bob API. Use Bob’s JS checkout package to tokenize the card in the browser. See the Checkout SDK.

Structure

A credit card transaction is represented by the following structure:

{
  "id": "clx7a8b9c0d1e2f3g4h5",
  "externalId": "pedido_123",
  "amountCents": 25000,
  "product": "Assinatura Pro",
  "paymentMethod": "credit_card",
  "status": "paid",
  "card": {
    "brand": "visa",
    "last4": "4242"
  },
  "customerEmail": "[email protected]",
  "customerName": "João Silva",
  "customer": {
    "name": "João Silva",
    "email": "[email protected]",
    "document": "12345678900"
  },
  "createdAt": "2026-02-28T09:00:00.000Z",
  "updatedAt": "2026-02-28T09:00:00.000Z"
}

Attributes

string

Unique identifier of the transaction in CUID format.

string

Identifier of the transaction in your system. Use it to reconcile data without storing the internal id. Must be unique per project.

integer

Transaction amount in cents. Example: 25000 = R$ 250.00.

string

Name or description of the product/service being charged.

string

Payment method of the transaction. For card, the value is credit_card. Bob handles the processing of the attempt internally.

string

Current status of the transaction.

Status	Description
`pending`	Transaction created, still without final confirmation
`waiting_payment`	Awaiting 3DS authentication or asynchronous confirmation
`paid`	Payment approved
`failed`	Processing was not completed
`refunded`	The amount was refunded to the customer
`cancelled`	The transaction was cancelled

Do not treat the HTTP 201 alone as confirmation of payment — use a webhook and/or a status check to confirm the financial outcome.

object | null

Card display data, safe to store and show to the buyer. brand is the card brand and last4 are the last four digits. PAN, CVV, and expiration date are never returned — the card is tokenized in the browser by Bob’s checkout package.

string | null

Buyer’s email. A direct shortcut to the customer.email field, available at the root level of the transaction.

string | null

Buyer’s name. A direct shortcut to the customer.name field, available at the root level of the transaction.

object

Data of the buyer linked to the transaction. See the Customer entity.

date-time

Date and time when the transaction was created.

date-time

Date and time of the last update.

Next steps

Credit card

Integration modes, tokenization via SDK, and route configuration.

Checkout SDK

Tokenize the card in the browser without touching PAN or CVV.

Transactions

Checkout

Customers

Project

Sandbox

Structure

Attributes

Next steps

Credit card

Checkout SDK

​Structure

​Attributes

​Next steps

Credit card

Checkout SDK

Structure

Attributes

Next steps