v2026.06Product Updates | June/2026
Here are the main new features and improvements at Pluggy in June 2026.
June highlights
- Transition to cursor pagination on the transactions endpoint for accounts created from June onwards, with the legacy endpoint (v1) being gradually discontinued.
- A more complete Open Finance, with new fields for investments (tax exemption, Anbima classification, brokerage note, Tesouro coupon), for credit cards (fee type and credit operation type), the counterparty ISPB code, reserved balances and the grace period date for fixed income.
- A more transparent Pix Automático, with debited account data, recipient bank, timestamps and reconciliation identifiers in the responses, plus fixes for retries and in the sandbox environment.
- Dashboard improvements, with a Customer ID filter in Payments and Portuguese as the default language for new accounts.
- Several stability fixes in connectors, credit card bills, Open Finance syncs, duplicated loans and in the Connect Widget.
26 changes · 1 breaking · 5 categories
Breaking changes and deprecations1
Deprecated
Transition to cursor pagination on the transactions endpoint
Accounts created from June 2026 onwards now use the transactions endpoint with cursor pagination by default. The legacy endpoint (v1) is being gradually discontinued for those accounts.
Accounts created before June 2026 are not affected at this time.
What to do: if your integration uses the legacy endpoint, migrate to the cursor-paginated one. The documentation and the guides already reflect the change, and the SDK has been updated to support it.
🚀 New Features7
New
Open Finance: new investment fields
New fields available for investments via Open Finance, including a tax exemption indicator (LCI/LCA/CRI/CRA), debtor data for CRI/CRA, remuneration frequency, price factor for variable income, Anbima fund classification, brokerage note number and coupon information for Tesouro Direto bonds.
New
Open Finance: new credit card fields
New categorization fields on credit cards, including detailed fee type, credit operation type, card network information when classified as "other", and the reason for a zeroed limit.
New
Open Finance: new counterparty code on transactions
Account transactions now return the ISPB code of the counterparty institution and an additional description for transactions classified as "other", improving categorization.
New
Open Finance: support for reserved balances
New
hasReservedBalance field and a dedicated endpoint to query blocked or reserved amounts in an account (e.g. court-ordered blocks, scheduled Pix), providing a more accurate view of the available balance.FixedOpen Finance:
Open Finance: gracePeriodDate field for fixed income
Fixed income investments (CDB, LCI, LCA, CRI, CRA, Debentures) now return the grace period date via Open Finance.
New
More specific error codes on the balance endpoint
The balance endpoint now returns more granular error codes, instead of grouping most failures under a generic error, making it easier for your integration to handle them.
New
clientUserId limit standardized
The maximum length of the
clientUserId field has been standardized at 500 characters across all API endpoints (Item, Connect Token and Investments), eliminating inconsistencies between the previous limits.💳 Payments5
Improved
Pix Automático: more complete payment responses
Pix Automático authorization and payment responses now include more information: debited account data, recipient bank, authorization and update timestamps, detailed error reason and identifiers for reconciliation (
consentId, transactionIdentification).Fixed
Pix Automático: fix to the retry logic
Fixed the recording of dates on failed retry attempts, which now reflect the date of each individual attempt instead of the original payment date. The system also now avoids new automatic scheduling when the institution returns a period limit exceeded error.
Fixed
Pix Automático: fixes in the sandbox environment
Fixed the 500 error when cancelling a schedule and the failure to generate a payment request from the dashboard, both in sandbox mode.
Fixed
Fix to the status of completed payments
Fixed an issue where an already completed payment could have its status overwritten with an error when a subsequent intent expired or was rejected.
🖥️ Dashboard2
Improved
Customer ID filter in Payments
The Payments > Customers section now lets you filter records directly by Customer ID, making it easier to find a specific customer's payments.
Improved
Portuguese as the default language
The default dashboard language when creating a new account is now Portuguese (pt-BR).
🐛 Fixes10
Fixed
Santander PJ connector: transaction deduplication fixed
Fixed a failure that incorrectly discarded distinct transactions that shared the same date, amount, description and balance, treating them wrongly as duplicates.
Fixed
Credit cards (Open Finance): improved partial sync
Bill fetching in partial syncs now correctly follows the transaction period, significantly increasing the share of transactions correctly associated with their bill.
Fixed
Reliability in Open Finance syncs
Fixed cases of false success in syncs that actually indicated instability, and merge errors (MERGE_ERROR) caused by transactions returned without a defined currency.
Fixed
Loan duplication fixed
Fixed the duplication of loans data on Open Finance connections, including the cleanup of existing duplicates.
Fixed
Bradesco PJ connector: user validation restored
Fixed the validation of unsupported users (USER_NOT_SUPPORTED), which had stopped working correctly.
Fixed
Bradesco connector: error messages with accents fixed
Fixed the encoding of special characters in error messages (e.g. invalid credentials), which displayed invalid characters to the end user.
Fixed
Connectivity restored on direct connectors
Connectivity restored on direct connectors that were blocked (Sicredi PJ and Bradesco PF).
Fixed
Connect Widget: connector type filter fixed
Fixed a bug where certain combinations of connector types passed to the widget did not display the expected connectors.
Fixed
Connect Widget: individual/business mode in payments
Fixed an issue where the widget did not correctly take into account the customer's account type (individual or business) when starting a payment flow, requiring a manual mode switch.
Fixed
Connect Widget: notification overlap fixed
Fixed an overlap between notification messages and the list of available accounts in the widget, which could make it harder to select the right account.
📚 Documentation1
Improved
.NET SDK: cursor pagination support
The .NET SDK has been updated to support cursor pagination, aligning it with the current capabilities of the API.