I wonder if PayPal did the old “Your account is locked and we’re keeping your money” thing to GitHub too, as they have too so many others.
PayPal just happens to be one of the most used online payment providers, being very trigger happy on this one due to pressure from regulators. This makes PayPal unideal for any businesses that deal with digital goods.
Payment processors will ALL (including stripe, authorize, adyen, etc) lock your account (with your money still in it!) if:
1) You're taking money for a product that will be delivered in the distant future (like tickets for an event, or preorders)
2) Your account has a sudden change in ticket size or quantity
3) You're violating their TOS. On HN that might look like a service that winks about piracy, or being a spamming tool.
Ever since I learned about this ~10 years ago, I've been looking into the details every time someone gets their account shut down, and it's always the above. The way people describe what happened to them to carefully leave out one of those points prevents it from ever being shocking.
their one benefit - ubiquity - isn't even earned. no, they were just early to the scene 20 years ago, then held their nerve until about 2010 after which the major online players pretty much haven't changed. fuck the current online eco[nomic]-system. the network effects of familiarity nearly always trump competence or quality
my advice: never ever have money in your account. it's just too tempting for them. if you're taking payments, auto-transfer them out. if you use it pay for things, use it via a card. since I realised this, I've not once had to unlock my account, no unsolicited two-factor, not even a dodgy notification. it's almost like they have nothing to gain from locking it anymore :o
Braintree might have been decent as a startup/small player, but getting pushed to the same stage as Stripe make them look struggling IMO.
Used to interface with Adyen and Stripe in the past, and PayPal's Braintree part is way laggier and prone to errors.
>Several of you have reached out asking why we don’t support certain platforms (including PayPal and Venmo) natively in FUNDING.yml, the file for configuring a “Sponsor” button on a repo. Great question!
>We decided to leave PayPal, Venmo, and others out of the set of supported platforms because there is a less explicit social contract for where the money is going compared to platforms like Patreon, Open Collective, Tidelift, and Community Bridge, to name a few of the platforms we do support. Those are community, creator, open source, or developer-focused—and they make it clear that you are supporting the work of the person or team developing code in that repository.
>We support custom fields so we can monitor funding methods we might not have known about, and iterate accordingly. Good news is you can put PayPal—or any other link—in the custom field, too.
>They wouldn't have that option if PayPal had locked the GitHub Sponsors PayPal account.
Does that lock any incoming money or just taking the money out of the account ?
if (file.getName().contains("trojan")) {
antivirus.flag("malware");
}