There are some errors like the account number being invalid that may arise upon transaction as the validation for that comes out only after processing. If the customer encountered this error, it will be detailed with the reason for rejection.

A customer can encounter this error if the ID, UID, and PWD provided is invalid or the static IP address used in the calling of API is not enabled/filtered in our system.

A customer can encounter this error if the data is incomplete like one or more fields are missing.

A customer can encounter this error due to the following reasons: 1. Amount set to param2 is not equal to amount due, and 2. totalAmount is not equal to amount with applicable date

A customer can encounter this error if the signature does not match or the payload has been tampered.

This is applicable only in API, if the agentRefNo entered in /process endpoint already exists, API will respond with result code 124 with Duplicate Reference Number remarks. The agentRefNo or the agent reference number is a unique parameter that is included in the /process endpoint in Ventaja’s API, if the agentRefNo used in the next transaction is the same as in the previous transaction (which is already a successful transaction), API will respond with result code 124 with Duplicate Reference Number remarks.

This is applicable only in API, if the agentRefNo entered in /inquiry endpoint is a non-existing transaction, API will respond with result code 129 with No Record Found remarks.

This is applicable only in API, if the billerCode entered in /cancel endpoint is a non-cancellable transaction, API will respond with result code 130 with Invalid Biller Code remarks. Billers that applies the Cancellation Transaction are G01, G02, G03, G04, G05, G08, and G09. API will also respond with result code 130 in /pulldata endpoint if the billerCode entered does not have a data retrieval process. The billers that applies the Data Retrieval or /pulldata are P02, P03, A02, G06, and G07.

Our system keeps a list of fraudulent names and if a customer's name is in the list, we will deny the transaction. The support process is through whitelisting of the name.

The whitelisting process is 1-2 business days because we need to review the transaction. If the customer’s name is already whitelisted in the system, they can immediately proceed with the transaction.

You may schedule the download of biller data using /billerdata endpoint periodically

The API will return a rejection response on /validate or /process endpoints

You may refer to the biller template document

The param2 only includes the amount to be paid by the user/customer, fees are not included.

The totalAmount is the amount to be paid by the client in PinoyPay including the base amount and the fees. The computation is as follows: totalAmount = (param2 + param8 + param9(if applicable)) - param10(if applicable)

The settlementAmount is the same as the totalAmount and it is an amount to be deducted in client's PinoyPay wallet including the base amount and the fees. The computation is as follows: totalAmount = settlementAmount = (param2 + param8 + param9(if applicable)) - param10(if applicable)

The param8 is the service fee between the client and Ventaja, which will be deducted to the client's wallet. The param9 is the convenience fee, whilst param10 is the merchant commission. The mentioned fees are to be set by the Account Manager in the PinoyPay for a client to process with the transaction. Once the Account Manager is done setting the fees, the client can identify the values using the /billerdata endpoint in the Unified API.

A customer can encounter this error when the account number being payed is already paid with the set applicable month.

A customer can encounter this error when the identifier used is invalid or have a special characters in it.

The param1 is for account number or reservation number of the customer whilst param4 is used for identifier such as account name or mobile number which is required for some payments