Skip to main content
Every transaction that comes into Partner Ecosystem Management goes through error validation checks. These checks are related to the following errors listed below.

​
Idempotency

Consider the following example of idempotency in Partner Ecosystem Management. Partner Ecosystem Management processes a transaction and it is successfully applied to the customer’s bill. A few minutes later, the same transaction with the same external transaction ID (ID 123) that is generated by the Merchant comes into Partner Ecosystem Management again. In response to this duplicate transaction, Partner Ecosystem Management verifies whether the external transaction ID (in this case ID 123) already exists in the Partner Ecosystem Management database. If it does exist, then Partner Ecosystem Management responds back with the same status of “success” that it gave to the first transaction. Partner Ecosystem Management does not apply this duplicate transaction to the bill, thereby avoiding the need to provide an error message and then process error checks. Now, consider another example of a duplicate transaction. Partner Ecosystem Management processes a transaction and it is successfully applied to the customer’s bill. A few minutes later, the same transaction with a different external transaction ID (ID 456) that is generated by the Merchant comes into Partner Ecosystem Management. In response to this duplicate transaction, Partner Ecosystem Management verifies whether the external transaction ID (in this case, ID 456) already exists in the Partner Ecosystem Management database. Since it does not exist, Partner Ecosystem Management will process the transaction.

​
Standard Account Errors

Partner Ecosystem Management also handles standard account errors, which are errors where an account either does not exist, does not have a balance, or is in a suspended state. For example, Partner Ecosystem Management is sent a transaction from a Merchant and attempts to post it on an account, but the account does not exist, does not have a balance, or is in a suspended state. Partner Ecosystem Management responds to the Merchant indicating the actual account error. The Merchant will then need to re-send the transaction in response to the error message to try the transaction again. This second transaction will have a different transaction ID. Note: The format for these transaction exchanges is JSON. Partner Ecosystem Management has an API that Merchants can call for Partner Ecosystem Management to apply transactions in real time. Parent topic:Partner Ecosystem Management Features