Written by DROPS.ST.
A payment gateway carries payment information through the checkout process. A merchant-account or acquiring arrangement handles the card-acceptance relationship and settlement under its agreed terms. Your ecommerce platform presents the products and order. Providers may bundle these services, but buying one does not automatically secure the others.
DROPS offers a connected shop with BTC/XMR checkout and order-status handling. That is a distinct payment route to evaluate. It does not amount to card-merchant approval, and it should not be compared with a card gateway as though both were the same service.
Separate the jobs behind the payment button
Authorize.net's payment-processing explanation distinguishes the gateway from the merchant bank account. Its merchant-account and processor guide also explains the acquiring and processing roles. These are useful definitions, not a recommendation that the provider accepts your particular vape catalogue.
| Part of the arrangement | Main job | Question to ask |
|---|---|---|
| Ecommerce platform | Product selection, cart and order record | Which payment connections are demonstrated? |
| Gateway | Transmit and manage payment requests | Which processor or acquiring arrangement does it use? |
| Acquirer or merchant-service arrangement | Approve and support card acceptance under contract | Does the approved scope include the exact products and channels? |
| Processor | Handle transaction data through payment networks | Who resolves transaction and settlement issues? |
Some services combine several roles in one commercial package. Ask the provider to explain the actual arrangement rather than forcing its product into a rigid label.
Get an answer for the real business
Describe your products accurately, including relevant nicotine products, devices, accessories and selling locations. Ask about online sales specifically if your existing arrangement only covers the physical shop.
A gateway account, a technical integration or a successful sandbox transaction does not establish live merchant approval. Confirm the accepted catalogue, any conditions, settlement arrangements and the provider responsible for the decision before depending on card payments at launch.
Keep software signup and payment approval distinct. Our guide to software, payment and customer verification explains why those decisions should not be collapsed into one promise.
Compare the complete fee schedule
Request the actual charges for the proposed service, including monthly fees, transaction charges, any minimums and relevant exception costs. Ask which fees continue when there are few orders. Understand reserves or settlement delays if they form part of the quoted arrangement.
For an illustrative comparison, suppose one quote contains a monthly platform fee of 60 and a gateway fee of 20, while another lists 80 for those two services together. Both total 80 before transaction charges and other costs. A lower headline gateway price has not established a lower total.
Now add the same expected order volume and transaction values to each quote. Keep every assumption visible, and do not invent an approval probability or a generic “high-risk rate”. The provider's offer for your business is the relevant input.
Test the order and the payment status together
During a demo, use supported test scenarios to see a successful payment, a pending state and an unsuccessful attempt. Check whether staff can identify the order without interpreting a customer screenshot as proof of payment.
For DROPS crypto checkout, inspect the relevant payment and order states and discuss how exceptions are handled. Gateway versus operator-wallet roles provides a separate comparison for that path. Do not assume automatic refunds, conversion or card-style settlement behaviour.
Explore DROPS with your product range and intended payment methods. Choose a buying path your customers can use and a payment arrangement whose responsibilities and costs are clear to your team.