Payment Gateway
Understand how a gateway connects merchant orders with payment outcomes and specialist processing services.
Explore page ↗02Merchant Tools
Explore transaction visibility, reconciliation, refunds, and dispute follow-up requirements.
Explore page ↗03Payment Methods
Discuss payment preferences, merchant eligibility, and the scope required for your customer journey.
Explore page ↗04Developers
Clarify integration architecture, confirmed documentation, and technical responsibilities.
Explore page ↗Start with the business, then connect the technology
A merchant needs more than a checkout button. The website must connect an order to its payment, the operations team needs to understand transaction outcomes, and the business needs a clear route for integration questions.
Three connected layers
The integration layer connects the merchant’s website or application to the gateway. The merchant layer is intended to bring transaction visibility and operational follow-up together. The processing layer involves specialist providers responsible for agreed processing, acquiring, approval, and settlement arrangements. A useful solution makes the boundaries between these layers understandable rather than hiding them.
Choose the starting point that matches your need
Explore Payment Gateway for the intended payment journey and division of responsibilities. Visit Merchant Tools for reporting, reconciliation, refund requests, and dispute follow-up. Payment Methods explains the initial card-payment goal and the assessment of additional options.
Define scope before implementation
The right starting scope depends on the business activity, registered country, website or application, and partner requirements. Before development, the parties need to agree what is included, who supplies each requirement, and what evidence will be needed for testing.
- 01Your businessWebsite or application
- 02Sofa WorkUnified gateway
- 03Processing servicesSpecialist payment partners
The payment outcome needs to be linked back to the merchant’s order or service reference. Exact responsibilities and interfaces depend on the agreed arrangement.