Payments

If the 1c debit is unsuccesful with error code 51 (insufficient funds), we send a 0c debit instead. We are assuming that the 1c debit passed all fraud and cvv checks and the user just has a negative balance.

The full debit card number and cvv are not saved in our database. They are only transmitted to usio and a masked debit card number is sent to our backend (************1234). This keeps us PCI compliant because we do not store the debit card information or have it pass through our servers.

The two tokens that usio generated during the tokenization are used to make further payments, using them as reference. The tokens are generated in the usio master account, and we have several sub accounts for crediting and debiting where those tokens will work. When submitting a payment, all we have to do is include the original token and usio can lookup the actual card information and make the payment.