edwinwee

Great to hear! BBPOS is perfect for iOS projects.

Besides the look, Stripe Reader works a bit differently—it can be docked on a counter or mounted on iPad/iPhone.

We’re working on Europe now and Terminal will available soon! Could you email me and I can keep you in the loop? edwin@stripe.com

That's a neat idea! Adding to the list.

(I work at Stripe.) Keep in mind that Stripe Terminal has upfront pricing: there are no additional software, PCI compliance, or monthly fees (or even equipment lease payments!). When factoring in these additional fees that many legacy players charge on top of the payment processing, Terminal oftentimes has more favorable pricing (along with working alongside your existing online Stripe transactions).

If you want funds in minutes, we have Instant Payouts in the US, Canada, and Singapore now, which lets you cash out to a debit card right away for a small processing fee. Our standard bank transfers are limited by existing banking infrastucture (e.g. the ACH network), but most transfers land within 2 days.

For BINs support—I'm sorry for those issues. Would you be able to email me and I can see if we can work on this? edwin@stripe.com

(I work at Stripe.) The offerings are meant for different use-cases. Stripe Terminal’s great for developers looking to deploy in-person payments at tech-forward companies. Square’s great for coffee shops and other SMBs!

Just an update on this—we've some changes in flight. Accessing sensitive verification results like date of birth, extracted document numbers, or collected images will soon require the use of restricted API keys. (More at https://stripe.com/docs/identity/verification-sessions#resul....) Thanks again for your feedback. I'll shoot you an email to chat more too.

To be clear, this isn't entirely true for all situations (sorry). Stripe verifies identities as a service provider (or processor) for the business that's using Identity. Stripe may be either a controller or a processor of data depending on the purpose of data processing (https://support.stripe.com/questions/managing-your-id-verifi...).

Hm! Could you email me with more on the device and browser versions? edwin@stripe.com

Edwin from Stripe here. The two cases are actually very similar. If you want to avoid ID documents ever being stored on your servers, Identity makes it easy to do that. (Just as Elements/Stripe.js makes that easy for card numbers.) On the other hand, if you want to score card numbers or ID documents (and there are sometimes good reasons for doing this!), Stripe makes that straightforward.

Liveness check is coming soon!

At the moment we take live photos of the individual to help confirm that there’s a real person behind the camera.

Identity is the step that comes after Sift (or Stripe Radar).

If Sift flags that a user may be suspicious, you may need to collect more information about them to confirm if they are legitimate or not. That’s where Identity comes in.

Oftentimes, this is handled manually via an ops team asking a user to reply with a photo. Instead they can collect this automatically by surfacing Stripe Identity.

Since we are storing these IDs on behalf of businesses using Identity, we need to retain non-biometric information for a period of time to support their use cases.

For example: KYC is a core use case for identity, which requires us to retain ID information for audit purposes.

For businesses who don’t need to keep the ID for as long, we provide a deletion API that lets them automatically delete the IDs from our system.

Identity was built in-house over the last decade from learnings from Stripe’s experience as a payment company.

We’ve invested heavily in creating an end-to-end verification product with an ergonomic API, responsive capture experience, and advanced fraud detection and verification capabilities.

Scaling ID verification globally also means working with others—we supplement our homegrown system with a number of partners for the best experience for the user. (e.g. Analogous to Stripe credit card payments, we also work with banking institutions.)

1. Stripe has strict access controls—only those working on Identity/verifications can access the data.

2. Biometric data is not stored! It’s gone from our systems within 48 hours (usually in just minutes).

3. We think this’ll actually make the state of global privacy better—rather than having individuals collect, and verify your ID, Stripe will securely handle verification.

Neat idea and something we’ll think about.

Stripe supports the legal processing and transfer of data by our users — and EU requirements are top of mind. (Feel free to me at edwin@stripe.com if you have more questions.)

We are very specific about collecting consent before doing anything with your data. We ask for permissions before beginning the verification process, and if you consent, we will only use your biometric identifiers for the verification itself. (And again, those identifiers—which contain the most sensitive info—aren't stored.) Specifically, we ask for an additional level of permissions before conducting any additional biometric analysis. https://support.stripe.com/questions/common-questions-about-...

Verifications typically happen in 2 minutes, oftentimes 30 seconds (for common IDs like state driver’s licenses). And we’re working on making this faster!

Chat apps use Identity to verify bots and prevent bad bots from spamming real users. And shipping services use Identity when a user is suspected as a fraudster—to double check before creating fraudulent shipping labels.

This is a small localization bug that we’re fixing now (the pricing section doesn’t properly show for countries where Identity isn’t available in yet), but you can see pricing for the US at https://stripe.com/en-us/identity#pricing.

It’s not really a “trend”—if you think about it, ID verification is already required when checking into hotels, buying alcohol, or when visiting a bank teller.

As more commerce moves online, Stripe Identity was built to significantly reduce the number of organizations and humans that would touch your ID—in a faster, secure way that’s hosted by Stripe (https://support.stripe.com/questions/common-questions-about-...).

We are also very direct about collecting consent: https://support.stripe.com/questions/common-questions-about-....

Yes, we’ve spent a lot of time on the scanning logic—especially to help guide users through photo-taking, since that’s half the battle for a successful verification.

• Document detection

• Blur and glare detection

• Tool-tips during the user flow

We store data in the US right now (https://support.stripe.com/questions/managing-your-id-verifi... ), but we’ll look into region-specific storage in the future.

No. 1. Stripe cares tremendously about and knows the importance of security—we’ve learned a lot from securely processing hundreds of billions of dollars in payments annually, and Identity is built from those learnings. (https://stripe.com/docs/security/stripe).

2. Any biometric identifiers that are created to perform the verification are never stored or retained—they are fully removed from all of our systems within 48 hours (usually within minutes).

More on this at https://support.stripe.com/questions/managing-your-id-verifi....

Working on it! Coming soon.

Yep, Stripe would be the data controller in this situation (and we comply with GDPR). https://support.stripe.com/questions/managing-your-id-verifi...

Identity isn't available in India today, but that anchor link is indeed broken (we'll fix this now—thank you!).

...neat idea, yes!

Nope, no need! Tax ID is validated when you accept the payment: https://stripe.com/docs/tax/checkout#create-session.

If you're looking to invoice a customer, Stripe Invoicing is VAT-compliant. It allows you to customize your invoices according to your customers' jurisdiction requirements (like sequential numbering): https://stripe.com/docs/invoicing/customize. We're also working on providing VAT invoices after a payment too. Give us a poke if you have any questions. edwin@stripe.com