Setting up your own crypto payment system?

Scorpion Ghost said:

Yeah it was nice I had a good time with it.

I mean, it's stored safely and securely and used only for verification purposes. It's is certainly NOT used for sexual deviant purposes. You can trust our company, dear sir

Wanna check out my amazing crypto payment processor that's gonna out-compete them all and land me in prison for 100,000 years?

Click to expand...

Not for 100k years these are too low. 1 mil years are more appropriate xD.

Scorpion Ghost said:

I've been receiving crypto payments on Coinpayments for years, and suddenly they want KYB, asking me for a bunch of info which I don't have. I just have a website and I sell services on it. There are no contracts, invoices, registered business, and all that insanity.

I sent them the info they requested and explained the situation, but they may reject me. And seeing as we're talking about crypto, not a bank, I'm tempted to create my own payment gateway thing for my website. Crypto is the one payment method where I don't have to deal with sending my dick pick while erect with a ruler next to it while standing on my head with my thumb in my mouth.

Did anyone set up their own payment gateway? Is it hard? Any advice?

Click to expand...

Maybe you should switch to another crypto payment processor which doesn't require kyc because making your own might not be that hard due to ai but it is surely a headache to now learn a lot of new information to get the same amount of money. You could what rdp sellers use like crazy rdp.

I built my own instead. If you're only accepting crypto for your own services, it's pretty straightforward: generate a unique address per order, watch for confirmations, then mark it paid. No surprise KYB, but security is on you.

Building your own from absolute scratch is a waste of time. If your site runs on WordPress /WooCommerce, BTCPay Server has an official plugin. Money goes directly to your private keys and no one can freeze your account or demand business registration papers

The happy path of rolling your own is genuinely easy: derive an address per order, watch for confirmations, mark it paid. What you're really buying from a processor is the tail. Underpayments, someone sending on the wrong network, a payment landing four days later against an expired order, a customer who insists they sent it.

We take crypto for a software business and nearly all of the support time goes to that tail, not to the watching. If you self-host, decide your policy on underpayment and late payment in writing before launch, because you'll meet both in the first month.

The other half of your problem is worth naming separately. Providers tighten their requirements over time, so whoever you move to can ask the same questions a year from now. The durable fix isn't a better provider, it's making that part swappable: keep order state in your own system and treat the provider as something that only reports paid or not paid. Then changing rails takes a day instead of a rebuild.

Best,
Floqal