Key highlights
- Payments that need a second step: Stripe checkout completes methods such as Pix in Brazil, showing the customer the QR code or instructions to finish paying.
What’s new in Core dna Platform 2026.4.5
Stripe Payment Improvements and Bug Fixes
Stripe checkout supports payment methods that need an extra step, such as Pix in Brazil, and shows the customer the QR code or instructions to finish paying.
Changes in behaviour
- Custom checkout front ends: whenever Stripe asks the customer for an extra step, the purchase response is now
pendingwith anauthenticateaction, as it is for 3-D Secure. Integrations with their own handling of 3-D Secure should test asynchronous payment methods too.
Payments that need a second step
Stripe checkout now supports payment methods that need an extra step from the customer after the payment starts, such as Pix instant payments in Brazil. Customers are shown what they need to finish paying, for example a QR code to scan; before, only 3-D Secure card checks were handled. Which methods are offered is set in your Stripe dashboard, so nothing changes in Core dna's payment method settings.
A custom checkout front end sees the step in the purchase response: the state is pending, and the action carries what the browser needs, including nextActionType and, for methods such as Pix, hostedInstructionsUrl.
Other improvements and bug fixes
- The generated API documentation now renders correct links for union and nullable property, parameter and response types, which previously appeared broken or unlinked.
- Fixed an issue where desktop Safari users could be unable to scroll the page when the cursor was positioned over a data table in the admin interface.
- Fixed an issue where the color picker could appear hidden behind the attributes panel when a color field was used as an attribute, and gave its button rounded corners to match the other form inputs.
Go deeper
Was this page helpful?
Your answer goes to the docs team.