Skip to navigation

v2.141.0 — Daily and monthly QR code creation quota

  • The qrCode policy section gains maxIssuesPerDay and maxIssuesPerMonth. When set, QR creation (static, dynamic and due-date) is refused with 422 policy_denied and rule qrCode.maxIssuesPerDay or qrCode.maxIssuesPerMonth as soon as the account reaches that many QR codes created in the Brasília calendar day or month. The quota is per account — set on the tenant, each account gets its own — and counts every QR created in the window, in any status: cancelling does not free the slot. Without the two keys nothing changes. Automatic PIX QR codes are not counted. Details in Policies and Rules.

v2.142.0 — MED rate in the policy: account block and critical MEDs

  • New med policy section. When a new dispute (MED) is received against the account, the MED rate of the rolling window — MEDs received over PIX successfully received, per account, windowDays backwards (default 30, cap 90) — is compared with maxRatePercent. Rate at the ceiling and at least minMedCount MEDs in the window block the account’s outbound side (423 account_blocked on every debit until support reactivates it). The MED follows the normal flow.
  • Critical MEDs, with their own ceiling. med.critical has the same shape (maxRatePercent, minMedCount) and counts only disputes whose settlement-partner reason is scam-or-fraud or whose claimant message carries scam or betting terms from a list maintained by CorpX, the same for every account. Meant for limits lower than the general rate.
  • policy.violation with phase: "med". Action BLOCK_ACCOUNT, accountBlocked, the dispute’s medId and the window numbers (windowDays, medCount, criticalMedCount, pixInCount, ratePercent, criticalRatePercent). The pix.med.opened for the same dispute goes out with accountBlocked: true. Rules med.maxRatePercent and med.critical.maxRatePercent. Without the section nothing changes. Details in Policies and Rules.

v2.145.0 — Expediting the grace period of a new credential IP

  • A new IP on a credential’s allowlist can be released before the 18h. As with credential activation, CorpX ends the grace period at the holder’s request, with a ticket and the approval of an administrator other than the person who asked. The pending IPs apply right away: pendingIps is gone and they move into ips. Neither the credential nor the master that issued it can expedite through the API; adding an IP still waits 18h and removing one is still immediate. Details in Keys and IPs.

v2.146.0 — Dedicated code for a source account without a PIX key

  • New code payer_key_required (422). When the paying account has no active PIX key, an outgoing PIX now fails with payer_key_required instead of key_inactive. The old message told the payer to check the recipient’s key, but the one who has to act is the source account holder: register a key on the account (a random key works) and send again. key_inactive still covers a recipient key that is inactive or under portability. Details in Errors.