Exceptions - POPRecarga/PartnerAPI GitHub Wiki
#InPDV Exceptions
##Exception Codes
##Exception Information
###1.NotFound Error message: Recurring Token doesnt exist or it was cancelled
This message occurs when the API tries to use/delete a RecurringToken that doesn't exist.
Obs: The user can delete any of his RecurringTokens at his POP private area.
###2.InvalidIdentifier Error message: identifier must be informed
This message occurs when the API receives no identifier when it is a mandatory field.
###4.InvalidTransaction There are a few different error messages for this code, they are listed and explained below:
| Error Message | Description |
|---|---|
| This customer is not currently active | This happens when the API tries to authorize a transaction of an inactive Customer (users are activated during payment creation). |
| RecurringToken is not active | This message occurs when the API tries to use a RecurringToken that is not active in our database. |
| RecurringToken is now locked for mismatching. | This message occurs when the comparation between the RecurringToken sent to our API and the one saved in our database fails. |
| The transaction is not pending. | This message occurs when the API tries to resend a transaction token and the transaction is not pending. |
| This transaction can't receive a chargeback. | This error occurs when the API tries to chargeback a transaction that already have a chargeback. |
| The chargeback exceeds the transaction available amount. | This error occurs when the API tries to chargeback a transaction that exceeds the contract limit. |
| The chargeback exceeds the transaction available amount. | This message occurs when the API tries to chargeback a value bigger than the available for the transaction. |
| The transaction can't receive a chargeback because its time limit is expired. | This error occurs when the API tries to chargeback a transaction that has reached its limit date of chargeback. |
###5.NotAuthorizedTransaction Error message: The transaction must be authorized.
This message occurs when the API tries to execute a transaction that wasn't authorized.
###6.InsufficientBalance Error message: This customer dont have suficient balance.
This message occurs when the API tries to create/authorize/execute a transaction, and the client don't have enough POPs. In all cases our API sends SMS to inform the user that he needs more credit.
###7.ExpiredTransactionToken Error message: The transaction token has expired by timeout.
This message occurs when the API tries to authorize a transaction that have an expired token (expiration time = 3 minutes). This exception also occurs when the API tries to resend an expired transaction token.
###8.InvalidTransactionToken Error message: The transaction token is invalid.
This message occurs when the API tries to authorize a transaction but the validation token is wrong.
###9.AlreadyExecutedTransaction Error message: The transaction already has its final state.
This message occurs when the API tries to process a transaction that is already processed.
Ex. trying to execute a transaction that is finished or cancelled will result on this exception.
###10.NotAuthorizedApplication Error message: The application is not authorized to do this operation.
This message occurs when an application tries to do an operation that he doesn't have permission.
###13.LockedCustomer Error message: This customer can't do a payment because your status is locked.
This message occurs when the API tries to create/authorize/execute a payment and the user account is locked for security reasons
###15.InvalidContractConfiguration Error message: The contract is expired.
This message occurs when the contract between your application and our API is expired. Please contact [email protected] for more information.
###16.ValidationTokenMisMatch Error message: validation token does not match
This message occurs when the API tries to Authorize a new RecurringToken but the ValidationToken is wrong.
###17.AlreadyAuthorizedTransaction Error message: The transaction already has been authorized.
This message occurs when the API tries to authorize a transaction that is already authorized.
###18.TokenAlreadyUsed Error message: token already used
This message occurs when the user tries to use the same token to validate more than one operation. Because we use Time-based One-time Password the user must wait for a while before we can generate a new token for him.