Skip to main content
August 24, 2026 Documentation correction Action required

​
Affects

Teams that use TED OUT completion signals, operate STA inbound transfers, or integrate Pix Automático or Consignado event streaming.

​
What changed

TED OUT exposes a transfer status of COMPLETED through its transfer and reconciliation APIs. It does not emit a transfer.completed event yet. The event and configuration documentation also now states that:
  • the BR Code context consumes spi.mandate.resolved to move a Pix Automático mandate out of CRIADA;
  • Consignado exposes its wired streaming manifest at GET /api/v1/streaming/manifest;
  • STA defaults SERVER_ADDRESS to :4028 and uses 11111111-1111-1111-1111-111111111111 only as the streaming/outbox ce-tenantid fallback when an event has no tenant ID; and
  • STA inbound ZIP extraction defaults to a single 5 GiB entry, a 5 GiB advertised-file limit, and a maximum 100:1 expansion ratio. Set a value of 0 or less only when you intentionally disable the corresponding bound.
This is a documentation correction of existing contracts. It does not announce a runtime release.

​
Impact

Classification: Action required. A TED OUT consumer that waits for the transfer.completed event will not receive that completion signal. The other corrections can affect event routing and operating limits.

​
What you need to do

1
Replace any TED OUT completion dependency on the transfer.completed event with a transfer or reconciliation API status check.
2
If you run BR Code for Pix Automático, include spi.mandate.resolved in the consumer path that advances a mandate from CRIADA.
3
Use the Consignado streaming manifest from the documented endpoint when validating your event catalog.
4
Review STA inbound-transfer overrides before deployment if its 5 GiB or 100:1 ZIP extraction bounds do not fit your operating environment.

​
Deadline

Update TED OUT completion handling before your next deployment.

​
Resources