448 / 736CONFIRMO

Confirmo

Merchant payment gateway and payouts

A customer wants to pay in bitcoin; the merchant needs to know that payment has arrived and what they will receive. Confirmo connects the two sides. It creates a payment request, tracks the payment and credits the merchant. That journey does not always end in bitcoin, or immediately in the merchant’s own wallet.

Confirmo is a payment gateway for businesses and other professional clients. It helps them accept cryptocurrency payments and send funds to recipients, with conversion between assets where needed. Think of three separate steps: paying for an order, crediting a balance with the provider and transferring funds out. This entry distinguishes the general interface documentation from Confirmo Limited’s European terms.

The European contracting party is Ireland’s Confirmo Limited. ESMA records a notification dated 16.12.2025 for exchange between crypto-assets and funds, crypto-to-crypto exchange and transfers. Its terms updated 02.10.2026 describe business, professional and institutional use, rather than a personal shopping account. Registration needs approval and includes AML checks, measures against money laundering. The provider also states that it is not authorised to provide crypto-asset custody. Its working payment balance should therefore not be understood as a long-term storage service. These European terms do not automatically apply to other companies sharing the brand. [1] [2]

Imagine a shop pricing goods in euros and a customer paying BTC. The pricing currency, bitcoin sent and asset credited to the merchant can differ. An API, the interface through which the shop communicates with the gateway, creates an invoice and checkout link. currencyFrom sets the pricing base; the customer chooses a supported asset and network. settlement.currency specifies what the merchant receives. Here, null means keeping the asset the customer used. A credit to the Confirmo account is still not a transfer to a wallet whose keys the merchant controls. [4]

The checkout shows an amount, address, network and quote expiry. The Commercial Policy sets default windows of 15 minutes for settlement in ordinary money and 30 minutes for crypto settlement; extending the window recalculates the rate. The transaction must be broadcast to the correct address and network within the valid window. Required network confirmations can follow later: in Bitcoin, they relate to inclusion in blocks. Thus confirming is not yet paid. pending_verification awaits Travel Rule information about the participants in the transfer. Nor does a customer returning via returnUrl prove that the order was paid. [3] [5]

A webhook is an automatic message the gateway sends the shop when a payment changes. To prevent a forged message from triggering shipment, the integration must verify its origin and then retrieve the final status through GET invoice API. The documented method calculates bp-signature as a SHA256 fingerprint of the complete original message body followed by the callback password, a shared secret used for verification. Rebuilding the JSON with a different representation is insufficient. Delivery retries until a 200 response, up to 20 attempts. The shop must recognise further notices about the same invoice and avoid fulfilling the order again. [6]

A customer may send the wrong amount or pay after the quote expires. An overpaid invoice can remain paid while unhandledExceptions marks excess funds requiring attention. That case concerns returning the surplus, not automatically refunding the entire order. Underpayment tolerance is configurable rather than identical for every merchant. Accepting a late payment uses the current rate. European terms allow 30 days from invoice creation to resolve an exception; afterwards they state no obligation to refund and provide for a fee. Costs can consume small amounts. Do not overlook an exception just because the main order appears paid. [2] [7]

The gateway balance is for processing payments as they pass through. European terms provide for crypto transfers each business day to the merchant’s verified own wallet. If the company holds funds for two business days, it automatically converts them to ordinary money at the end of the second; timely settlement or a payout instruction can prevent this. An unverified address, insufficient funds after fees or AML checks can stop the transfer. The wording self-custody wallets refers to wallets controlled by the provider. It does not mean the merchant holds their private keys, which authorise spending. [2] [3]

A merchant can also use the balance to pay another recipient. Sending a different asset involves conversion. Before confirming, compare the amount debited, amount sent, rate and fees; an expired quote needs repricing. The rate includes a spread, an adjustment to the underlying market price. For an incoming invoice, also distinguish the customer’s wallet fee, Confirmo’s network fee and the processing fee deducted from the merchant. Acceptance of an instruction is not proof of delivery. A wrong address or network may be impossible to correct. [3]

Cancelling a purchase does not erase the original blockchain payment. Under the European terms, a refund is a new cryptocurrency transaction, preceded by conversion of an ordinary-money balance if needed. It uses the rate at execution and incurs new costs, while the original processing fee is not returned. Using the gateway therefore does not itself guarantee the customer the original market value. The provider may refuse a refund when costs reach the amount to be returned or the law prevents it. Merchants should explain their refund rules before the customer pays. [2]

For the clearest picture, read this entry together with Bitcoin, Lightning Network, LNURL, Lightning Address. The reverse links also lead from Bitcoin Payment at Alza.

DOC · 001ESMA — Authorized crypto-asset service providersPrimary DOC · 002Confirmo Limited — Terms and Conditions (2 October 2026)Primary DOC · 003Confirmo Limited — Commercial PolicyPrimary DOC · 004Confirmo — Accepting Your First PaymentDocumentation DOC · 005Confirmo — Invoice LifecycleDocumentation DOC · 006Confirmo — NotificationsDocumentation DOC · 007Confirmo — Handling Invoice ExceptionsDocumentation
Revised: Source-first · No investment advice