BitPay Privacy Guide

BitPay Inc. is cryptocurrency payment processor founded to enable businesses and organizations to accept digital currency payments with settlement in traditional fiat currencies. According to company positioning, BitPay serves as licensed and regulated payment gateway handling cryptocurrency acceptance while converting payments to local currency for merchant bank deposits. The platform eliminates merchant need to understand cryptocurrency technology, manage blockchain wallets, or handle cryptocurrency volatility risk.

According to service architecture, BitPay provides comprehensive payment processing infrastructure including invoice generation with locked exchange rates (protecting merchants from cryptocurrency price volatility during payment window), support for 100+ cryptocurrencies representing over 90% global crypto market capitalization (Bitcoin, Ethereum, Litecoin, Bitcoin Cash, Dogecoin, USDC, USDT, and numerous others), automatic conversion to merchant's chosen settlement currency (USD, EUR, and other supported fiat currencies), next-business-day bank settlement (BitPay initiates ACH or wire transfer to merchant bank account), integration options through flexible APIs, plugins for e-commerce platforms (Shopify, WooCommerce, Magento, PrestaShop, others), hosted payment pages, and point-of-sale systems for brick-and-mortar retail.

The fundamental regulatory framework distinguishes BitPay from typical payment processors. According to Terms of Use and compliance documentation, BitPay Inc. is subject to United States laws and regulations including Bank Secrecy Act (establishing anti-money laundering requirements for financial institutions), USA PATRIOT Act (expanding AML obligations and terrorist financing prevention), Office of Foreign Assets Control sanctions programs (prohibiting transactions with designated countries, entities, individuals), and state-level money transmission regulations where applicable.

According to FinCEN registration status, BitPay voluntarily registered with Financial Crimes Enforcement Network in 2011 as Money Services Business, establishing online account for electronically reporting suspicious activity. BitPay is licensed money transmitter in US states where applicable law requires licensing. This regulatory status means BitPay operates under same compliance framework as traditional money services businesses including check cashing services, money order providers, and remittance companies—but applied to cryptocurrency transactions.

For European operations, according to Terms of Use, BitPay B.V. is subject to Dutch and EU laws and regulations including Dutch Act on Prevention of Money Laundering and Terrorism Financing (Wwft) and Dutch Sanctions Act. BitPay B.V. maintains office in Amsterdam at Keizersgracht 520H, 1017EK, serving as Data Protection Officer contact point for European privacy inquiries.

The KYC/AML verification framework represents core compliance infrastructure. According to service requirements, BitPay requires Know Your Customer and Anti-Money Laundering compliance from customers using services to accept payments exceeding certain thresholds. Businesses must comply with Bank Secrecy Act and USA PATRIOT Act requirements. According to jurisdiction-specific thresholds, verification requirements trigger at $10,000 cumulative transaction value (general threshold), $3,000 for United States residents, and €1,000 for European Union residents.

According to identity verification process documentation, BitPay ID verification utilizes Onfido platform for identity document verification and biometric authentication. Process includes submitting government-issued identification (passport, driver's license, national ID card), providing proof of address documentation, completing live selfie or video verification to match face with submitted documents, and accepting Onfido privacy statement and Terms of Service. Onfido employs machine learning and AI algorithms for identity verification, conducting document authenticity checks, facial biometric matching, and fraud signal detection.

From data controller perspective, according to Privacy Notice, BitPay acts as data controller for merchant account information, transaction data, and KYC documentation. For shopper data (individuals paying BitPay invoices during merchant checkout), relationship is more complex—BitPay processes payment transaction but merchant controls customer relationship and determines what additional data to collect. According to invoice architecture, BitPay hosted invoice interface must be displayed to shopper during checkout, creating direct data processing relationship between BitPay and payer.

Service offerings span multiple use cases. According to product documentation, core offerings include merchant cryptocurrency acceptance (e-commerce, brick-and-mortar retail, digital goods, subscription services), cryptocurrency payouts and batch payments (paying contractors, affiliates, international recipients), crypto payroll services (paying employees in cryptocurrency or fiat converted from crypto), donation acceptance for non-profits (hosted donation pages with cryptocurrency support), and point-of-sale systems converting phones, tablets, computers into crypto payment terminals.

Pricing structure according to transaction processing documentation operates on tiered model based on cumulative month-to-date processed invoice value. Merchants automatically pay lower transaction rate as total processed invoices increase—lower rate applies to next invoice and entire invoice value. BitPay charges 1-2% transaction fee depending on monthly volume plus $0.25 fixed fee per transaction regardless of rate. Rates reset first of each calendar month. For Third Party Partner arrangements where processing fees set by aggregator or platform partner, BitPay does not reflect or deduct processing fees from invoices or merchant ledger—questions directed to partner. Network costs and miner fees separate from processing fees and charged to relevant invoice.

Security infrastructure according to security documentation includes multi-signature wallet technology requiring signatures from multiple participants preventing unauthorized access, mandatory two-factor authentication (2FA) for transaction confirmation from separate device, local data storage with passwords and wallet data stored exclusively on users' devices rather than centralized servers reducing server breach risk, and transaction encryption using modern cryptographic methods. BitPay received SOC 2 report from independent auditor addressing security of services.

Refund and chargeback handling differs from traditional payment processing. According to cryptocurrency payment characteristics, cryptocurrency transactions are generally irreversible on blockchain level. BitPay provides refund facilitation but refund processing differs from credit card chargebacks. For refunds in amounts based on fiat pricing currency, BitPay converts fiat value to cryptocurrency using exchange rate at time refund sent to shopper. Unless merchant instructs otherwise, miner fee for sending refund deducted from cryptocurrency amount refunded to shopper. For donation processing, BitPay does not facilitate cryptocurrency refunds or rescissions of donations—if donee chooses to issue refund, processing handled directly between donee and donor.

According to dispute resolution documentation, BitPay acts as intermediary between customer and merchant for payment disputes. Dedicated dispute resolution process assists merchants and customers resolving payment-related issues. Clear terms and conditions outline responsibilities and rights of both parties. Merchants encouraged to provide excellent customer service, clearly communicate refund and cancellation policies, and address customer issues promptly to minimize dispute escalation.

From account lifecycle perspective, according to Terms of Use, if account closed for any reason, BitPay retains certain information and account data stored on servers as required under applicable laws and regulations. This extended retention reflects regulatory obligations for financial institutions maintaining AML/CFT compliance records. Account closure results in immediate cessation of service access, license termination, and requirement to remove BitPay branding from websites, apps, marketing materials.

Data Categories Collected

BitPay's data collection framework reflects dual role as payment processor and regulated financial institution subject to Bank Secrecy Act and anti-money laundering requirements. According to Privacy Notice and EU Privacy Notice, data categories encompass regulatory compliance information, payment processing data, and operational analytics.

Merchant Account Information: For businesses using BitPay acceptance services, according to Privacy Notice, BitPay collects identifying information including real name or business name, aliases used in commerce, postal address and physical business location, unique personal identifiers (account numbers, customer IDs), online identifiers (IP addresses, device IDs), email addresses for account communication and notifications, account names and usernames, social security numbers or tax identification numbers for US merchants, driver's license numbers, passport numbers, or other government-issued identification numbers, phone numbers for account security and support contact, and business formation documents (articles of incorporation, operating agreements, business licenses) for entity verification.

According to California Customer Records Statute categories in CCPA disclosure, this includes information that identifies, relates to, describes, or is capable of being associated with individual or household including name, signature, social security number, physical characteristics or description, address, telephone number, passport number, driver's license or state identification card number, insurance policy number, education, employment, employment history, bank account number, credit card number, debit card number, or any other financial information, medical information, or health insurance information.

KYC and Identity Verification Data: According to BitPay ID verification requirements and Onfido integration, BitPay collects government-issued identification documents (passports, driver's licenses, national identity cards, residence permits), proof of address documentation (utility bills, bank statements, government correspondence), biometric data including facial images from submitted identification documents, live selfie photographs for liveness detection, facial geometry data extracted for biometric matching, document security feature analysis (holograms, watermarks, microprinting, UV features), and verification metadata (submission timestamps, device information, geolocation data from verification session).

According to Onfido's technology platform used by BitPay, identity verification involves machine learning algorithms analyzing document authenticity, biometric comparison between photo ID and live selfie, fraud signal detection, and liveness verification ensuring real person present during verification rather than photograph or video replay. Onfido maintains ISO 27001 certification and SOC 2 Type II compliance, operates EU and US data centers for data residency compliance, and provides biometric consent screens for US users referencing Illinois Biometric Information Privacy Act requirements.

Financial Account and Transaction Data: For payment processing and settlement, according to service model, BitPay collects merchant bank account information (account numbers, routing numbers, IBAN/SWIFT codes for international accounts, bank name and branch details), transaction history (cryptocurrency received, fiat amounts settled, exchange rates applied, timestamps, miner fees, processing fees), ledger balances (cryptocurrency held, fiat currency owed, pending settlements), payment source information (cryptocurrency wallet addresses used by payers, blockchain transaction hashes), and refund records (refund amounts, recipients, processing dates, miner fees deducted).

Shopper Payment Information: For individuals paying BitPay invoices, according to invoice processing model, BitPay collects email addresses for payment notifications and receipt delivery, cryptocurrency wallet addresses from which payments originate, blockchain transaction data (transaction hashes, amounts, timestamps, confirmations), IP addresses during invoice payment, device information (browser type, operating system, screen resolution), and optionally purchaser names if merchant requests this information for order fulfillment.

According to privacy framework, BitPay does not collect or store credit card information—service processes cryptocurrency payments exclusively. Shoppers pay invoices using self-custody wallets or exchange-connected wallets, with payment occurring on blockchain and BitPay detecting payment through blockchain monitoring.

Website and Analytics Data: According to Cookie Policy and privacy documentation, BitPay automatically collects website usage information including IP addresses and approximate geographic location derived from IP, browser type and version, operating system and device type, pages visited and navigation paths through website, time spent on pages and interaction patterns, referral sources (websites or search terms leading to BitPay), login timestamps and authentication events, and feature usage patterns within merchant dashboard.

According to analytics infrastructure, BitPay uses cookies and tracking technologies for strictly necessary functions (session management, login persistence, form data retention, security features), analytics purposes (traffic counting, performance measurement, user journey analysis through tools not specifically disclosed in available documentation), and targeting purposes (marketing through partners including LinkedIn for B2B advertising, understanding which site areas interest visitors, delivering relevant advertising on BitPay site or partner sites).

Compliance and Security Monitoring Data: As regulated financial institution, according to AML/ATF compliance program requirements, BitPay monitors suspicious activity patterns including unusual transaction volumes, velocity, or amounts, transactions involving high-risk jurisdictions or sanctioned entities, payment patterns inconsistent with business model, IP address anomalies or proxy usage, behavioral patterns suggesting fraud or money laundering, chargeback rates and dispute patterns, and blockchain analysis data (transaction chain analysis, wallet clustering, exchange deposit tracking for AML purposes).

According to Privacy Notice purposes, BitPay uses information to detect and protect against security incidents, malicious activity, deceptive activity, fraudulent activity, illegal activity, and to prosecute same. This includes maintaining internal watchlists, screening against OFAC sanctions lists, conducting enhanced due diligence on high-risk accounts, and filing Suspicious Activity Reports with FinCEN when required.

Support and Communication Records: According to customer service operations, BitPay retains support ticket content and email correspondence with merchants and shoppers, chat logs from customer service interactions, problem descriptions and resolution records, recorded phone calls when disclosed and consented, feedback and survey responses, and complaint records including Shopper/Donor complaints that may trigger account review or termination under Terms of Use Section 12.1.

Employment and Recruitment Data: According to EU Privacy Notice provisions on job applicants, BitPay processes applicant personal data including contact information (name, postal address, email, phone), working experience and employment history, education and qualifications, references from employers or colleagues, and recruitment agency information. Data collected from applicants directly, employer colleagues, recruitment agencies, or other references.

Data BitPay Does NOT Collect: According to service model limitations, BitPay does not collect or store credit card numbers (service is cryptocurrency-only payment processor), traditional card payment credentials (CVV codes, card expiration dates, magnetic stripe data), cryptocurrency private keys (users maintain custody of private keys in own wallets), extensive shopper personal information (unless merchant separately collects and shares—BitPay's invoice only requires email for receipt), or social media content (though may use LinkedIn for B2B marketing analytics).

Gramm-Leach-Bliley Act Exemptions: According to California-specific privacy provisions, CCPA privacy rights do not apply to personal information BitPay collects, processes, sells, or discloses subject to federal Gramm-Leach-Bliley Act and implementing regulations. Because BitPay is subject to those laws and regulations as financial institution, much personal information collected is exempt from CCPA. This means California residents' rights under CCPA limited for financial information collected in course of providing financial services.

Data Retention: According to EU Privacy Notice retention framework, in principle BitPay does not store personal data longer than strictly necessary for processing purposes. However, as regulated financial institution in United States, BitPay retains personal data collected as part of customer due diligence and identification program as required by applicable federal and state regulations. According to typical AML/CFT retention requirements under Bank Secrecy Act, financial institutions must retain customer identification program records for five years after account closure and suspicious activity documentation for five years after filing SAR. This extended retention applies to KYC documents, transaction records, and AML compliance documentation.

For account termination, according to Terms of Use, BitPay retains certain information and account data stored on servers as required under applicable laws and regulations. For recruitment data, retention period not specifically disclosed but follows employment law requirements. For website analytics, typical retention periods range from months to years depending on business need and legal requirements.

BitPay's legal basis for processing personal data varies significantly by jurisdiction and data category, reflecting complex position as US-regulated financial institution operating internationally. According to Privacy Notice and EU Privacy Notice, following legal bases apply.

Contractual Necessity for Service Provision: According to privacy framework, primary legal basis for processing merchant account information and transaction data is contractual necessity. BitPay must process personal information to perform Terms of Use contract including creating and maintaining merchant accounts, processing cryptocurrency payments and converting to fiat, initiating bank settlements, providing customer support, managing refunds and disputes, and maintaining accurate financial records.

For shoppers paying BitPay invoices, according to invoice processing model, contractual necessity applies to processing payment transaction data—BitPay must detect cryptocurrency payment, verify sufficient amount and confirmations, notify merchant of successful payment, and provide payment receipt to shopper. This processing necessary to complete checkout transaction even though primary contractual relationship exists between shopper and merchant rather than BitPay.

Compliance with Legal Obligations: As regulated financial institution, according to Terms of Use and regulatory framework, BitPay relies heavily on legal obligation as basis for processing. Bank Secrecy Act requires financial institutions to implement customer identification programs, verify customer identity, maintain records of identification information, and file suspicious activity reports. USA PATRIOT Act expanded these obligations including enhanced due diligence for certain account types and terrorist financing prevention.

According to AML/CFT legal requirements, BitPay must collect and verify government-issued identification, conduct risk-based customer due diligence, monitor transactions for suspicious patterns, screen customers and transactions against OFAC sanctions lists, maintain comprehensive AML compliance program, retain records for regulatory examination, and report suspicious activity to FinCEN. These are not discretionary processing activities—federal law mandates these processes for money services businesses.

According to FinCEN Money Services Business obligations, BitPay must register as MSB, designate compliance officer, implement written AML policies and procedures, conduct independent audits of compliance program, and train personnel on AML requirements. State money transmitter licenses impose additional compliance obligations varying by jurisdiction.

For European operations, according to BitPay B.V. legal framework, Dutch Act on Prevention of Money Laundering and Terrorism Financing imposes similar customer due diligence requirements, Dutch Sanctions Act requires sanctions screening, and EU anti-money laundering directives establish harmonized standards across member states.

Legitimate Interests: For certain processing activities, according to EU Privacy Notice GDPR framework, BitPay relies on legitimate interests including fraud prevention (detecting and preventing fraudulent transactions, protecting platform integrity, identifying compromised accounts, preventing cryptocurrency theft or scams), security monitoring (logging access to systems, detecting unauthorized access attempts, maintaining audit trails for security investigations, conducting penetration testing and vulnerability assessments), business operations (maintaining financial records, conducting internal audits, managing vendor relationships, defending legal claims, enforcing Terms of Use), service improvement (analyzing aggregated usage patterns to optimize performance, identifying feature adoption to inform product development, conducting market research through anonymized data), and marketing communications (sending relevant business updates to merchants about platform features, industry developments, regulatory changes).

According to GDPR balancing requirements, legitimate interests must be weighed against rights and freedoms of data subjects. BitPay implements safeguards including data minimization in operational logs, access controls limiting staff access to personal data, encryption protecting sensitive information, transparency through documented privacy policies, and data subject rights fulfillment mechanisms.

Consent: According to privacy framework, consent serves as legal basis for certain processing activities including marketing communications beyond transactional emails (where opt-in required by law such as GDPR), optional features requiring data sharing (if BitPay implements any), analytics cookies and tracking beyond strictly necessary functions (where ePrivacy Directive or similar laws require consent), and biometric data processing where required by law (for example, Illinois BIPA requires written consent before collecting biometric identifiers).

According to Onfido biometric verification used for BitPay ID, consent screens present to US users reference BIPA requirements. For EU users, GDPR Article 9 requires explicit consent for processing biometric data for unique identification purposes. Consent must be freely given, specific, informed, unambiguous, and provided through clear affirmative action—pre-checked boxes or implied consent insufficient.

Vital Interests and Public Interest: Though rarely invoked, according to GDPR framework, vital interests may justify processing necessary to protect life or physical safety of data subject or another person. Public interest basis applies to processing necessary for carrying out obligations in field of employment and social security and social protection law. Given BitPay's role as financial services provider, public interest may support AML/CFT processing insofar as preventing money laundering and terrorist financing serves public good recognized in law.

Special Categories - Biometric Data: According to GDPR Article 9, biometric data processed for purpose of uniquely identifying natural person constitutes special category requiring higher protection. BitPay processes facial biometric data through Onfido verification platform. Legal basis for this processing includes explicit consent where required by jurisdiction, legal obligation to perform customer due diligence under AML laws, or substantial public interest in preventing money laundering and terrorist financing.

According to BitPay's position, KYC verification serves AML compliance obligations mandated by law—financial institutions cannot legally provide services without verifying customer identity. This mandatory compliance context affects consent analysis under GDPR—while users can choose whether to use BitPay, if they choose to use service exceeding verification thresholds, identification verification is condition of service provision rather than optional feature requiring separate consent.

Gramm-Leach-Bliley Act Framework: For US operations, according to California privacy provisions noting GLBA applicability, much of BitPay's processing falls under Gramm-Leach-Bliley Act regulatory framework for financial institutions rather than general privacy laws like CCPA. GLBA establishes specific privacy and security requirements for financial institutions including providing privacy notices to customers, offering opt-out from certain information sharing, implementing administrative, technical, physical safeguards to protect customer information, and contractually requiring service providers to maintain safeguards.

GLBA does not rely on 'legal basis' framework like GDPR but instead presumes financial institutions may collect and use personal financial information necessary to provide financial services, subject to specific limitations on sharing with non-affiliated third parties and required privacy notice disclosures.

Data Subject Rights and Limitations: According to EU Privacy Notice, data subjects have rights to access personal data, rectification of inaccurate data, erasure (subject to regulatory retention requirements), restriction of processing, data portability, and objection to processing based on legitimate interests. However, according to AML retention obligations, right to erasure limited where retention necessary for compliance with legal obligation to which BitPay is subject (Bank Secrecy Act, state regulations). BitPay cannot delete KYC records or transaction data within regulatory retention periods regardless of data subject request.

Merchant vs. Shopper Legal Bases: According to data controller roles, for merchants using acceptance services, BitPay acts as independent controller with direct legal bases described above. For shoppers paying invoices, relationship more nuanced—merchant is controller for customer relationship and purchase data, but BitPay processes payment transaction as independent controller for fraud prevention, AML compliance, and payment facilitation purposes. Shopper's payment of invoice constitutes entering into payment processing transaction with BitPay even though underlying purchase is with merchant.

BitPay's subprocessor disclosure is significantly more limited than typical enterprise SaaS providers. According to available documentation, BitPay does not maintain publicly accessible, comprehensive subprocessor list. Subprocessor information must be gleaned from privacy policy references, service documentation, and technical implementation details.

Onfido / Entrust (Identity Verification): According to BitPay ID verification process and identity verification documentation, Onfido provides identity document verification and biometric authentication services. Onfido (acquired by and now part of Entrust) processes government-issued identification documents, facial biometric data from selfies, liveness detection data, document authenticity analysis, and fraud signals.

According to Onfido compliance framework, service maintains ISO 27001 certification (information security management system certification number IS 660122 issued by BSI), SOC 2 Type II compliance (audited by BDO Limited covering security, availability, and confidentiality trust service principles), EU and US data center options enabling customers to satisfy data residency requirements, and Workflow Studio capability to route verification checks to specific regions when regulations require.

According to Onfido's data processing, EU/UK data residency guarantee ensures personal data collected in EEA or UK stays in-region unless Standard Contractual Clauses or equivalent safeguards in place. Encryption includes TLS 1.2+ in transit and AES-256 at rest with 256-bit SSL. Biometric consent screens present to US users reference Illinois BIPA requirements. Default retention follows customer-defined schedules with maximum limits in privacy notice. Annual ISO and SOC 2 reports available to customers under NDA.

Processing locations for Onfido include EU data centers for European customers and US data centers for US customers, with customers able to specify regional routing based on compliance needs. Onfido processes on behalf of BitPay as subprocessor for identity verification function.

Banking and Settlement Partners: According to payment processing model, BitPay initiates bank settlements to merchants next business day after cryptocurrency payment conversion. This necessarily involves relationships with banks and payment networks though specific banks not disclosed publicly. According to US financial system architecture, settlements likely utilize Federal Reserve's Automated Clearing House (ACH) network for domestic US transfers, wire transfer networks (Fedwire) for same-day or large transfers, SWIFT network for international transfers, and correspondent banking relationships for currency conversion and cross-border settlements.

These banking partners process merchant bank account numbers, ACH routing numbers, settlement amounts and timing, and merchant identifying information necessary for payment processing. However, banking relationships fall under financial services agreements rather than typical data processing agreements, and banks serve as independent financial institutions rather than subprocessors in data protection sense.

Cloud Infrastructure and Hosting: According to typical payment processor architecture and absence of contrary disclosure, BitPay likely utilizes cloud infrastructure providers for application hosting, database services, and operational infrastructure. Common choices for financial services include Amazon Web Services, Google Cloud Platform, Microsoft Azure, or specialized financial services hosting providers meeting compliance requirements. However, specific hosting providers not disclosed in available documentation.

Given BitPay's security infrastructure including SOC 2 audit, hosting providers would need to meet comparable security standards with certifications such as SOC 2 Type II, ISO 27001, PCI DSS (if card data ever involved), and compliance frameworks relevant to financial services.

Analytics and Monitoring: According to Cookie Policy and typical SaaS operations, BitPay uses analytics services though specific providers not named beyond general references. Cookie Policy mentions analytics cookies allowing BitPay to count visits and traffic sources to measure and improve site performance, calculating visitor, session, and campaign data through aggregated anonymous user data. Specific analytics platforms (Google Analytics, Mixpanel, Segment, or others) not disclosed in available documentation.

CDN and Security Services: According to Cookie Policy, Cloudflare identified as providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services. Cloudflare cookie collects and anonymizes end user IP addresses using one-way hash so they cannot be personally identified. According to Cloudflare's infrastructure, service operates global network spanning 300+ cities worldwide processing traffic between users and BitPay website.

Cloudflare processes IP addresses and routing information, HTTP request headers, threat detection signals, cached content for delivery optimization, and SSL/TLS encryption for connections. Cloudflare maintains SOC 2 Type II, ISO 27001, and other security certifications, with data processing occurring across global network.

Marketing and Advertising Partners: According to Cookie Policy targeting cookies section, BitPay uses marketing partners for B2B advertising though specific partners not fully enumerated. LinkedIn explicitly mentioned as targeting cookie provider used to provide insight into user behavior responsive to marketing efforts, delivering marketing content including emails, white papers, webinars, etc. LinkedIn processes professional profile information, page interaction data, and advertising engagement metrics.

Email and Communication Services: According to typical business operations, BitPay necessarily uses email service providers for transactional emails (payment receipts, account notifications, security alerts, invoice notifications to shoppers) and marketing emails to merchants. Specific email service providers not disclosed in available documentation. Common choices for financial services include SendGrid, Mailgun, Amazon SES, or specialized transactional email platforms.

Support and Customer Service: According to support operations, BitPay provides customer support through email and support ticket system. Support infrastructure likely involves helpdesk platform such as Zendesk (mentioned in support documentation context of creating Zendesk account to view attachments), Freshdesk, Intercom, or similar. Support platforms process support ticket content, customer identifying information, problem descriptions, resolution notes, and support agent interactions.

Payment Network Relationships: For cryptocurrency payment detection, according to blockchain monitoring requirements, BitPay must monitor multiple blockchain networks for incoming payments. This may involve blockchain infrastructure providers (node hosting services, blockchain API providers such as BlockCypher, Coinbase Cloud, Alchemy, Infura) processing cryptocurrency wallet addresses, transaction hashes, block data, and payment confirmations. Specific blockchain infrastructure providers not disclosed.

No Public Subprocessor List or DPA: Unlike enterprise SaaS providers maintaining public subprocessor lists with change notifications, BitPay does not maintain publicly accessible subprocessor directory. No publicly available Data Processing Addendum document found in research despite GDPR requiring processors to execute DPAs with subprocessors. EU Privacy Notice references Standard Contractual Clauses for international transfers but does not provide DPA document or comprehensive subprocessor list.

According to EU Privacy Notice, BitPay may share personal data with other BitPay entities including to help detect and prevent illegal acts and policy violations, guide decisions about products, services, communications, and service providers helping with business operations and service delivery (cloud infrastructure, ID verification, due diligence solutions for KYC/AML). However, comprehensive list not provided.

Subprocessor Change Management: No documented subprocessor change notification process found in available materials. Typical enterprise DPAs provide 30-day advance notice before engaging new subprocessors with customer objection rights. Whether BitPay implements similar framework not disclosed in public documentation.

Comparison to Traditional Financial Services: BitPay's limited subprocessor disclosure reflects financial services industry norms rather than technology SaaS norms. Traditional banks and payment processors similarly do not publish comprehensive subprocessor lists. However, this creates transparency gap for customers evaluating GDPR compliance, data residency requirements, and privacy impact assessments.

BitPay's approach to international data transfer reflects position as US-headquartered financial institution with global operations. According to Privacy Notice and EU Privacy Notice, BitPay processes personal data internationally with headquarters in United States and European entity in Netherlands.

US Headquarters and Primary Processing Location: According to company structure, BitPay Inc. maintains headquarters in United States with primary data processing occurring in US infrastructure. This means personal data collected from merchants and shoppers globally is transferred to and processed in United States regardless of data subject location. According to Privacy Notice international transfer disclosure, recipients of disclosures are located in United States and elsewhere in world, including countries where privacy laws may not provide same level of protection as laws in country where data subject lives.

For European data subjects, this transfer from EU/EEA to United States requires appropriate safeguards under GDPR Chapter V. United States does not have adequacy decision from European Commission for general commercial data transfers (though EU-US Data Privacy Framework provides adequacy for certified companies). BitPay's participation in Data Privacy Framework not disclosed in available documentation.

Standard Contractual Clauses: According to EU Privacy Notice, BitPay complies with applicable legal requirements for protecting personal information transferred across borders including through use of regulator-approved Standard Contractual Clauses where appropriate. This indicates BitPay implements European Commission's Standard Contractual Clauses (Decision 2021/914) as transfer mechanism for personal data from EU/EEA to United States.

However, unlike many enterprise technology providers, BitPay does not publish Data Processing Addendum incorporating SCCs. Absence of publicly accessible DPA document means customers cannot review specific SCC implementation, annexes describing processing activities, or technical and organizational measures. Enterprise customers requiring DPA review for procurement or compliance purposes would need to request document directly from BitPay.

BitPay B.V. European Operations: According to Terms of Use and EU Privacy Notice, BitPay B.V. operates as Dutch entity subject to Dutch and EU laws including Dutch Act on Prevention of Money Laundering and Terrorism Financing and Dutch Sanctions Act. Office located in Amsterdam at Keizersgracht 520H, 1017EK, Amsterdam, Netherlands. This entity serves as Data Protection Officer contact point with email [email protected].

However, according to infrastructure and operational model, unclear whether BitPay B.V. processes European customer data entirely within EU/EEA or transfers to US systems. Financial services payment processing often involves centralized transaction processing even when local entities serve as contracting parties. Absence of clear data residency disclosure means European customers cannot confirm whether personal data remains in EU or transfers to US.

Onfido Data Residency Options: For identity verification subprocessor, according to Onfido documentation, service provides EU and US data center options allowing customers to satisfy data residency requirements. Workflow Studio can route verification checks to specific region when regulations require. EU/UK data residency guarantee ensures personal data collected in EEA or UK stays in-region unless Standard Contractual Clauses or equivalent safeguards in place.

Whether BitPay utilizes Onfido EU data centers for European merchants or routes all verification through US infrastructure not disclosed in available documentation. Best practice would be routing European merchant verification through Onfido EU infrastructure maintaining data within EEA.

Blockchain Technology and Global Data Flows: Cryptocurrency payment processing inherently involves global data flows through decentralized blockchain networks. When shopper pays BitPay invoice using Bitcoin, Ethereum, or other cryptocurrency, transaction broadcasts to blockchain network spanning nodes in jurisdictions worldwide. Transaction data including cryptocurrency addresses and amounts becomes part of public blockchain permanently recorded across distributed global infrastructure.

According to blockchain architecture, BitPay must monitor blockchain networks to detect incoming payments. This monitoring may utilize blockchain infrastructure providers (node hosting, blockchain APIs) operating globally. Payment confirmation involves analyzing transactions recorded on blockchain nodes worldwide. This creates unavoidable international data transfer inherent in cryptocurrency technology rather than discretionary business decision.

Banking Settlement International Transfers: For merchants receiving fiat settlements in currencies other than US dollars or from non-US banks, according to international payment infrastructure, settlements necessarily flow through international banking networks. SWIFT network spanning banks in 200+ countries processes cross-border payments. Correspondent banking relationships involve US banks, European banks, and banks in merchant jurisdictions cooperating to complete settlements.

These international transfers occur within financial services regulatory framework including SWIFT's oversight by central banks, anti-money laundering cooperation agreements between jurisdictions, and financial services specific data protection regimes. Banking transfers fall under different legal framework than general commercial data transfers—GLBA, Bank Secrecy Act, and financial services regulations rather than GDPR Article 45-46 transfer provisions.

No Regional Data Residency Options: Unlike cloud infrastructure providers offering regional deployments, BitPay does not offer data residency options allowing merchants to select geographic location for data processing. All merchants regardless of location utilize same centralized infrastructure. European merchant serving European customers cannot configure BitPay to process data exclusively within EU. Canadian merchant cannot restrict processing to Canada. All processing flows through BitPay's infrastructure with primary operations in United States.

Supplementary Measures: Following Schrems II decision requiring supplementary measures beyond SCCs, according to BitPay security framework, implemented measures include encryption in transit (HTTPS/TLS for all communications), encryption for stored data using modern cryptographic methods, access controls limiting personnel access to personal data, mandatory two-factor authentication for sensitive operations, SOC 2 audit providing independent verification of security controls, and AML/CFT monitoring reducing risk of surveillance-related access to transaction data (since suspicious activity screening may flag unusual access patterns).

However, BitPay has not published Transfer Impact Assessment evaluating US surveillance law risks (FISA 702, Executive Order 12333) and whether SCCs provide essentially equivalent protection to GDPR given US legal framework. European Data Protection Board guidelines recommend conducting and documenting TIA for transfers to United States. Absence of public TIA or detailed supplementary measures disclosure creates compliance evaluation challenge for European customers.

UK and Swiss Transfers: For transfers from United Kingdom, according to UK GDPR requirements, International Data Transfer Agreement (UK IDTA) or UK Addendum to EU SCCs provides lawful transfer mechanism. For Switzerland, Swiss Federal Act on Data Protection requires appropriate safeguards similar to EU framework. BitPay's implementation of Standard Contractual Clauses should be adapted with UK Addendum or Swiss annexes but specific documentation not publicly available.

GLBA and Financial Services Data Transfers: For US customers, international transfers governed by Gramm-Leach-Bliley Act financial services privacy framework rather than GDPR-style transfer requirements. GLBA does not prohibit international transfers but requires financial institutions to implement safeguards protecting customer information including contractual requirements for service providers. Banking regulations may impose additional requirements for international data transfers involving financial account information.

Customer Responsibilities: Merchants using BitPay for international commerce bear responsibility for complying with data protection requirements in jurisdictions where their customers (shoppers paying invoices) are located. If European merchant uses BitPay to accept payments from European shoppers, merchant must evaluate whether use of US-based payment processor complies with GDPR transfer requirements. Merchant-shopper relationship is separate from BitPay processing, but merchant's choice of payment processor affects data flow and compliance posture.

When developers and merchants integrate BitPay for cryptocurrency payment acceptance, they assume significant compliance responsibilities spanning payment processing, customer data protection, and regulatory obligations. According to Terms of Use, Privacy Notice, and regulatory framework, following developer responsibilities apply.

Regulatory and Licensing Compliance: Developers must understand that accepting cryptocurrency payments through BitPay does not eliminate merchant's own regulatory obligations. According to cryptocurrency regulation landscape, merchants accepting crypto may have state or local licensing requirements depending on jurisdiction, volume, and business model. Developers should consult legal counsel regarding whether business operations require money transmitter licenses, virtual currency business licenses (such as New York BitLicense), or other cryptocurrency-specific registrations independent of BitPay's licenses.

While BitPay holds FinCEN registration and state money transmitter licenses for its payment processing operations, these licenses cover BitPay's activities, not merchant's activities. Merchant selling goods or services for cryptocurrency serves different role than BitPay as intermediary payment processor.

KYC and Account Verification Preparation: Developers must prepare for BitPay ID verification requirements when transaction volumes exceed thresholds. According to verification requirements, $3,000 cumulative transaction value triggers verification for US merchants, €1,000 for EU merchants, and $10,000 general threshold. Developers should gather documentation before reaching thresholds including government-issued photo identification (passport, driver's license, national ID), proof of address documentation (utility bills, bank statements dated within recent months), business formation documents if merchant is legal entity (articles of incorporation, EIN letter, operating agreement), beneficial ownership information for corporate accounts, and selfie capability for biometric verification through Onfido.

Verification delays can interrupt payment processing. According to BitPay's process, verification typically completes within hours to days but complex cases involving document quality issues, name mismatches, or compliance reviews may take longer. Developers should initiate verification before reaching thresholds rather than waiting until payment processing suspended.

Customer Privacy Policy Requirements: Developers must maintain privacy policies explaining data processing in context of cryptocurrency payments. According to privacy law requirements, policies should identify BitPay as payment processor handling checkout transactions, explain that customer email addresses provided to BitPay for payment receipts, disclose cryptocurrency wallet addresses visible on public blockchains when customers pay, explain that BitPay processes payments as independent financial services provider, reference BitPay Privacy Notice for details on BitPay's data handling, describe merchant's own data collection beyond payment processing (shipping addresses, account creation, marketing preferences), explain retention periods for payment records, provide unsubscribe mechanisms for marketing emails, and include required disclosures under applicable privacy laws (GDPR for European customers, CCPA for California customers, other jurisdiction-specific requirements).

Refund Policy Implementation: Developers must establish clear refund policies considering cryptocurrency payment characteristics. According to refund framework limitations, cryptocurrency transactions are irreversible at blockchain level—refunds require BitPay to send new payment to customer, miner fees apply to refund transactions (by default deducted from refund amount received by customer unless merchant absorbs), exchange rate risk exists if significant time passes between original payment and refund (crypto price volatility may result in refund amount differing from original payment value when converted to fiat), and refunds processed through BitPay API or merchant dashboard rather than automatic chargeback system like credit cards.

According to Terms of Use, BitPay is not responsible for merchant refund policies or verifying policies conform to applicable law. Developers must ensure refund policies comply with consumer protection laws in relevant jurisdictions, clearly communicate refund terms to customers before purchase, process refunds promptly when required by policy or law, and maintain refund records for accounting and potential dispute resolution.

Customer Data Minimization: Developers should collect minimum necessary customer information for cryptocurrency checkout. According to BitPay invoice model, only email address required for BitPay to send payment receipt and track invoice status. Developers requesting additional customer information (names, phone numbers, shipping addresses) should do so based on legitimate business need (physical product shipping, customer service contact, account creation) rather than collecting expansively.

For merchants not shipping physical products (digital goods, services, donations), email address may suffice for checkout. Collecting unnecessary data creates privacy obligations, security risks, and potential regulatory burdens without commensurate business benefit.

Sanctions and Restricted Jurisdictions Compliance: Developers must implement appropriate geographic restrictions for cryptocurrency payments if business subject to US sanctions programs. According to Office of Foreign Assets Control requirements and BitPay Terms of Use, BitPay is subject to OFAC sanctions prohibiting transactions with certain countries, entities, and individuals. Merchants using BitPay similarly bear obligation not to facilitate sanctions violations.

Developers should implement IP address geolocation screening to block checkout from sanctioned jurisdictions (currently including Cuba, Iran, North Korea, Syria, regions of Ukraine, and other designated areas), review OFAC Specially Designated Nationals list if conducting high-value transactions, maintain transaction records adequate for sanctions compliance audits, and consult OFAC guidance for industry-specific sanctions requirements.

Cryptocurrency's borderless nature creates sanctions compliance challenges—merchant must implement controls preventing sanctions violations rather than relying solely on payment processor screening.

Tax Reporting and Accounting: Developers must implement appropriate tax treatment for cryptocurrency payments. According to US Internal Revenue Service guidance and international tax frameworks, cryptocurrency payments are taxable events with reporting requirements including calculating cost basis and capital gains for cryptocurrency received (if merchant accepts crypto directly), reporting gross proceeds from sales regardless of payment method, issuing 1099 forms to contractors paid via cryptocurrency if applicable, and maintaining transaction records including timestamps, exchange rates at payment time, cryptocurrency types and amounts, fiat settlement amounts, and fees paid to BitPay.

According to typical BitPay settlement model, merchant receives fiat settlement next business day with BitPay handling crypto-to-fiat conversion. This simplifies merchant accounting compared to holding cryptocurrency directly but still requires proper revenue recognition, reconciliation of bank deposits with sales records, and accurate tax reporting.

Integration Security and Best Practices: Developers must implement secure BitPay integration including storing BitPay API keys securely (environment variables, secure credential vaults, never in version control repositories), implementing proper authentication for API calls, validating webhook signatures to confirm payment notifications originate from BitPay, implementing idempotency to handle duplicate webhook deliveries gracefully, maintaining HTTPS/TLS for all communications with BitPay API, implementing proper error handling for payment failures or network issues, and testing thoroughly using BitPay test environment before production deployment.

According to BitPay developer documentation, test merchant accounts available without KYC validation for integration testing. Developers should complete integration testing in test environment before moving to production, utilizing test environment API credentials separate from production credentials.

Shopper Experience and Disclosure: Developers must ensure clear disclosure to shoppers about cryptocurrency payment process including displaying accurate prices in shopper's expected currency, disclosing cryptocurrency payment option clearly during checkout, explaining exchange rate locks and payment windows (typical BitPay invoice provides 15-minute payment window with locked exchange rate), providing clear instructions for completing cryptocurrency payment, explaining that cryptocurrency transactions are irreversible (shoppers should verify payment details carefully), and making customer service contact information prominent for payment issues.

According to user experience considerations, cryptocurrency checkout may be unfamiliar to many customers. Clear instructions, expected wait time for blockchain confirmations, and responsive customer service help reduce payment abandonment and support requests.

Dispute and Chargeback Handling: Developers must implement dispute resolution processes appropriate for cryptocurrency payments. According to BitPay framework, cryptocurrency payments lack traditional chargeback mechanisms but disputes still occur including customer claims of non-delivery, product quality issues, unauthorized purchase disputes, and requests for refunds outside policy terms. Merchants bear responsibility for reasonable dispute resolution, documenting dispute communications, processing legitimate refunds appropriately, and maintaining customer service quality to minimize disputes.

According to Terms of Use Section 12.1, BitPay reserves right to terminate accounts receiving excessive Shopper or Donor complaints. Merchants should treat dispute resolution as business priority to maintain BitPay account good standing.

Transaction Monitoring and Fraud Prevention: Developers should implement fraud prevention measures recognizing cryptocurrency payment characteristics including monitoring for velocity anomalies (unusual order frequency or volume from single customer), verifying shipping addresses for physical goods (confirming address valid, watching for freight forwarders suggesting reshipping schemes), watching for email pattern anomalies (temporary email addresses, pattern suggesting automated account creation), implementing CAPTCHA or similar anti-bot measures at checkout, and maintaining blocklists of problematic cryptocurrency addresses if patterns emerge.

While BitPay implements platform-level AML monitoring, merchant-level fraud prevention remains important for protecting business from losses due to fraudulent orders, chargebacks (if any traditional payment methods also offered), and reputational harm.

Record Retention for Compliance: Developers must maintain adequate records for tax compliance, legal defense, and regulatory obligations including transaction records (amounts, timestamps, cryptocurrency types, wallet addresses, exchange rates), customer communications (emails, support tickets, dispute correspondence), refund records and rationale, financial reconciliation documentation tying BitPay settlements to accounting systems, and API logs or integration documentation sufficient to reconstruct transaction flows if questioned in audit or legal proceeding.

According to typical financial services recordkeeping requirements, seven years considered prudent retention period for tax purposes in US though some states require longer retention. GDPR and privacy laws may require deletion after purpose fulfilled, creating tension between compliance frameworks that developers must navigate based on specific circumstances.

Ongoing Monitoring of BitPay Changes: Developers should monitor BitPay communications for Terms of Use updates, fee structure changes, supported cryptocurrency additions or removals, API deprecations or new versions, security advisories or integration best practice updates, and regulatory developments affecting cryptocurrency payments.

According to Terms of Use, BitPay may modify terms with notice. Developers should review changes to assess whether modifications affect integration functionality, compliance obligations, or cost structure.

Core Documentation:

Product and Business:

Developer Resources:

Support:

This Privacy & Data Handling Profile provides comprehensive overview of BitPay's data processing practices as documented in Privacy Notice, EU Privacy Notice, Terms of Use, Cookie Policy, and publicly available compliance documentation. BitPay represents cryptocurrency payment processor operating under financial services regulatory framework fundamentally different from typical technology SaaS providers.

Critical considerations for BitPay implementation include understanding that BitPay operates as regulated financial institution subject to Bank Secrecy Act, USA PATRIOT Act, and OFAC sanctions rather than general-purpose payment processor. Mandatory KYC verification requirements trigger at transaction volume thresholds ($3,000 for US, €1,000 for EU, $10,000 general) requiring government ID, proof of address, and biometric verification through Onfido platform. These are regulatory compliance requirements, not discretionary business decisions—BitPay legally cannot provide services without customer identification program.

Gramm-Leach-Bliley Act applicability means much of BitPay's data processing exempt from California Consumer Privacy Act and potentially other state privacy laws. Financial services data governed by specialized regulatory framework prioritizing AML/CFT compliance, sanctions screening, and fraud prevention over general privacy rights. Extended data retention required by Bank Secrecy Act (typically five years after account closure) limits data deletion rights even under GDPR—regulatory retention obligations override right to erasure.

US-based processing with limited international data transfer disclosure creates compliance evaluation challenge for non-US merchants. All data processes through US infrastructure regardless of merchant or customer location. Standard Contractual Clauses referenced for EU transfers but no publicly accessible Data Processing Addendum document available. European merchants should request DPA directly from BitPay for GDPR compliance assessment, conduct Transfer Impact Assessments evaluating adequacy of SCCs given US surveillance law environment, implement supplementary measures if TIA reveals risks, and document basis for determining transfers lawful under Chapter V.

Onfido identity verification subprocessor maintains strong security posture with ISO 27001 and SOC 2 Type II compliance, EU and US data center options for regional processing, but specific routing for BitPay customers not disclosed. European merchants should confirm whether verification routed through Onfido EU infrastructure or transferred to US. Biometric data processing raises GDPR Article 9 special category considerations requiring explicit consent or substantial public interest legal basis.

Limited subprocessor transparency compared to enterprise technology vendors. No publicly maintained comprehensive subprocessor list, no documented change notification process, no detailed processing activity descriptions for each subprocessor. Financial services industry norms differ from technology SaaS norms but create information gaps for customers conducting privacy impact assessments or vendor due diligence. Enterprise customers requiring detailed subprocessor documentation should request supplementary information directly from BitPay.

Blockchain technology inherent transparency means cryptocurrency addresses and transaction amounts permanently recorded on public blockchains visible to anyone. Shoppers paying BitPay invoices should understand wallet addresses become part of public blockchain record. While addresses not directly linked to identity without additional information, blockchain analysis companies track transaction flows enabling potential de-anonymization. This differs fundamentally from traditional payment card processing where transaction details remain private between parties.

Cryptocurrency payment irreversibility requires clear refund policy communication. Unlike credit card chargebacks occurring without merchant consent, cryptocurrency refunds require merchant to initiate new payment to customer. Miner fees apply to refunds (typically deducted from amount customer receives). Exchange rate fluctuations between original payment and refund create potential value differences. Merchants should clearly disclose refund terms before purchase and implement responsive refund processing to maintain customer satisfaction.

Sanctions compliance responsibility shared between BitPay and merchant. While BitPay implements OFAC screening, merchants also bear obligation not to facilitate sanctions violations. Developers should implement geographic restrictions blocking checkout from sanctioned jurisdictions, review high-value transactions for sanctions compliance, and maintain adequate records for potential regulatory examination. Cryptocurrency's borderless nature increases sanctions compliance complexity compared to traditional payment processing.

Tax reporting obligations differ from credit card processing. While BitPay simplifies merchant accounting by providing fiat settlements rather than cryptocurrency holdings, merchants still must report cryptocurrency payment revenue accurately, maintain records of exchange rates at payment time, issue appropriate tax forms for contractor payments via crypto, and consult tax advisors for jurisdiction-specific requirements. IRS treats cryptocurrency as property rather than currency creating unique reporting obligations.

SOC 2 audit provides independent verification of security controls but full report not publicly available. Security infrastructure includes multi-signature wallets, mandatory 2FA, local password storage, and transaction encryption. However, BitPay has not disclosed ISO 27001 certification for BitPay Inc. itself (only for subprocessor Onfido) or published detailed security architecture documentation. Enterprise customers requiring security validation should request SOC 2 report under NDA.

Customer service and dispute resolution important for maintaining BitPay account good standing. According to Terms of Use, excessive shopper complaints may result in account termination. Merchants should prioritize responsive customer service, clear communication of refund policies, and reasonable dispute resolution. Unlike traditional merchant accounts where disputes handled through payment network processes, cryptocurrency merchant accounts rely on direct merchant-customer resolution with BitPay acting as intermediary.

Developer integration testing should utilize BitPay test environment before production deployment. Test accounts require no KYC validation enabling immediate integration development. Production deployment should follow comprehensive testing including webhook handling, error scenarios, payment timeout situations, and refund workflows. Moving to production too quickly without adequate testing creates payment processing failures affecting customer experience and revenue.

The information presented here derives from BitPay official documentation including Privacy Notice, EU Privacy Notice, Terms of Use, Cookie Policy, and regulatory compliance disclosures as of May 2026. However, documentation comprehensiveness significantly limited compared to typical enterprise technology providers. No publicly accessible Data Processing Addendum, no comprehensive subprocessor list with change notifications, no detailed data residency disclosures, and limited security architecture documentation create evaluation challenges for enterprise procurement and compliance assessment.

Developers and merchants should request supplementary documentation directly from BitPay including Data Processing Addendum with Standard Contractual Clauses, comprehensive subprocessor list with processing descriptions, detailed data residency and international transfer documentation, SOC 2 report under NDA, specific Onfido routing configuration for their region, and clarification of BitPay B.V. processing activities versus US-based processing. Monitor BitPay communications for Terms of Use updates, regulatory changes affecting cryptocurrency payments, and integration best practice guidance. Consult legal counsel specializing in cryptocurrency regulation, financial services compliance, and international data transfers for complex compliance questions specific to business model and customer jurisdictions.

Document Prepared: May 2026

Primary Sources: BitPay Privacy Notice, EU Privacy Notice, Terms of Use, Cookie Policy, Onfido Technical Documentation, Financial Services Regulatory Framework

Intended Use: Educational and informational purposes for developers and merchants evaluating BitPay cryptocurrency payment processing integration

Not Legal Advice: Consult qualified legal counsel specializing in cryptocurrency regulation, financial services compliance, and international data protection for guidance specific to your business model, transaction volumes, and customer jurisdictions

Documentation Limitation Notice: BitPay's public documentation less comprehensive than typical enterprise technology vendors—request supplementary materials directly from BitPay for enterprise procurement and detailed compliance assessment