Resolution
The table below describes common types of issues related to the orders processing functionality in PBA-E along with the suggestion on where to start searching for the relevant information.
| Type | Description | Actions and relevant logs |
|---|---|---|
| Order stuck in ‘WP’ | Order stuck in “Waiting for Payment” Status | Two possible cases: 1)Order is waiting for Payment (before provisioning) -> Check Payment 2)Order is waiting to be consolidated. |
| Order stuck in ‘NP’ | Order stuck in “No Payment Method attached” Status | There is no Payment Method selected for automatic payments on customer’s account. Suggest customer to use one. |
| Order stuck in ‘WA’or ‘SS’ | Order stuck in “Waiting for Approval” or “Suspected” Statuses | Check Payment -> Fraud screening results. Reconfigure Fraud Filter if necessary. |
| Order stuck in ‘PR’ | Order stuck in “Provisioning” Status | Event Log: Check if the necessary “Submit Event” was posted. BM.log: Check submit event handler |
Following system components have direct influence on the orders processing functionality:
BM, TASKMAN, PEMGATE, [Payment plugin], [Fraud plugin] containers on the PBA-E application server.
Log files could be found as below:
BM.log -- Linux: /usr/local/bm/log/BM.log; Windows: C:\Program Files\Parallels\PBA\log\BM.log
Event Log -- PBA-E Control Panel, Configuration Director, Event Manager, Event Log