The method available today is PIX. The credit card is coming soon — the sections below about card tokenization apply once it launches.
The payment process on Bob
1
1. Identify the customer
Every payment is associated with a customer (name, document, contact). Bob stores this data to reuse it in future charges and generates an identifier used in the following steps.
2
2. Create the checkout session
The session connects the customer to the payment, stores the charge details, and loads the available methods (today PIX; card coming soon). Server-to-server integrations that use PIX directly via the API can skip this step and create the transaction directly.
3
3. Collect the payment
There are two ways to collect:
- Hosted checkout or Checkout SDK — Bob collects it securely: it shows PIX (QR Code and copy-and-paste) and, for card, tokenizes the data in the browser, generating a secure identifier (
pm_...). PAN, CVV, and expiry never pass through your application. - Direct API — you take on tokenization and PCI compliance, sending Bob only the secure token.
4
4. Create the transaction
The transaction is the payment itself — each charge attempt. It uses the customer and the data collected in the previous steps and receives a status that evolves until the final outcome.
Confirmation via webhook
The financial outcome is asynchronous. As soon as the transaction changes state (transaction.paid, transaction.expired), Bob sends a signed webhook to your backend — treat it as the official payment confirmation. The return page (successUrl) guides the buyer, but it does not replace the webhook.
Responsibilities
Next steps
Choose an integration
Compare the available paths.
Understand transactions
Learn about the resource that represents each payment attempt.
Customers
See how buyer data is stored and reused.
Webhooks
Implement asynchronous confirmation on your server.