A crypto payment gateway can connect a Shopify checkout to a cryptocurrency payment process, but the integration determines what customers see, how payment updates reach the store, and what settlement options are available. Merchants should verify current Shopify and provider documentation for eligibility, supported assets and locations, payment statuses, settlement, refunds, fees, security, support, and their own responsibilities. The evidence available here does not establish current Shopify-specific integrations or provider terms, so it cannot confirm that a particular setup or feature is available.

How a crypto payment gateway connects to Shopify

A payment flow involves distinct roles: Shopify presents the store’s checkout and order records; an integration connects the store to a payment service; and the relevant payment network processes or records a cryptocurrency transaction. These roles do not automatically share the same status or responsibilities. The exact handoff—such as a redirect, embedded checkout, or another customer step—depends on the configured integration and must be checked in its current documentation.

An app listing or integration option alone does not establish that a merchant can use it. Confirm whether the provider requires a separate account, verification, configuration, or approval, and whether the merchant’s location, business type, and intended assets are supported. Also check current Shopify requirements and any limitations that apply to the store or checkout configuration. This article cannot verify those platform- or provider-specific details.

For example, one operator’s documented Bitcoin ATM flow in Australia includes selecting an asset and amount, accepting disclosures, completing phone and identity checks, scanning a wallet QR code, inserting cash, confirming the transaction, and receiving cryptocurrency. That is an operator-specific example—not a description of Shopify checkout or a universal payment sequence. It illustrates why merchants should inspect the actual steps and requirements of the integration they intend to use. (source )

Follow the payment from checkout to order status

Map the customer’s action separately from the store’s response:

  1. The customer selects the payment method and follows the instructions shown by the configured checkout.
  2. The payment service detects or receives information about the transaction.
  3. The integration sends an update to the store, if its design supports that handoff.
  4. The Shopify order record is updated according to the integration’s status mapping and the merchant’s configuration.
  5. The merchant communicates the order’s status and decides when to fulfill it under the applicable workflow.

These are questions to verify, not a claim that every Shopify integration follows this exact sequence or uses the same status labels. Ask what the checkout displays, which system is authoritative for each status, and whether the store receives updates for incomplete, failed, partial, late, or successful payments.

A documented e-commerce integration example, BTCPay Server, distinguishes statuses such as awaiting payment, processing, settled, expired, invalid, partial, overpaid, and late, and calls for validating webhook signatures before updating an order. A webhook is a message that an integration can use to report a change in transaction state. This example illustrates useful status-handling questions; it does not establish how a Shopify integration or another provider works. (source )

Do not treat a transaction being broadcast as proof that the merchant’s fulfillment conditions have been met. A broadcast transaction has been sent; the merchant’s configured settlement conditions determine when an onchain payment should be treated as fulfilled. Confirm the provider’s status definitions and the store’s fulfillment trigger before making goods or services available. (source )

For customer communications, check what the integration says when a payment is pending, unsuccessful, or requires follow-up, and whether those messages can be customized. Establish who handles customer questions when the checkout, provider dashboard, and Shopify order record show different information. The evidence available here does not specify Shopify’s order-update behavior or any provider’s recovery process, so those details require direct verification.

Settlement, refunds, and reconciliation

The asset a customer uses to pay and the asset or currency a merchant receives are separate questions. Confirm whether the provider passes through the received cryptocurrency, offers a conversion option, or supports another settlement arrangement. Check the applicable schedule and conditions in the provider’s current terms; the available evidence does not establish a timing, conversion rate, or guaranteed settlement outcome.

Ask for the complete fee schedule and determine which charges apply to payment, conversion, settlement, refunds, or other relevant operations. Do not infer a fee or rate from a checkout estimate without checking its scope and conditions. The information available for this article does not substantiate a fee amount or provider-specific refund policy.

Before launch, document how a Shopify order can be matched to payment and settlement records. Check which identifiers appear in each system, who can retrieve them, and how staff handle refunds, adjustments, and mismatches. Ask whether refunds are made in cryptocurrency, another currency, or through a separate process, and how the amount is determined. These are verification questions; no universal refund method or accounting treatment is established here.

Reconciliation should account for differences between the store’s order record and the provider’s payment record. Identify which record staff consult when statuses disagree, how they document a resolution, and who is authorized to make a change. If the integration supplies notifications, confirm how the system handles repeated or delayed messages. The documented BTCPay example supports checking status distinctions and webhook validation, but it does not establish that a Shopify integration uses the same records or processes. (source )

Merchant checks before enabling crypto checkout

Use current Shopify and provider documentation to work through these checks:

  • Availability: Confirm store eligibility, provider access, supported locations, business types, assets, and networks. Treat these details as time-sensitive and integration-specific.
  • Customer flow: Review the exact checkout screens, instructions, and failure messages. Confirm whether customers leave Shopify checkout and how they return to the order flow, if applicable.
  • Order states: Identify the status labels and the event that triggers each Shopify order update. Check how the integration handles delayed, incomplete, partial, duplicated, or conflicting updates. For webhook-based integrations, verify instructions for checking event authenticity and handling repeated or out-of-order events. A notification is not by itself proof that fulfillment conditions have been met. (source ; source )
  • Settlement and refunds: Get written terms for supported settlement assets, conversion, timing, fees, and refund handling. Confirm what transaction and settlement records are available for reconciliation.
  • Permissions and security: Review the access requested by the integration, its data handling, account protections, incident procedures, and support route. The evidence available here does not establish the permissions or security controls of any specific Shopify integration.
  • Support and recovery: Find out how the merchant can regain account access, report a failed or disputed payment, and reach support. Verify these paths before relying on the integration for live orders; no specific provider recovery process is established here.
  • Testing: Where the provider and Shopify setup offer a non-live test environment, use it to check customer instructions, order-state transitions, notifications, and reconciliation before accepting live payments. The available evidence does not establish that every integration offers such an environment.

Keep a record of the documents and settings checked, including when they were reviewed. Availability, supported assets, checkout behavior, and terms can change, so recheck them before changing the store’s payment configuration. Make sure the staff responsible for order handling know which status triggers fulfillment and where to escalate an unresolved mismatch.

Compliance and jurisdiction-specific questions

Provider availability or a provider’s compliance process does not establish the merchant’s own legal, licensing, reporting, or tax obligations. Those issues depend on the relevant jurisdiction and business circumstances. The evidence available for this article does not establish Shopify-specific regulatory requirements, a merchant’s licensing status, or tax treatment, so it cannot answer those questions for a particular store.

Use authoritative sources for each jurisdiction where the merchant operates, and obtain qualified, jurisdiction-specific tax guidance for recording receipts, conversions, refunds, and reporting. Keep this review separate from the technical integration check: a checkout that works as configured does not, by itself, establish that the merchant has met applicable obligations.

Sources and references