Blockchain Payment Integration
Accepting crypto is straightforward. Accepting it in a way your finance team can reconcile, your accountant can report and your customer can get refunded is the actual project. Zelpex integrates on-chain payments into commerce and SaaS products with the back-office half treated as a first-class requirement rather than an afterthought.
We work with stablecoin and native-token payments across EVM chains and Solana, using established processors where they fit and direct integration where they do not. The recurring design questions are volatility, confirmation time and refunds — each of which behaves differently from card payments and needs an explicit answer before launch.
- Stablecoin and native-token checkout with clear confirmation states
- Reconciliation and exports your finance team can actually work with
- Refund and chargeback handling designed around irreversible transfers
- Wallet flows that do not lose customers who have never used one
Decide the volatility policy
Whether you price in fiat and settle in crypto, hold the asset, or convert immediately. This is a finance decision with engineering consequences, and it should be made by the people who own the P&L.
Define confirmation rules
How many confirmations before an order is treated as paid, and what the customer sees while waiting. Too few risks reorgs, too many make checkout feel broken.
Build reconciliation first
Every on-chain payment maps to an order and an accounting entry, with a report finance can run. Crypto payments that cannot be reconciled become a month-end problem that recurs forever.
Plan the refund path
Transfers do not reverse, so refunds need an explicit process — a return address, an approval step, and a policy your support team can follow without improvising.
What merchants ask us about crypto payments
A processor for most merchants: they handle volatility, compliance and settlement, and the integration is comparable to a card gateway. Direct makes sense when you want custody, need chains a processor does not support, or the fee difference is material at your volume. Direct also means you own compliance.
As a new outbound transaction, which makes them a policy question rather than a technical one. You need a stored return address, an approval step, and a rule for what happens when the customer's wallet has changed. Teams that skip this discover it during their first dispute.
This is where the real work is. Depending on jurisdiction, receiving crypto can be a disposal event with a gain or loss at the moment of receipt. We build the export and reporting your accountant needs, but the treatment itself should be confirmed with them before launch, not after.
Where these projects usually go wrong
Not in the checkout. In reconciliation, refunds and the first conversation with an accountant.
We treat the finance and support side as part of the build, because a crypto payment path that works technically and creates a monthly manual reconciliation is a net loss. That means exports, audit trails and a refund process defined before the feature ships.
Thinking about a project like this?
Tell us what you are building and what is getting in the way. You will get an honest read on scope, approach, and whether we are the right team for it — including when the answer is that you do not need us.
Services that pair well with crypto payments
Adobe Commerce Integration
Enterprise-grade e-commerce solutions with Adobe Commerce (Magento). Full integration, customization, and ongoing support for scalable online stores.
BigCommerce Development
Build and scale your online store with BigCommerce. Custom themes, integrations, and performance optimization for growing businesses.
Shopify Commerce Development
Custom Shopify stores, theme development, and app integrations. From startups to enterprise with Shopify Plus solutions.