Custom Banco Inter Pix integration

The challenge

The store needed to create Banco Inter charges and turn the bank's confirmation into an order update, with a clear payment screen for customers.

Accepting Pix in an online store involves more than displaying a payment key. The charge must match the order amount, the customer needs clear instructions, and the system must recognize when the bank confirms receipt. This project connected those steps in a dedicated Banco Inter module for Botble.

The work covered certificate-based communication, dynamic charge creation and a pending-payment page. The interface was refined around the QR code, a copyable payment code and order information. Technical identifiers support operations while the customer sees the information needed to complete payment.

How the workflow works

1. 01

   Prepare the order

   The integration receives order data, checks the currency and prepares the amount, reference and expiration. The implemented flow works with Brazilian reais.

2. 02

   Generate the Pix charge

   The server authenticates with the bank and requests a dynamic charge. The response supplies the QR code and the payment text that the customer can copy.

3. 03

   Follow payment progress

   The page checks status without a full reload. Polling intervals increase over time and automatic checking stops after a configured duration.

4. 04

   Confirm and update

   A bank query checks whether the charge has completed. Once payment is recognized, the integration updates the linked orders through the store's payment flow.

The work

A custom module combines authentication, charge creation, QR display, status checks and the Botble payment lifecycle.

• QR code and copyable Pix code
• Progressive polling with a time limit
• Linked payment and order updates

Status queries and webhooks serve different roles

The confirmation button queries the bank; clicking it does not mark an order as paid by itself. The API response determines the update. The code also provides a webhook handler that receives notifications and checks the corresponding payment state.

In the historical test, the bank created the charge and later returned a completed state during a query. That demonstrates this particular path through the integration. Automatic webhook delivery needs its own validation, including what happens after the customer closes the page.

A foundation for specific requirements

The module includes checks for orders already completed and configurable payment monitoring. Interface fixes also addressed display dependencies that could interrupt the page after a charge had already been created.

A new deployment requires checking the Botble version, account permissions, certificate setup and callback behavior. A quoted project can include interface changes, payment validation and operating documentation tailored to the customer's sales process.

Delivery and context

The project history records a charge created, paid and confirmed through a bank status query. Automatic webhook delivery remained a separate validation step.

Frequently asked questions