Skip to navigation

v2.125.0 — Cards in the daily balance and locked balance on account close

  • The daily balance shows card settlement. Each day of GET /v1/accounts/{accountId}/daily-balance carries cardSettlementIn (debit, credit and receivables prepayment inflows) and cardSettlementOut (outflows). Both are always present, 0 when there is no movement. With them, a day’s opening balance matches the previous day’s opening plus inflows, minus outflows and fees.
  • Account close tells a locked balance apart. On POST /v1/accounts/{accountId}/close, when the account is yours alone, the settlement bank only closes a zeroed account: no available balance and no locked balance. An available balance still returns 422 account_has_balance. A zero available balance with a locked balance (for example a MED hold) now returns 422 account_has_locked_balance. In both cases the account stays active and the body carries the settlement-bank balance.
  • Documentation. The reference for GET /v1/accounts/{accountId}/pix/transactions now describes what the route has always returned: the statement envelope (items[], AccountStatement schema) with 0 or 1 item, and 200 with items: [] when the transaction does not exist. If you generated a client from the old schema (transactionId, type, transactionDate), regenerate it. The GET /balance reference now states that includeLocks has no effect. The new Balance, daily balance and account close guide brings the three routes together.

v2.126.0 — Due-date QR Code and Pix Location

  • Due-date QR Code. POST /v1/accounts/{accountId}/pix/qr-code/due-date issues a Pix charge with a due day, a debtor and, optionally, deduction, discount, interest and penalty. The QR accepts payment until the end of dueDate + daysAfterDueDate (Brasília), at most 365 days ahead. See the guide.
  • Pix Location. POST /v1/accounts/{accountId}/pix/qr-code/location generates the QR blocked (status: BLOCKED), ready to be printed. PUT /v1/accounts/{accountId}/pix/qr-code/location/{identifier}/confirm sets amount, due date and debtor and releases payment. If confirmation is refused, the error carries details.qrStatus: BLOCKED and the QR stays blocked. See the guide.
  • Both products are enabled per tenant. Without it, the routes return 403 feature_disabled. They use the qrcode.manage scope and the dynamic QR policy rules.
  • Lookup, cancellation and webhooks keep their routes. The lookup returns the due-date fields (dueDate, daysAfterDueDate, charges, finalValue, debtor, receiverName) and, for Location, locationId. In qrcode.paid, qrcode.expired and qrcode.cancelled, data.type may be due-date or location, and qrcode.paid data.amount is the amount actually paid.
  • Two new timeline events: qrcode.location_generated and qrcode.location_confirm_failed.

v2.127.0 — Pix Automático

  • Pix Automático: recurring charges authorized once by the payer. New routes under /v1/accounts/{accountId}/pix/automatic to request the recurrence authorization, issue a composite QR (immediate or with due date), schedule each charge, postpone, query retry dates and request a retry. Guides in Pix Automático.
  • Off until CorpX enables it. The automatic_pix feature starts disabled for every tenant; while off, the routes return 403 feature_disabled. New credential scope: pix.automatic. Scheduling and retries are financial operations and only accept an M2M credential.
  • Ten new webhooks. pix.automatic.recurrence.authorized, .rejected, .expired, .failed; pix.automatic.scheduling.confirmed, .rejected, .failed; pix.automatic.settlement.completed, .failed; and pix.automatic.qrcode.paid. Settlement and composite QR payment also emit pix.in.completed. Payloads in Webhooks.
  • Timeline per recurrence. GET /v1/transactions/{recurrenceId}/timeline returns the pix_automatic.* events of the recurrence, its schedulings and settlements.
  • New error codes. automatic_pix_* for blocked contract, ineligible receiver, unavailable payer bank, recurrence not authorized, date out of window, scheduling conflict, retry not allowed, amount above the payer limit, amount mismatch and repeated QR identifier.

v2.128.1 — boleto beneficiary webhooks

  • Four new events track the boleto beneficiary. boleto.charge.beneficiary.approved (registration accepted or relationship reactivated), boleto.charge.beneficiary.rejected (operation rejected, with rejectionCode and rejectionReason), boleto.charge.beneficiary.updated (data or eligibility changed) and boleto.charge.beneficiary.closed (relationship closed). operationId matches the one in the operation’s 202 response. Subscribe with POST /v1/webhooks or list them with GET /v1/webhooks/events. See Webhooks.
  • GET /v1/accounts/{accountId}/boleto/charge/beneficiary returns lastEvent. The field repeats the settlement bank’s latest notice. On 404, the notice comes in details.lastEvent, so a rejected registration shows up even with no beneficiary created.
  • Issuance does not redo a rejected registration for 24 hours. If the settlement bank rejected the beneficiary registration in the last 24 hours, issuance (single or batch dispatch) returns 502 boleto_charge_beneficiary_registration_failed with the reason, details.lastEvent and a Retry-After header with the seconds left, and sends no new registration. After fixing the account data, register again with POST /v1/accounts/{accountId}/boleto/charge/beneficiary: that endpoint does not wait. A pending beneficiary without a recent rejection still gets the usual 202.
  • A paid issued boleto updates the charge sooner. The settlement bank’s settlement notice triggers a fresh read of the charge. Payment events are unchanged.

v2.129.0 — balance holds and P2P Crypto

  • Balance holds. POST /v1/accounts/{accountId}/holds locks part of the balance at the banking provider; the hold is released to another CorpX account (with an optional fee to a third one) or cancelled. GET /balance gains heldAmount. GET .../holds?status=held lists only what still locks balance, and the sum matches heldAmount. Events account.hold.created, account.hold.released and account.hold.cancelled. See Balance holds.
  • P2P Crypto. A stablecoin market in a single CorpX book: accounts of every tenant with the feature on advertise and take ads from each other, with global rules and an anonymous counterparty. Includes ads, orders, a hold on the buyer’s amount, a contract signed by both parties, txid checking on chain, release with PIN and disputes decided by CorpX. The p2p_crypto feature starts disabled for every tenant. See P2P Crypto.
  • The advertiser pays the intermediation fee. On a sell ad it is charged to the seller right after the payment; on a buy ad it is part of the buyer’s hold. See Money and fee.
  • Orders with timeline and receipt. GET .../p2p/orders/{orderId} returns timeline, deadlineAt, concluded and concludedAt. GET .../p2p/orders/{orderId}/receipt returns the receipt of a concluded trade, the only place where the parties are identified (masked document).
  • Statement and webhooks recognize the order. Transfers with identifier p2p-{orderId}, fee-p2p-{orderId} and fee-p2p-{orderId}-r show as COMPRA P2P CRIPTO, VENDA P2P CRIPTO, TAXA INTERMEDIAÇÃO KYC P2P CRIPTO or ESTORNO TAXA INTERMEDIAÇÃO KYC P2P CRIPTO, with partnerType: P2P_CRYPTO_ORDER, p2pOrderId, p2pKind, p2pOrder and counterparty ORDEM P2P CRIPTO. The line detail returns p2pNegotiation. Order holds return source. See Statement and balance.
  • Reserved prefixes. An identifier starting with fee- or p2p- is refused with 400 invalid_identifier on internal transfers, PIX and charges.