Skip to navigation

v2.152.0 — Admin: replace scopes on a master without rotating the secret

  • New route: POST /v1/admin/tenants/{tenantId}/credentials/{clientId}/scopes (admin_super only, with ticket, reason, and a requester other than the approver). Replaces the scope set of an active master: adds what is missing (e.g. credentials.delegate) or swaps a legacy api2/write master for the granular set. Refuses scope reduction on a granular master, refuses changes that would alter the Cognito OAuth pair, and writes an admin_audit_log trail. Unlocks delegated credential issuance by internet banking without rotating the clientSecret.

v2.150.0 — P2P requires a confirmed e-mail and phone on the profile

  • The P2P profile now has its own contact, confirmed by code. PUT /v1/accounts/{id}/p2p/profile/contact stores email and phone (plus representativeName on a business account) and sends a code to each channel not yet confirmed. POST .../p2p/profile/contact/confirm with channel (email or phone) and code confirms the channel; POST .../p2p/profile/contact/codes resends the code. The profile GET returns contact with masked destinations, emailVerified, phoneVerified and ready.
  • The CPF of whoever signs the contract is not sent in the body. On an individual account it is the account document. On a business account it is the holder given in X-Acting-Document; if another holder stores the contact, both confirmations reset. Changing the e-mail or the phone resets that channel’s confirmation.
  • Without both channels confirmed, the account cannot trade. Opening an order returns 422 p2p_contact_unverified; so do creating or reactivating an ad and requesting advertiser status. Ads from profiles that have not confirmed leave the book, and an order on one returns 409 ad_unavailable. Orders already open carry on as usual (release and cancel do not require the contact).
  • Profiles that already advertise must confirm their contact to return to the book. The contact was not copied from the accreditation record.
  • New codes: p2p_contact_unverified, contact_code_invalid, contact_code_locked, contact_code_rate_limited (429), contact_delivery_failed (503) and contact_already_verified (409). A code is valid for 10 minutes, with up to 5 attempts and up to 5 sends every 15 minutes.

v2.151.0 — P2P: ad range in crypto, tenant-attested contact and username cooldown

  • An ad’s per-order range can be in crypto. limitsUnit: asset with minAssetAmount and maxAssetAmount on creation or PATCH; opening an order compares the crypto amount. minAmount/maxAmount stay in the response, in BRL at the shown price, so they move with the price. Without limitsUnit nothing changes (brl). Sending the other unit’s fields is 400 invalid_payload; switching units requires the full range in the new unit. Changing the range or the price of a crypto-range ad without a Binance quote returns 409 price_unavailable.
  • The tenant can attest a contact it already verified. PUT .../p2p/profile/contact accepts emailVerified and phoneVerified: an attested channel is stored confirmed, with no code. The profile contact shows the source in emailVerifiedBy/phoneVerifiedBy (otp or tenant).
  • The username changes at most once every 90 days. Creating the profile does not count. A second change within the cooldown returns 409 username_change_too_soon with details.nextChangeAt. The profile returns usernameChangedAt and usernameNextChangeAt.
  • New route: GET /v1/accounts/{id}/p2p/usernames/{username}/availability returns { username, available } without saying who holds a taken username.

v2.147.0 — Advertiser fee on the P2P profile

  • New feeBps field on the P2P profile. GET /v1/accounts/{accountId}/p2p/profile (and the responses of the profile PUT and the advertiser request) now include the fee, in basis points of the order amount, that the account pays on the orders of its own ads: on a sell ad the seller receives the amount minus the fee; on a buy ad the buyer pays the amount plus the fee. It comes from the level; without a level, the lowest level’s fee applies, as when the order opens. Use it to preview the net amount before publishing the ad.

v2.148.0 — P2P price from Binance only, locked live with evidence

  • Behavior change: the P2P market quote is now exclusively the Binance spot price (GET /api/v3/ticker/price?symbol={ASSET}BRL), read live. There is no more source aggregation, no quote stored every minute and no age rule. GET /v1/p2p/pairs gains spotSource: "binance"; spotAvailable now means “Binance answered this request” (cached up to 2 s). The price on the list and on the ad is indicative.
  • The order locks its price with a live Binance read at opening, also for fixed-price ads (there the spot is recorded as the market at that moment). If Binance does not answer, POST .../p2p/orders refuses with 409 price_unavailable and nothing is created or locked; retry with the same Idempotency-Key. Replaying an existing order does not query Binance.
  • New route GET /v1/accounts/{accountId}/p2p/orders/{orderId}/price-evidence: the whole query that locked the price (request, response with every header and the raw body, TLS and certificate chain, timestamps, hashes), written in the same transaction as the order and available to both parties from opening. verified recomputes the hash on read. Orders older than this version answer 404 price_evidence_not_found.
  • New offset price mode on ads: priceMode: "offset" with offsetCents (signed BRL cents per unit added to the Binance spot: -1 buys at R0.01below,‘1‘sellsatR 0.01 below, `1` sells at R 0.01 above). Capped at 5% of the current spot (422 invalid_offset); publishing the ad or changing offsetCents without a quote answers 409 price_unavailable. Editing stock, limits or deadline neither calls Binance nor re-checks the cap. The fee stays in bps of the order amount in every mode. The priceMode enum in the contract now reads spread | fixed | offset; the floating value the spec showed was never accepted.
  • Contract: the copies now carry cotacao_binance, cotacao_horario and cotacao_evidencia_sha256. The Dracma templates must be re-registered for the fields to show in the PDF; until then the rest of the contract is unchanged.

v2.149.0 — P2P unit price has 4 decimals; the fee rounds up

  • The P2P unit price now has 4 decimal places (5.4321). That covers the Binance spot on GET /v1/p2p/pairs, the ad price, the price locked on the order, spotPrice and orderPrice on the evidence, and the contract fields preco_unitario and cotacao_binance. Stored prices do not change value: the migration only appends two zeros.
  • Only BRL money becomes cents, and only when the order opens. The order amount (crypto × price) truncates to the cent. The fee (feeBps of the level, on the amount) rounds to the cent up: a fraction of a cent never drops to zero.
  • offset replaces offsetCents on the ad. It is a signed decimal with up to 4 places ("-0.0100", "0.0001"), under the same 5% of spot cap. The integer offsetCents is still accepted on the request (1 cent becomes 0.0100) and is no longer returned. fixedPrice also takes 4 decimal places.

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.

v2.136.0 — P2P market parameters in GET /v1/p2p/settings

  • New route GET /v1/p2p/settings. Read-only, it returns what a customer needs before the first order: signing deadline (signingDeadlineMin), delivery deadline range (deliveryMinMin, deliveryMaxMin), release deadline (releaseDeadlineH), new-wallet grace (walletChangeGraceH), the per-order and daily caps that apply to the tenant (orderCap, dailyCap, the lower of market and tenant, null when there is none), the advertiser fee range across levels (feeBpsMin, feeBpsMax, null without levels) and the enabled pairs. Same scopes and same feature_disabled gate as GET /v1/p2p/pairs. See Getting started.

v2.137.0 — 60- and 90-day windows for DICT lookups

  • DICT lookups get 60- and 90-day windows. The policy’s dictLookup.windows section accepts 60d and 90d, on top of the existing windows. Anyone who declares no values inherits the fleet baseline, revised in this version. The values are in Policies.

v2.138.0 — ted.in.received carries the receiving account

  • ted.in.received now includes data.payee. The account that received the TED, as the settlement bank identifies it: bank 681 / ISPB 50871921, branch, account and holder (name and document). Until now the event only carried the payer. Additive field; schemaVersion stays 1.0. Examples in TED and Webhooks.

v2.139.0 — ted.in.received with the payer's bank, branch and account

  • data.payer in ted.in.received is now complete. Besides name and document, the event carries the originator’s bankCode, bankIspb, bankName, branch and account, taken from the settlement bank’s statement at notification time. In the rare case the line is not there yet, the event goes out as before, with name and document only. Additive fields; schemaVersion stays 1.0. Example in Webhooks.

v2.131.0 — P2P ad detail

  • GET /v1/p2p/ads/{adId} returns one ad of the book. The fields are those of a GET /v1/p2p/ads item, plus the pair’s network, asset and decimals. The open-order screen can load the ad from a direct link or after a reload. An inactive ad, or one that left the book, returns 404 ad_not_found. The advertiser’s wallet and tenant are not returned: to open the order, send the customer’s walletId on the pair’s network. See Internet banking guide.

v2.131.1 — P2P PIN only for the buyer

  • Opening a P2P order asks for the PIN and goes through the cashout locks only when the opener buys (takes a sell ad), because that is whose balance is held. Taking a buy ad means selling: nothing leaves that account, and the order opens without X-Transaction-Pin. Releasing still asks for the buyer’s PIN. See P2P Crypto.

v2.134.0 — P2P buy ads follow the advertiser's cashout locks

  • A buy ad only takes orders when the advertiser could pay. On a buy ad, the order amount is held from the advertiser’s account. With cashoutBlocked on, the account’s active buy ads are paused (pausedReason: cashout_locked), and creating or turning one back on answers 423 cashout_locked. Outside cashoutHours, the ad leaves GET /v1/p2p/ads and the detail (404 ad_not_found), and opening an order on it answers 409 ad_unavailable, until the window opens. In the owner’s list, the hidden ad has hiddenReason. Sell ads do not change. See Ads.

v2.135.0 — Account holder details, account closing and contestation

  • Person holder address on PUT /v1/accounts/{accountId}/holder/address, with X-Acting-Document equal to the account CPF. A company uses a request with proof (holder-updates). See Account holder details.
  • Closing the account on the exclusive path also refuses while a PIX key remains: 422 account_has_pix_keys, with only the key type.
  • Contesting a sent PIX on POST /v1/accounts/{accountId}/pix/med-requests, with a MED-YYYY-NNNNNN code. Opening it at the settlement bank is still done by the desk. See Contesting a sent PIX.

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.