Woovi Pix with order reconciliation

The challenge

The store needed Pix payments with clear environment settings and local payment records consistent with the provider's charge.

A single checkout can produce more than one order in the platform. This module organizes one Pix charge for that group while retaining payment records linked to each order. Its technical purpose is to reconcile receipt without losing the relationship to local amounts.

The UP implementation uses its own namespace and documented rules. It includes charge creation, QR and copyable payment codes, expiration, a configurable discount and separate production and test screens. The history records a test deployment and automated checks, without establishing a complete live financial operation.

How the workflow works

1. 01

   Calculate the purchase

   The store groups the orders and calculates the total in cents. When enabled, the Pix discount applies to products after existing discounts, leaving shipping and fees outside that discount.

2. 02

   Create or recover

   A stable reference identifies the charge. The module uses a local lock and existing-charge recovery to handle repeated attempts or delayed responses.

3. 03

   Present the Pix payment

   The page displays the QR code, payment text and expiration. While visible, it follows local status and uses controls intended to prevent payment-page caching and indexing.

4. 04

   Verify receipt

   A validated webhook or manual check queries the API. The module compares environment, reference, transaction and amount before accepting a state change.

5. 05

   Reconcile the orders

   The group's native payment records are updated according to transition rules, with checks for completed states and links to the expected orders.

The work

A UP module creates or recovers a charge, presents the Pix payment and checks its reference, transaction and amount before updating orders.

• Separate production and test settings
• Stable references for charge recovery
• Validated webhooks and API queries

Separate environments for clearer configuration

Production and test administration screens have their own credentials, webhook settings, discount and expiration. Opening one screen does not independently change the checkout's active environment. This makes the configuration being edited explicit.

The Pix page also distinguishes local monitoring from provider queries. The browser can follow status without requesting a new charge on every check. Webhooks and manual refresh have defined roles in checking the remote payment.

Tested rules with documented limits

Webhook validation includes a token and signature, followed by an authenticated charge query. The module does not simply accept the amount stated in a notification: it compares the service response with the order group stored by the shop.

The 98 recorded checks are isolated tests using simulated responses and an in-memory database. They are not real transactions and do not replace complete flow validation. A new deployment should check payment, expiration, redelivery and the platform's order effects.

Delivery and context

Version 1.1.0 was deployed to a test store, with 98 isolated checks recorded as passing in the project history.

Frequently asked questions