Does adding a payment method later require a development sprint?
No. A new payment method is a setting on the platform, not a project. Opening a market means switching on its local methods, and card-present payments sit on the same stack as online ones, so in-store can go live without a second system. Your engineers stay on your product while your merchants gain the new options.
In detail
No. A new payment method is a setting on the platform, not a project for your engineers.
Payment methods are activated through contracts. A contract links a merchant account to a provider and carries the credentials, mapping and configuration that provider needs. Once the contract passes its activation test, the method can be offered at checkout and used in routing rules.
Opening a market works the same way
Opening a market means switching on its local methods, such as a domestic card scheme, a bank transfer method or a popular wallet. Your merchants explore the catalogue in the Console, with each method's type, countries and currencies, and select what their customers expect.
Card-present payments sit on the same stack as online ones. In-store can go live without a second system, and the same reporting and reconciliation cover both channels.
What stays with your team
Your product team decides which methods to offer and how to present them. Some methods may need a small change in how your own interface presents them, such as a redirect or a QR code, but the connection, certification and maintenance stay on the infrastructure side.
Your engineers stay on your product while your merchants gain new options, and every addition runs through the same governance and audit trail.