Connect your checkout to your payment strategy
We provide payment gateway solutions for eligible businesses, aligning checkout requirements with the approved acquiring arrangement. Hosted checkout, API integration, transaction notifications and reporting needs are addressed as part of the implementation scope. We connect the technical discussion with the business model that will use the gateway.
Our approach
We define the customer journey, transaction states and reconciliation needs with your team and the relevant gateway provider. Required methods, currencies, authentication and recurring functions are confirmed for the selected configuration. Testing covers both successful payments and the exceptions your operations team needs to handle.
Choose the checkout boundary before choosing features
We review whether you need hosted checkout, an API-based journey or a connection to an existing platform. Describe where customers choose a payment method, where they enter payment details and where the order is confirmed. Bring the current platform, essential extensions and any recurring-payment needs into the discussion. A gateway feature list is useful only when it maps to the approved acquiring arrangement and the technical responsibilities your team is prepared to maintain.
Separate gateway functions from acquiring terms
We clarify which organisation provides the checkout connection, which handles acquiring and which defines settlement. Confirm any setup, gateway, transaction or support charges in the actual proposal. Authentication, stored credentials, recurring payments and local methods should be discussed as individual requirements, not assumed from the word gateway. Your team should receive the agreed integration scope and relevant provider documentation so commercial expectations and technical delivery follow the same arrangement.
Agree how orders receive their final payment status
We support a practical transaction-state discussion before launch. Your developer should identify how success, decline, cancellation, pending status and refund results reach the order system using the selected integration. Browser redirects and server notifications need a clear division of responsibility. Test the same payment reference returning more than once, a customer leaving checkout and a notification arriving after the customer returns. The goal is an order history your support and finance teams can interpret consistently.
Maintain an integration your team can support
Keep the provider documentation, enabled methods, environment settings and escalation route accessible to the people operating checkout. Review changes to the store, domain, subscriptions or payment methods before releasing them into the live flow. Record transaction references and timestamps when reporting an issue. Do not include live card details, secret keys or passwords in a business brief. Additional features and any migration work need to be confirmed against the actual gateway arrangement.
Start your eLotPay enquiry
Prepare your company country, website, customer markets, expected activity and essential payment requirements. Include the issue you are trying to solve, such as a new checkout, additional methods or a different settlement need. Our business-brief tool organises those details into a download for your next discussion. It currently saves the file on your device rather than submitting an application online. Do not include card details, passwords or identity documents in the brief. Any subsequent document sharing should use the agreed secure onboarding channel.
Frequently asked questions
Should I choose hosted checkout or an API integration?
We review the customer journey, platform and development responsibilities before defining the integration. The selected provider must support the approach for the approved business and required features.
Does a gateway automatically include recurring billing?
No. Confirm recurring collection, stored-payment features and the subscription platform's responsibilities individually. A generic gateway description does not establish the functions available in your arrangement.