Digital-asset payments with a defined operating flow
We offer crypto payment processing solutions for eligible businesses, with asset, network, conversion and settlement requirements addressed individually. We connect the customer payment journey with the way your business needs to receive and reconcile proceeds. Supported functionality is defined for the selected arrangement.
Our approach
We review the underlying product, entity and customer markets before confirming the available route. The technical scope addresses payment instructions, completion status and exceptions such as amount or timing discrepancies. Refund handling, relevant fees and conversion records belong in the same operating discussion.
Define the digital-asset payment requirement precisely
We start with the customer sale, not a generic list of digital assets. Identify whether you need acceptance for goods or services, conversion into another currency or a particular settlement destination. Describe the company, products, customer markets and expected transaction sizes. Proposed assets and networks must be assessed explicitly for the arrangement. We do not assume that support for one asset or network means a merchant can accept all digital-asset payments.
Agree conversion, settlement and exception ownership
Your commercial review should establish the amount quoted to the customer, the asset and network used, any conversion requirement and the proceeds your business expects to receive. We address who supplies each part of that flow and which charges and conditions apply. Include refunds and payment exceptions in the discussion. A digital-asset payment option does not define the complete settlement agreement or replace the need to establish the eligibility of the underlying merchant activity.
Plan the customer flow around the selected provider
We support the requirements discussion for creating a payment request, showing instructions and recording the provider's final result. Ask the selected provider how it handles an expired request, an incorrect amount or a payment using an unsupported network. Those behaviours are implementation-specific and must be confirmed before launch. Your order system should retain the relevant provider reference and avoid presenting unresolved payments as completed sales simply because the customer has returned to the website.
Keep refund and support instructions explicit
Prepare a support route for customers who cannot relate a payment to their order. Your staff need the order reference, payment-request reference and timeline rather than private wallet credentials. Agree the refund process and who authorises it within the selected arrangement. When adding assets, networks or conversion options, review both the commercial scope and the customer instructions. We assess these changes against the actual business and the capabilities confirmed by the relevant providers.
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
Which assets and networks will my business be able to accept?
The proposed assets and networks must be assessed and confirmed for your arrangement. We do not publish an unverified universal list or treat support for one asset as support for all networks.
What should I clarify about conversion and refunds?
Identify the quoted amount, payment asset, network, conversion requirement, settlement destination and refund responsibility. Ask the selected provider how payment exceptions are handled before building the customer flow.