The published PI or EMI comparison addresses the permission boundary. The remaining work concerns checkout instructions, payment confirmation and the merchant's obligations after the sale. (CoinGate, Create Order, opening description.)
Summary
- UK and Ireland. Consumer checkout requirements apply to the underlying sale. The merchant must provide the applicable price, additional-charge and cancellation information before the customer commits. (Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 (Consumer Contracts Regulations), regulation 13 and Schedule 2; CCPC, Buying online, "What information must a business give you before you buy?")
- UK and Ireland, implementation. Fulfilment should follow the provider's authenticated payment status. CoinGate distinguishes a transfer awaiting confirmation from a confirmed payment credited to the merchant. (CoinGate, Order Status, "confirming" and "paid"; API Callbacks, "Accepting Payment Callback".)
- UK and Ireland. HMRC and Revenue apply ordinary VAT treatment to goods paid for with cryptoassets. Their guidance requires valuation in sterling and euros respectively. (HMRC, CRYPTO45000; Revenue, Tax and Duty Manual Part 02-01-03, section 2.2.)
- UK and Ireland. Where statutory cancellation requires reimbursement, the default is the original payment method unless the consumer expressly agrees otherwise. A merchant must implement that duty in its refund process. (Consumer Contracts Regulations 2013, regulation 34(7); Consumer Rights Act 2022, section 117(5).)
- UK. Trading receipts in exchange tokens enter the taxable-profit calculation. The merchant must retain an appropriate valuation method rather than record only a later cash conversion. (HMRC, CRYPTO40350 and CRYPTO40100.)
Checkout prices and payment instructions
The order should distinguish the goods' price from the crypto payment and the merchant's settlement currency. CoinGate's order interface separates price_amount, price_currency and receive_currency. Its hosted checkout then allows the shopper to select the payment currency. A merchant using this design should preserve the original sterling or euro price alongside the payment record. (CoinGate, Create Order, "Body Params" and opening description.)
For UK consumer sales, the required pre-contract information includes the total price, applicable additional charges and payment arrangements. Where the contract requires payment, the information specified in regulation 14(2) must be clear and prominent directly before the order is placed. An electronic order must also make the obligation to pay explicit. When placing the order involves a button, its wording must identify that obligation unambiguously. Accepted payment methods must be clear by the start of the ordering process. The website must also state by that point whether any delivery restrictions apply. A wallet-connection step should not be mistaken for the consumer's required acknowledgement of a payment obligation. (Consumer Contracts Regulations 2013, regulation 13, regulation 14(2)–(6), and Schedule 2, paragraphs (f), (g) and (j).)
Irish distance sellers must provide the information required by section 106 and Schedule 3 before the consumer is bound. The CCPC's guidance includes the total price, extra charges and cancellation information. For electronic orders involving a payment obligation, section 108 also requires clear and prominent presentation of the specified information directly before the order, an explicit acknowledgement of the obligation to pay and unambiguous wording on any order button or similar function. Delivery restrictions and accepted payment methods must be clear by the start of the ordering process. These disclosures concern the merchant's sale even when another company supplies the payment screen. (Consumer Rights Act 2022, sections 106 and 108 and Schedule 3; CCPC, Buying online, "What information must a business give you before you buy?")
Supported networks and payment confirmation
The integration should use the provider's supported currency-and-network combinations. CoinGate's Platforms interface identifies supported payment networks and their currencies. Its sandbox and live systems have different identifiers, with fewer options available for testing. The launch configuration should replace test credentials and identifiers with their live equivalents. (CoinGate, Platforms, opening description; Environments, "Key Differences".)
CoinGate marks a transferred payment as confirming while it awaits network confirmation. Its paid status means the network has confirmed the payment and the merchant account has been credited. The provider identifies that status as the point when goods or services can be delivered. For an integration following that instruction, a customer's screenshot or return to the shop does not replace verification of the order's payment status. (CoinGate, Order Status, "confirming" and "paid".)
Payment notifications and duplicate fulfilment
CoinGate returns a callback token for checking payment notifications. The merchant's server should validate the token and match the notification to the stored order. Its checks should cover the expected price and currency before releasing goods. (CoinGate, Payment Callback, fields token, order_id, price_amount and price_currency; API Callbacks, "Accepting Payment Callback".)
The provider retries notifications and permits previously delivered callbacks to be resent. The fulfilment system should therefore recognise an order already processed and avoid a second dispatch. A useful acceptance test sends the same valid notification twice and checks that the order produces only one shipment. (CoinGate, API Callbacks, "Callback Retry Schedule" and "Re-send API Callback".)
Late payments and incomplete amounts
An expired invoice does not always end payment processing. CoinGate permits merchants to configure continued attempts to complete expired or cancelled orders. A merchant should coordinate that setting with stock reservations and order closure. Otherwise, a late payment can complete after the shop has treated the order as abandoned. Payment completion does not by itself revive a contract cancelled under the consumer cancellation rules. (CoinGate, Can an order be completed after it was cancelled or expired?, "Payment Completion Attempt"; Consumer Contracts Regulations 2013, regulation 33; Consumer Rights Act 2022, section 116.)
Underpayment and overpayment figures can change after an initial notification. Changes to those amounts do not trigger another callback; the latest values appear when the order is retrieved. The reconciliation process should retrieve the current record before resolving an amount discrepancy. (CoinGate, Payment Callback, fields underpaid_amount and overpaid_amount.)
VAT on the goods
HMRC's guidance, which labels its VAT treatments provisional, applies ordinary VAT to goods paid for with exchange tokens. It values the taxable supply using the tokens' sterling value when the transaction occurs. (HMRC, CRYPTO45000, opening paragraphs and qualification before "Bitcoin exchanges".)
Revenue adopts the corresponding approach in Ireland. Its guidance values the supply in euros at the time of the supply. The payment record should retain that valuation rather than substitute a later withdrawal amount. (Revenue, Tax and Duty Manual Part 02-01-03, section 2.2.)
Order confirmations and VAT invoices
A UK distance seller must provide contract confirmation in a durable medium. The confirmation must be provided within a reasonable time after the contract is concluded. For goods, the deadline is no later than delivery. The confirmation must include the required information unless it was already supplied in that form. Irish law also requires confirmation of the contract in a durable format for Irish online sales. It must be provided within a reasonable time after the contract is concluded and, for goods, no later than delivery, with the required information unless already supplied on a durable medium before the contract. A payment reference alone is insufficient when it omits the required contractual information. (Consumer Contracts Regulations 2013, regulation 16; Consumer Rights Act 2022, section 109; CCPC, Buying online, "Does the business have to provide me with any proof of purchase when I buy online or on my doorstep?")
A processor's payment invoice must be assessed separately against any applicable VAT-invoice requirements. HMRC requires a full VAT invoice to contain prescribed supplier and customer details, a description, dates and tax information. The total VAT must appear in sterling. Retail sales have different invoicing rules, including circumstances where an invoice is required only on request. A merchant should select the applicable invoice format before treating a checkout receipt as its tax invoice. (HMRC, Record keeping (VAT Notice 700/21), sections 3.1, 4.1 and 4.4.)
Trading income and valuation records
HMRC requires exchange tokens received in an existing trade to be accounted for in taxable trading profits. Keeping the tokens does not justify omitting the original trading receipt. The applicable accounting and tax rules govern the calculation. (HMRC, CRYPTO40350; CRYPTO40100, "Accounting practices for calculating trading profits".)
For sterling tax calculations, HMRC requires an appropriate rate at the time of each transaction and a consistent valuation method. Records must explain that method. Companies using an applicable non-sterling functional-currency election receive separate treatment before completing their sterling tax return. A single exchange rate taken when a year's proceeds are withdrawn does not implement the transaction-level approach. (HMRC, CRYPTO40100, opening paragraphs.)
Revenue states that accepting crypto does not change when trading revenue is recognised or how taxable profits are calculated. The sale must remain identifiable in the business's accounting records. (Revenue, Tax and Duty Manual Part 02-01-03, section 1.)
Consumer cancellation and reimbursement
For ordinary online goods purchases within the cancellation rules, UK and Irish consumers generally have 14 days after receipt to notify cancellation. Product-specific exceptions remain relevant, including personalised goods. The merchant should classify its goods before publishing a cancellation policy. A technical payment status does not establish whether a particular sale falls within an exception. (GOV.UK, Accepting returns and giving refunds: the law, "Items bought online, by mail or phone"; Consumer Contracts Regulations 2013, regulation 28; CCPC, Buying online, "Online purchase" and "When does the right to cancel not apply?")
In the UK, reimbursement must occur without undue delay. Where the trader has not offered to collect returned goods, the outer deadline is 14 days after receipt or earlier evidence of return. Other covered cases use 14 days after notification of cancellation. The refund includes standard delivery costs, but the trader need not repay the premium for a more expensive delivery option. (Consumer Contracts Regulations 2013, regulation 34(1)–(6).)
Ireland requires reimbursement without undue delay and within 14 days after cancellation notice. For goods, the trader may withhold payment until receipt or evidence of return, whichever occurs first, unless it offered collection. Section 117 does not grant a new 14-day period after receiving the return. (Consumer Rights Act 2022, section 117(1)–(4).)
UK and Irish consumers can be liable for diminished value caused by handling beyond what was necessary to establish the goods' nature, characteristics and functioning. That liability requires the prescribed cancellation information to have been supplied. (Consumer Contracts Regulations 2013, regulation 34(9)–(12); Consumer Rights Act 2022, section 118(6)–(7).)
The statutory default in each jurisdiction is reimbursement through the original payment method unless the consumer expressly agrees otherwise. The UK rule prohibits a reimbursement fee. Irish law prohibits fees caused by an agreed alternative method. A merchant should document any express agreement before substituting a bank transfer for the original payment method. (Consumer Contracts Regulations 2013, regulation 34(7)–(8); Consumer Rights Act 2022, section 117(5)–(6).)
Customer data and provider roles
For Irish operations, the Data Protection Commission describes each organisation's data-protection role as a question of fact. A controller determines the purposes and means of processing; a processor acts on documented instructions. Calling a supplier a payment processor does not determine its data-protection role. Where the supplier processes personal data on the merchant's behalf, the required binding processing contract must govern that activity. (Data Protection Commission, Controller and Processor relationships, "Obligation on Controllers and Processors under the GDPR to enter into Data Processing Contract".)
The DPC's minimisation principle requires personal data to be adequate, relevant and limited to what is necessary for the processing purpose. That principle applies to the personal information collected during checkout. The integration should avoid copying optional customer information merely because an interface accepts it. Required accounting retention and payment processing should be assessed separately from unrelated reuse of customer information. (Data Protection Commission, Principles of Data Protection, "Data Minimisation", "Purpose Limitation" and "Storage Limitation".)
Reconciliation and retained records
CoinGate distinguishes the merchant's price, the shopper's payment and the net amount credited after processing fees. The accounting export should connect those amounts to the same order. Recording only the net credit loses the distinction between the sale price and the provider's deduction. (CoinGate, Payment Callback, fields price_amount, pay_amount and receive_amount; HMRC, Record keeping (VAT Notice 700/21), section 7.2.)
UK VAT records generally require retention for at least six years; One Stop Shop and Mini One Stop Shop records require ten years. Businesses subject to Making Tax Digital for VAT must retain the required digital records. Where several software products maintain those records and submit returns, the data must pass through digital links. Returns or exchanges requiring a replacement invoice or credit note must remain connected to the original record. (HMRC, Charge, reclaim and record VAT, "Keeping VAT records".)
Revenue requires cryptoasset transaction records to remain available for six years. Storage on a wallet or other device does not remove the requirement to make the records accessible to Revenue. The merchant should retain usable exports before losing access to an account or device. (Revenue, Tax and Duty Manual Part 02-01-03, section 7.)
