Diego,
Depending on the size of your online store I would not recommend you take responsibility for this data, in case of a possible external problem (hack, server security flaw and etc), I understand that it is bad for the user to have to enter the data every time they pay, but I think it will be less stressful than a possible audit, or lawsuits.
What I could recommend would be to use some options like:
There are other options, just mentioned these because they were the ones I remembered and on account of having a good
documentation even in Portuguese.
But if you really want to save the data in your database, use the crypt();
might be the best option, it has some size limitations, and it is not very recommended to use in passwords (according to the documentation), but it would suit your case well at least in the user information.
There’s this article here from Thiago de Belem, is old, but gives a good basis of the crypt();
In short, start by playing the responsibility to third-party companies, as you grow you will take responsibility for this information.
And paying me, I wonder if it’s good?
– Diego Souza
@Diegosouza o pagar.me is a novelty for me I will even keep it, the site is really beautiful, and I really liked the documentation, I just did not find his fees, but it seems to be a complete platform.
– Bulfaitelo
It seems that the rates are in the same way as Payu.
– Diego Souza