v2026.10Product Updates | October/2026
Check out Pluggy's main news and improvements for October 2026.
October highlights
- Heads up: the first Pix Automático payment can no longer fall on the same day as the
startDate, and the client secret is now shown only once. - New Open Finance connector: Azimut, for individuals.
- PIX by biometrics (Journey Without Redirect): the payer links their account once and confirms the following payments with biometrics, without going to the bank.
- Source account balance in Smart Transfers and in PIX by biometrics, with the Optimized Journey.
- Scheduled payments from checking accounts via Open Finance, starting with Itaú, and a richer real-time balance in
GET /accounts/{id}/balance. - More visibility into your integration: request Logs and metrics in the Dashboard, the execution explorer, and new tools in the Pluggy MCP.
22 changes · 3 breaking · 6 categories
Breaking changes and deprecations3
Deprecated
Pix Automático: the first payment cannot fall on the same day as the startDate
Since 10/23, POST /payments/requests/automatic-pix returns 400 AUTOMATIC_PIX_INVALID_FIRST_PAYMENT_DATE when the firstPayment date equals the startDate. If firstPayment has no date, it is settled on the day of authorization, and in that case the startDate cannot be today. The same validation runs on POST /payments/intents: requests already created in this format get the error there and must be recreated. This is an Open Finance rule: the recurrence only starts after the enrollment payment.
If you don't send firstPayment, you are not affected, and consents that are already authorized keep working.
What to do: send a startDate at least one day after the first payment (for example, charge the enrollment today and start the monthly recurrence one month from now).
Deprecated
Client secret shown only once
An application's client secret is now shown only at the moment it is generated: when the application is created or when you click "Generate new secret". After that, it can no longer be viewed in the Dashboard.
Integrations that already use the secret keep working normally.
What to do: store the secret in a secure vault as soon as it is shown. If it is lost, generate a new one in the Dashboard.
Deprecated
Reminder — announced in June: transition to cursor pagination on the transactions endpoint
Accounts created from June 2026 onward already use the cursor-paginated endpoint by default, and the legacy endpoint (v1) will be discontinued for those accounts in December 2026, one month from now.
What to do: migrate to the cursor-paginated endpoint. Accounts created before June 2026 remain unaffected, and we will give advance notice before any change for them.
📡 New Connectors1
New
Azimut (Open Finance)
New Open Finance connector for individuals (
connectorId 805), with accounts, transactions, credit cards, investments, loans and identity data.connector 805open finance
💳 Payments3
New
PIX by biometrics (Journey Without Redirect)
You can now charge with PIX by biometrics. You create the request and send the
paymentUrl to the payer. On the first payment, they choose the bank, approve the link and create a passkey at pay.pluggy.ai. On the following payments, on the same device, they confirm with biometrics, without being redirected to the bank's app. The API lets you create the charge, query the links and receive webhooks when a link is authorized, revoked or not completed. It is also available in the Node, Java and .NET SDKs and in the Dashboard, under Payments → Requests (new PIX by biometrics type) and Payments → Linked accounts. This is a first version, still without sandbox: to test it, use a real R$ 0.01 payment from an account different from the recipient's. For now the journey works only through Pluggy's payment page. Guides at docs.pluggy.ai, under Payments → PIX by biometrics.payments
Improved
Source account balance with the Optimized Journey (Smart Transfers)
When you create the preauthorization with
linkedJourney: true in POST /smart-transfers/preauthorizations, the user authorizes, in the same approval at the bank, reading the source account balance. The preauthorization now includes dataConsent with the permission status (AWAITING_AUTHORISATION, AUTHORISED or REJECTED). With the permission authorized, GET /smart-transfers/preauthorizations/{id}/balance returns the real-time balance and the overdraft limit (overdraft). To revoke only this permission, use DELETE /smart-transfers/preauthorizations/{id}/data-consent: the preauthorization stays active. Each query goes to the institution and counts toward the Open Finance monthly quota, so query right before transferring. Applies only to new preauthorizations.POST /smart-transfers/preauthorizationsGET /smart-transfers/preauthorizations/{id}/balanceDELETE /smart-transfers/preauthorizations/{id}/data-consentpaymentsapplies to: new preauthorizations
Improved
Linked account balance in PIX by biometrics
With
linkedJourney: true, the payer can also share the balance and overdraft of the account they link, so you can check it before charging.payments
🚀 New Features4
New
Scheduled payments from checking accounts (Open Finance)
Boletos, Pix and debits that the user has already scheduled at the bank now appear in
GET /transactions as transactions with status: PENDING and date set to the scheduled date. When the payment is made, the transaction moves to POSTED keeping the same id (transactions/updated webhook). If the schedule is canceled, the transaction is removed (transactions/deleted). Scheduled payments do not affect the account balance until they are made. It starts with Itaú (601), up to 90 days ahead, and the next institutions will be added gradually. Note: if you query with to equal to today, you will not see scheduled payments. Use a to in the future.GET /transactionsconnector 601open finance
NewRicher real-time balance:
Richer real-time balance: GET /accounts/{id}/balance
For Open Finance accounts, the endpoint now returns
blockedBalance, automaticallyInvestedBalance and closingBalance (balance + blockedBalance). Optional fields are omitted when the institution does not provide them. The call also updates bankData.closingBalance and bankData.automaticallyInvestedBalance in GET /accounts/{id}, which previously only changed on the next sync. At Itaú and Banco do Brasil, balance already includes the automatic investment, so balance and automaticallyInvestedBalance carry the same value. Available in pluggy-node 0.93.0, pluggy-net 0.46.1 and pluggy-java 1.16.1.GET /accounts/{id}/balanceGET /accounts/{id}open finance
New
SCR in sandbox
You can now test SCR without connecting a real account: create an item on the Sandbox Open Finance connector (600) with one of the sandbox CPFs and call
GET /items/{id}/scr. The response is synthetic, deterministic and has the same format as production. It does not query Bacen and is not billed. The SCR feature still needs to be enabled for your team, and windows with more than 60 reference dates are rejected in sandbox.GET /items/{id}/scrconnector 600open finance
New
New tools in the Pluggy MCP
From the assistant you already use (Claude, ChatGPT, Cursor…), logged in with your Dashboard account, you can now investigate your integration without opening a ticket.
get_execution_reports shows what each sync of an item brought: products with data, empty or failed, and transactions created, updated and removed. summarize_api_calls and list_api_calls show the calls your application made to the Pluggy API. summarize_of_calls and list_of_calls show the calls Pluggy made to the institution for each item, with the status of each one (for example, 429 for the bank's rate limit or 423 for the monthly limit). Each user only sees the applications and items of their own teams.open finance
🖥️ Dashboard5
Improved
Request logs and metrics
In the new Monitor section, the Logs page shows call, error and latency metrics for your application, with filters to find a request and the request and response detail for diagnosis. The section also brings together Webhooks and Analyze.
dashboard
Improved
API and Open Finance performance on the home page
The Dashboard home separates the calls you make to the Pluggy API from the requests Pluggy sends to Open Finance institutions: volume, HTTP response distribution, most-called endpoints and p95 latency per endpoint. The Open Finance view covers the last 24 hours, per application.
dashboardopen finance
Improved
Execution explorer
In Execution Troubleshooting, click an execution to see which products came with data, empty or failed, what the institution returned (accounts, cards, investments…) and the transactions created, updated and deleted. On the most recent execution, the panel also shows the item error and the state of each product. The history covers the item's last 20 executions.
dashboard
Improved
What's New
The Dashboard now has a What's New area, with a quick introduction to each release and access to this changelog.
dashboard
Improved
Monitors (beta)
On the new Monitors page, you set up alerts on your integration without depending on our team: create a monitor from templates with Pluggy's default values or define the metric, scope and condition, with a preview of the series and the threshold. When the monitor fires or recovers, the notice arrives by email or Slack, and active alerts and history are visible in the Dashboard. Monitors can be muted. Available on the Full and Full Plus plans; creating and editing monitors and channels requires the Owner or Admin role.
dashboardapplies to: Full and Full Plus plans
🛠️ Resolved incidents3
Improved
Cora
The connector was unavailable between 10/06 and 10/07 and had degraded performance between 10/10 and 10/12. The connection was restored on 10/12.
connectors
Improved
Banco do Brasil Empresas
Degraded performance between 10/16 and 10/17: connections with a device pending release ended in
UNEXPECTED_ERROR. They now follow the release flow again: the connector asks for the phone number for the SMS or leaves the item in USER_AUTHORIZATION_PENDING, with instructions to release the device in Internet Banking.connectors
Improved
Sicoob (Open Finance)
The checking account was not returned for some consents between 09/28 and 10/27. Resolved on 10/27.
open finance
🐛 Fixes3
Fixed
Future installments and pending card purchases (Itaú PF and C6, Open Finance)
At Itaú PF (601), future installments are now dated within the bill they belong to and are no longer deleted before that bill closes. At C6 (626), recent pending purchases are no longer deleted and recreated when the bill closes. The fix applies to new purchases. Note: at Itaú PF, the
date of a future installment is now the bill's date, not the purchase date.connector 601connector 626credit cardopen financeapplies to: new purchases
Fixed
XP investments (Open Finance)
New XP (602) investment positions stopped arriving when the institution's monthly query limit ran out, around mid-month. Positions now arrive on every update, without waiting for the month to turn.
connector 602open finance
Fixed
Investment fund taxes (Open Finance)
Investment funds from Open Finance now include
taxes (income tax provision) and taxes2 (IOF provision), which previously came as null. This applies to all Open Finance institutions that report these values. Existing positions are corrected on the item's next sync.open finance