Privacy notice
Last updated October 25, 2026
Who we are
Mintage Pay is a service of Mintage Pay LLC, a Wyoming limited liability company ("Mintage Pay", "we").
What we collect
- Applications: your business name, website, email, platform, sales range, what you sell, country, and the IP address and browser the form was sent from.
- Merchant accounts: your login email and the settings you choose.
- Payment records: invoice data (amounts, status, timestamps and any order details your store sends, such as order number and customer email), plus the public blockchain data of each payment (wallet addresses and transaction IDs), so we can confirm payments and show sales and fees. Paying wallet addresses are checked against public US sanctions lists.
- Orders from product links: when you buy through a store's product link, the details the store asks for (your email, and if requested your name, phone, shipping address and an answer to one question). They are stored encrypted, shared only with that store so it can deliver your order (including copying the order into the store's own e-commerce system when the store connects one), and used to email you a receipt. We also keep a one-way code of your IP address and email to limit abuse; we never store your IP address itself.
We do not collect full card numbers, card security codes, seed phrases or private keys.
Card payments: when a shopper pays by card, Apple Pay or Google Pay, we keep a record of that card purchase: the card brand and its last 4 digits, the wallet type (for example Apple Pay), the total and card fee shown, the card provider's reference for the purchase and the shopper, the shopper's IP address and browser, and the statement name and notes shown before they paid. If the store did not give us the shopper's email, we also keep the email they typed on the card page with the order, to send their receipt and the updates on a refund they ask for. We use it to answer refund requests and card disputes, and to give the store the details a dispute needs. The IP address and browser are deleted after 550 days. If a shopper disputes a card charge, we keep a one-way code of the email on the order (or the one verified with Coinbase), of the wallet and of the card provider's customer reference, and with these we may refuse card payments from that shopper on any Mintage Pay store. Paying in crypto stays available to them.
Refund requests: if you ask a store for a refund on our refund page, we keep your reason, your message, the amount and the refund address you give, share them with that store, and email you about your request.
On the payment page we record, without any personal data or IP address, which steps of a payment were reached (for example that a payment method was chosen or a wallet button was used) and the type of device and its operating system (for example an iPhone or a Windows computer), so we can see where payments fail and improve the page. These records are deleted after 180 days.
Website visits: on this website (mintagepay.com and its developer docs, not the payment page or the dashboards) we use Google Analytics to count visits, see which pages are read and where visitors come from, and count application forms sent (never their contents). Google receives the page address, the referring page, your browser and device type and your approximate location; Google Analytics does not store your IP address. Visitors in the European Economic Area, the UK and Switzerland are counted without cookies. Advertising features are off. Google handles that data under its own privacy policy. We also use Cloudflare Web Analytics, which counts page views without cookies and without identifying visitors, and Microsoft Clarity, which records how pages are used (clicks, scrolling and mouse movement, with every form field hidden) so we can see where the site is confusing. Microsoft handles Clarity data under its own privacy statement. Our web server keeps a log of website requests (the page, the time, the referring page and the browser name, without your IP address) for 30 days, to see how search engines and AI assistants read the site.
Why we use it
To review applications, run your account, calculate and bill fees, keep an audit trail of every fee and correction, secure the service, and meet legal obligations.
Who we share it with
We do not sell personal data. We share it only with the providers that host the service, and with authorities when the law requires it.
If a merchant chooses bank payouts, we send Bridge (Bridge Building, Inc., a Stripe company) the business's legal name, the email and country it gives us, and the bank account it enters, so Bridge can verify the business and pay out to that account. The bank account number goes straight to Bridge: we keep only the bank name and the last 4 digits. Bridge handles that data under its own privacy policy.
If a shopper pays with another token or chain, we ask LI.FI (li.fi) for a swap and bridge route. LI.FI receives the shopper's wallet address, the networks and tokens, the amount and the store's payment address, and later the transaction ID so we can follow the transfer. LI.FI handles that data under its own privacy policy. We keep the paying wallet address with the payment record; a price that was never used is deleted after 30 days.
If a shopper pays with Apple Pay or Google Pay, they sign in with their email through Coinbase (Coinbase, Inc.), which creates a wallet that is theirs, and buy the USDC from Coinbase into that wallet. Coinbase receives that email, the phone number and email the shopper verifies, the amount and the wallet address. Coinbase handles that data under its own privacy policy. We keep a keyed hash of the shopper's Coinbase user ID to limit repeated attempts; it is deleted after 30 days.
If a shopper pays by card on a payment page that offers it, Privy (Privy, Inc., a Stripe company) creates a wallet for them in that browser, and Stripe (Stripe, Inc.) sells them the USDC into that wallet through its crypto on-ramp and Link. Stripe receives the card or Google Pay or Apple Pay details, the name, address, email and phone number the shopper enters, the amount and the wallet address; Privy receives the wallet address and the technical data its service needs. Each handles that data under its own privacy policy. We never receive the card number. From the payment page we receive the wallet address, the payment that wallet makes to the store, and the card purchase record described above.
If a shopper pays with another token on Solana, we ask Jupiter (jup.ag) for a swap route. Jupiter receives the shopper's wallet address, the tokens and the amount. Jupiter handles that data under its own privacy policy. We keep a log of the transactions we prepared, with that wallet address, for 90 days.
If a shopper turns on automatic payments on Solana, their subscription is recorded on the public Solana blockchain by the Solana Foundation's Subscriptions program: their wallet address, the store's plan and each payment are visible on chain, as for any blockchain payment.
How long we keep it
Fee and payment records are kept for as long as accounting and tax rules require. Applications that do not become accounts are deleted within 12 months. Shoppers' order details from product links (name, phone, address, email) are deleted 2 years after the order; the store may keep its own copy under its own policy. The IP address and browser kept with a card purchase are deleted after 550 days, the longest time a card dispute can be opened.
Your choices
You can ask for a copy of your data, a correction, or deletion where the law allows, by emailing hello@mintagepay.com.
Contact
Postal address: Mintage Pay LLC, PO Box 273, Hankinson, ND 58041, USA.
Cookies
This website uses Google Analytics cookies (named _ga and _ga_ followed by an ID, kept up to 2 years) and Microsoft Clarity cookies (_clck, kept up to 1 year, and _clsk, kept 1 day, plus Microsoft's own cookies on clarity.ms) to tell new visits from returning ones, except for visitors in the European Economic Area, the UK and Switzerland, who get no analytics cookies. The payment page sets no tracking cookies. The merchant dashboard uses one essential cookie to keep you signed in.