New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Oh nothing, but why would a canadian company use a criminal hosting company and IP addresses from a shady company.
We require it only once for merchant onboarding.
They don't. And they haven't for a long time. Crypto is traceable and if you receive ransom funds or funds from the dark market and try to send them to an exchange, the exchange is more likely to block the transaction and request KYC/SOF documentation.
It's easier to say what we don't accept for onboarding: https://pawpayments.com/docs/terms (§5.6). We'll be happy to provide the service for anything else not in those terms.
It's crypto. Of course it's shady.
There was a recent report of Russians operating a money laundering operation through Canada. I'm sure there's more.
Cryptomus/Heleket? lol
Doesn't have to be... but yeah, welcome to lowendhackerforum.
Please add fiat payments via credit and debit cards. In its current form, the service does not offer much value. The same functionality can be implemented with a self-hosted solution or simply by using NOWPayments directly.Please add fiat payments via credit and debit cards. In its current form, the service does not offer much value. The same functionality can be implemented with a self-hosted solution or simply by using NOWPayments directly.
Card payments are on our roadmap for Q4 2026 – Q1 2027, and we'll announce them as soon as they're live. If there's anything else that would make PawPayments more useful for you, please let us know.
The other direction? Visa to you, then you pay a provider here in crypto?
Extra-non-anonymous on a system that stores every transaction FOREVER
Yes, that's coming soon. Card payments will be handled by our partners rather than by us directly: the customer pays by card, and the provider receives crypto as usual.
I'd much rather not KYC 95% of the time than have to KYC 100% of the time
Following up on the requests above: card payments are now live on the PawPayments checkout.
Your customer pays the invoice with a debit or credit card right on our checkout, and you receive the invoice amount in crypto on your PawPayments balance, like any other payment. There's also nothing to set up. Card processing is handled by Stripe.
Supported cardholder locations for now:
We're also in talks with other payment partners to bring card payments to more countries, so stay tuned.
Fair enough. 'Not very smart' is a working hypothesis that we're actively trying to disprove, and here's today's evidence.
The old setup was chosen for DDoS capacity, not how it appears in whois. This was a rookie mistake on LET's part, where whois is apparently part of the threat model. There was also a less cosmetic problem: when under attack, the upstream's anti-spoofing check would reset the initial TCP connection of every new client, meaning that API clients would have to retry. So you were right that it had to go, just for slightly different reasons.
As of today, PawPayments and the API are hosted by OVHcloud on the 139.64.146.0/24 network. This is a direct ARIN allocation, registered to PawPayments Inc. in Toronto. In other words: a Canadian company, on its own Canadian IP block, with nothing shady left to find in whois.
We hear every poster here, including the ones who think we're not very smart. Especially those, actually: you just got us a whole infrastructure migration. Keep it coming.