Connect BitPay

Why BitPay

BitPay is the crypto processor for people who do not actually want to hold crypto. It can settle to your bank account in your own currency, so a customer pays in bitcoin and you receive dollars, euros or pounds. The price swing between the two is BitPay's problem, not yours.

Configure that under Settings → Payouts in BitPay before you take a payment.

Before you start

BitPay verifies businesses before enabling live invoices. Start that early — it is the slowest step here.

Where to get the token

bitpay.com → Payment Tools → API Tokens → Add New Token.

Choose the Point of Sale facade. This matters and it is the one thing people get wrong: a Merchant facade token requires every request to be cryptographically signed with a key pair, which kitty does not do. A Point of Sale token can create invoices without signing, which is exactly and only what kitty needs.

Give the token a name you will recognise, leave "Require Authentication" off, and copy the token string.

Connecting

Settings → Connections → Take payments → the BitPay card → Connect → paste the token → Save and connect.

Test connection here is honest about its limits: a Point of Sale token can only create invoices, so there is no read for kitty to test with. The test confirms BitPay is reachable and tells you plainly that the token itself is proven the first time you put something on sale.

How kitty verifies a BitPay payment

BitPay's notifications are not signed. So rather than trusting the message, kitty reads the invoice id out of it and fetches that invoice back from BitPay on your own token. Only what BitPay itself serves is ever acted on. A forged notification cannot name an invoice that does not exist.

The webhook, which is not optional

kitty needs BitPay to tell it when someone pays. Without that, the checkout takes the money and no order, customer or revenue figure ever appears in kitty.

On the connected card, press Webhook URL, copy it, and paste it into bitpay.com → Payment Tools → Notification URL, or per-invoice in your BitPay settings.

Treat that URL like a password — anyone holding it can post events at this venture. It never expires; you rotate it by disconnecting and reconnecting. Deliveries are capped at 300 a minute per venture.

What it can and cannot do here

One-off payments only. No subscriptions, no failed-payment recovery. Refunds are issued in BitPay and recorded here.

After it's connected

Test connection proves the key works right now, and names the account it reached — so a member with two logins can see they pasted the wrong one. Do that before you put anything on sale.

Then, in Where new checkouts go, pick this provider on its own or One page, every method, which offers every provider you've connected on a single page and quietly hides one that starts failing.

Anything already on sale keeps the provider it was armed on. A price, once created at a provider, cannot be moved — so to switch, open the venture's Revenue tab, Take off sale, then put it back on sale.

How the keys are stored

Encrypted at rest with AES-256-GCM, used server-side only, never returned to the browser, never written to a log, and never shown again after saving.

Payment keys are scoped to a venture or the whole workspace, never to you personally — two businesses in one workspace settle into two different bank accounts, so a personal key is refused for money on purpose.