Okay, so now we've implemented payments into our application.
And in this particular section we've taken a look at taking payments of course using stripe.
And the reason that we're using stripe is due to PCI compliance regulations.
Really we cannot demonstrate setting up a system that meets PCI compliance.
That's not for us on this training course or the size of the application that we're building here.
And for an e-commerce store of this size, then we're simply not going to be able to justify the cost
of meeting PCI compliance regulations in order to take and store payment card details from a customer.
And we also took a look at strong customer authentication, which is the European standard for taking
payments, which relies on two of the three things something they know, like a password, something
they have, like their phone and something they are like their fingerprints.
And unless you know that you're only ever going to take payments within the US and Canada, then you
might as well use that approach to set it up.
And we've also taken a look at secrets and where to store them when it comes to publishing.
Then we can provide that secret information directly onto the platform that we're publishing, so it
remains in a secure location and cannot be accessed from anyone that doesn't have access to our platform,
where we're deploying our Application so frequently asked questions, then 2.9% is robbery.
Stripe charge 2.9% per transaction.
There must be a cheaper option.
Well, even if we did take payment cards directly on our application, then we're still going to face
a charge from the credit card companies themselves.
They impose a charge of around about 1.5% per transaction, and the smaller the business, the higher
that charges.
And typically that's just the cost of doing business when it doesn't involve taking cash payments.
The only way to really make that free is to take cash or the equivalent of cash in some way.
But if we want credit cards payments, which customers do prefer to use because of the protections they
get from using their credit card, then there is going to be a cost imposed whichever method we approach,
and there would be a certain size of business where it would make sense to transition to taking payments
directly.
But that's not something that we'd cover on this training course.
So it's better just to use the payment provider like stripe, for instance.
That takes care of all of the PCI compliance stuff, so we don't have to.
So now that we have payments in place up next, we're going to further enhance our application by being
able to create an actual order.
And that's coming up next.