This page will help you to understand Paggi API.
The Flow bellow illustrates the states that a transaction pass until it is confirmed or rejected
Transaction Flow Diagram in the Paggi::API
Any Doubts?
If you've had any doubts during your experience with Paggi::API feel free to get in touch through our Support page ;)
Requisites for creating a Charge
If you have checked the workflow above, you've noticed that we require a customer to be created with a card before you can actually make a charge.
For us, anyone with a legal document is a customer. Even you, our partner (that uses our API) have a customer, that is addressed to receive the money after the charge was successfully charged.
A customer consist of at least, all the following: name, email and document. Other informations include stuff we use to analyze the customer profile, so we can know if this is a fraud user. Remember that sometimes, if we don't have enough data to analyze, we will return a recused status, so it is best for you to send as many informations as possible.
Risk Analysis is important!
Some users may cancel their transactions with their card holder. This will make us to cancel the charge, and you will probably loose money! So it is very important that you send us as much data possible so we can identify users that have suspect profiles. We all would be happier with lower chargebacks.
If you have a high incidence of chargebacks, this may affect your tax, making it to go higher, so don't take this part unnoticed.
After registering a user and its cards (you can make this in one step, check /customers