2,495 karma · joined February 8, 2012
I don't think this is really true? These are not serially incrementing, they just indicate the time it happened. If you have an ID that you know exists, having the ability to know _when_ it was created is very rarely meaningful.
What could present more of a risk is being able to predict a large part of IDs that will be created. Even then though, you shouldn't depend on your IDs for secrecy - best to ensure the IDs are never used as protection by themselves (ie treat them like they're just a simple autoincrementing number, even if they're not)
They are phishing resistant, even when using the cross-device QR code thing, but that does rely on some base level of trust in the user agent
At the end of the day though, if the browser is the malicious actor, there's simply nothing you can do. That is not a realistic or defensible scenario in most threat models
Passkeys do represent an enormous improvement in security for users, including in the scenario you've highlighted
I know in traditional auth setups, that kind of situation does tend to invite additional concerns, but (again assuming you trust the user agent) FIDO2 still provides full protection when that's happening
And then "error" as - "things are not okay, a developer is going to need to intervene"
And errors then split roughly between "must be fixed sometime", and "must be fixed now/ASAP"
https://factmyth.com/factoids/there-are-no-straight-lines-or...
Had to wait a few days for recurring/subscription payments to be "approved", but going great since then
We noticed is that it doesn't expose any info about the region/country of the connected account, so we had to make a little adjustment to stop relying on that
Also I think the pricing is a little on the high side, but PayPal people do really seem to like PayPal so not really a concern
Very smooth on the whole
But that actually changed extremely recently. PayPal is now fully supported with Stripe, even payment settlement happens in Stripe, Connect is supported etc.
https://stripe.com/docs/payments/paypal
Its availability is limited - based on the merchant's Stripe account. It's not available in the US yet, but I can't imagine it'll be far behind. For EEA + UK + Swiss Stripe accounts, you can accept PayPal for US customers
It seems that it was launched very quietly, not crystal clear why. Maybe PayPal are trying to avoid cannibalisation of their own payment processing services
I don't think Apple are aiming to change that with this
1. you can charge any amount - the amount shown in the Apple Pay UI is arbitrary
2. you can make multiple charges, also of any amount (e.g. for a subscription)
It is tokenized, but practically it's just a card number you can charge like any other card number. It's also typically linked back to the original PAN, so multiple payments can be correlated together with ease
> generally regarded as seven in number, _including their related islands_, continental shelves etc.
Or you could release a new package manager which does provide support for that functionality, build out a team of maintainers, and stay on top of all the releases
So get it well known in the SD community -> maybe sell more laptops
e.g. Sofort is run by Klarna for some reason - https://www.klarna.com/pay-now/business/merchant-support/wha...
So it seems conceivable that they have options to process regular card payments too