3
READING TIME
Introducing “Connections”: the new way to manage your payment providers
Jun 20, 2025
Until now, each payment method in Zru had to be configured separately. Setting up several methods from the same provider meant repeating the credentials for each one. It worked, yes, but it was also redundant. And the more complex a merchant’s payment stack was, the more obvious that friction became.
We knew we could do better.
Today, we’re taking an important step in that direction: the “Payment methods” section is now called “Connections.” And while the change might seem small at first glance, it reflects a deeper redesign of how we approach payment integrations in Zru.
A simpler, more logical architecture
Instead of managing each method separately, everything is now grouped under a single connection per provider.
For example, if you use dLocal to accept card payments, but also use Pix or Pse with them, you no longer need to configure each method independently — just connect dLocal’s credentials once.
This brings several benefits:
Fewer steps to activate new methods
A cleaner setup with no duplicates
Full visibility of everything you’ve connected, all in one place
You can also enable or disable methods directly from the connection itself, without wasting time switching between screens.
Beyond payments
Another reason behind the change is that merchants increasingly need more than just payment methods. They need to integrate additional services: agnostic 3DS, fraud detection, network tokens, chargeback management...
With the new architecture, Connections becomes a space built for all of that. A flexible system, ready to grow and adapt as your operations evolve.
Why now?
Because what used to be an advantage — activating many methods in just a few clicks — is no longer enough. Digital merchants are raising the bar: they want to scale fast, have control over their integrations, and not depend on a rigid flow to test or tweak their payment strategy.
Connections comes from that insight: from watching how the needs of scaling merchants are evolving. We wanted to offer something that not only works better, but naturally supports each merchant’s growth.
3
READING TIME
Introducing “Connections”: the new way to manage your payment providers
Jun 20, 2025
Until now, each payment method in Zru had to be configured separately. Setting up several methods from the same provider meant repeating the credentials for each one. It worked, yes, but it was also redundant. And the more complex a merchant’s payment stack was, the more obvious that friction became.
We knew we could do better.
Today, we’re taking an important step in that direction: the “Payment methods” section is now called “Connections.” And while the change might seem small at first glance, it reflects a deeper redesign of how we approach payment integrations in Zru.
A simpler, more logical architecture
Instead of managing each method separately, everything is now grouped under a single connection per provider.
For example, if you use dLocal to accept card payments, but also use Pix or Pse with them, you no longer need to configure each method independently — just connect dLocal’s credentials once.
This brings several benefits:
Fewer steps to activate new methods
A cleaner setup with no duplicates
Full visibility of everything you’ve connected, all in one place
You can also enable or disable methods directly from the connection itself, without wasting time switching between screens.
Beyond payments
Another reason behind the change is that merchants increasingly need more than just payment methods. They need to integrate additional services: agnostic 3DS, fraud detection, network tokens, chargeback management...
With the new architecture, Connections becomes a space built for all of that. A flexible system, ready to grow and adapt as your operations evolve.
Why now?
Because what used to be an advantage — activating many methods in just a few clicks — is no longer enough. Digital merchants are raising the bar: they want to scale fast, have control over their integrations, and not depend on a rigid flow to test or tweak their payment strategy.
Connections comes from that insight: from watching how the needs of scaling merchants are evolving. We wanted to offer something that not only works better, but naturally supports each merchant’s growth.
