Connect CoinPayments

Why CoinPayments

100+ coins at 0.5%, and one technical advantage worth knowing: CoinPayments' hosted checkout is a plain link with the price in it. That makes it the only crypto provider here whose buy button is a reusable URL — it works forever and costs no API call each time someone clicks.

Where to get the four values

Merchant ID — coinpayments.net → Account Settings → Merchant Settings, at the top.

API public key and API private key — coinpayments.net → Account → API Keys → Generate New Key. Give it permission to read basic account info. The private key is shown once.

IPN secret — back on Merchant Settings. Invent a long random string, paste it into the IPN Secret field there, and paste the same string into kitty. While you are on that page, set the IPN URL to the webhook URL kitty gives you.

Connecting

Settings → Connections → Take payments → the CoinPayments card → Connect → fill the four fields → Save and connect. Test connection comes back naming your merchant account.

The webhook, which is not optional

kitty needs CoinPayments 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 coinpayments.net → Account Settings → Merchant Settings → IPN URL.

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.

A second check kitty makes

Beyond verifying the signature, kitty checks that the merchant id on every incoming notification matches yours. A correctly-signed notification for somebody else's merchant account is refused, not recorded.

What it can and cannot do here

One-off payments only — no subscriptions, no failed-payment recovery. CoinPayments only reports a payment as complete once the full amount has arrived, so there is no partial-payment case to worry about. Refunds are handled in CoinPayments.

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.