F9663 - CF - is this document an overview?
The purpose of this document is to provide an overview of the process used in PASI to reconcile payments with EPS2 (Electronic Payment System) for myPass services that requires payment collection. The following myPass services incorporates a payment collection process:
If a service on myPass has an associated cost, a user generally must submit the payment before it is submitted to PASI for processing. For example, a Transcript Document Order must be paid for in full before it is prompted to a status of Ordered.
For connected students and 3rd party users on myPass, the payment must be made using EPS2 (Electronic Payment System), which is the common electronic payment system (EPS) used by applications in the ministry to collect payment. EPS2 uses https://www.bambora.com/en/ca/ to collect payment from users.
When a user indicates that they would like to proceed with payment on myPass, the Payment Item the user is paying for is placed in a “Payment Pending” status. A PaymentPending status indicates that a payment session has been started in EPS2, but myPass has not received an indication from EPS2 that the payment process was completed.
In most cases, once a user completes the payment process on EPS2, myPass will receive a response from EPS2 and update the Payment Item accordingly. However, there are scenarios where the response fails to return to myPass. This can be caused by the user abandoning the payment process in EPS2/Bambora (e.g. by closing the browser window), or myPass has lost connection with EPS2. Hence, a reconciliation process is needed to determine the statuses of these outstanding Payment Pending orders/requests, so that PASI can update them accordingly.
I think these bullet points don't belong in this document F9663 - CF
PASI, using the Submit Invoice service, creates an Electronic Payment System Invoice with a Processing Status of Initiated (Invoice Processing Status) anytime a user launches EPS2 (Electronic Payment System) to pay for a service. The Invoice Identifier serves as the identifier for the payment session when communicating with EPS2.
The Processing Status is updated accordingly along with the Payment Item if PASI successfully obtains an End State response from EPS2.
While a particular payment item can have multiple Electronic Payment System Invoices (if user were to launch EPS2 to pay for the item multiple times), each payment item should only have at most one Initiated Invoice at any time.
During reconciliation, PASI will receive one of the following responses from EPS2 regarding the status of an Electronic Payment System Invoice:
For a payment item to be brought out of a PaymentPending status, the associated Invoice must have one of the three End States; otherwise the payment item remains in Payment Pending status.
EPS2 will perform validation on the request from myPass before determining the status of the payment; if the request fails validation, a validation error will be returned instead of one of the 4 possible responses listed in the Payment Reconciliation Process section below. The following are the possible validation errors that may be returned from EPS2:
Payment reconciliation can be triggered by one of two methods. Regardless of how it is triggered, the process to reconcile Payment Pending Payment Items is identical.
Can also be called User Reconciliation.
Reconciliation is triggered automatically as soon as one of the aforementioned pages loads. Depending on the result of the reconciliation, user may be given an option to manually trigger the reconciliation process to run again.
Reconciliation runs only on the payment item(s) that the Education Account user has created that is currently in the “Payment Pending” status. The associated Electronic Payment System Invoice that has a status of Initiated will be the invoice selected for reconciliation in the process.
Can also be called Scheduled Reconciliation.
A scheduled Reconciliation task in PASI will run the reconciliation process regularly. In all environments, the process will execute once every 46 minutes in all environments if the configuration setting Core.PaymentReconciliationEnabled is set to true.
The reconciliation process has been updated to attempt to reconcile invoices for the following discrepancies:
Payment Item | Message |
---|---|
Transcript Document Order | Pending Payment on the Transcript Document Order Message |
Diploma Exam Registration Request | Unsuccessful Payment on the Diploma Exam Registration Request Message |
Diploma Exam Rescore | Pending Payment on the Diploma Exams Rescore Request Message |
If EPS2 return the status of | Update Document Order to |
---|---|
Approved |
|
Declined |
|
Lost |
|
In Progress | (No Updates) |
Validation Errors (see Possible Validation Errors from EPS2) | Treat as Lost status:
An error will also be logged for the validation error (see Logging Validation Errors) |
{Error} (that are not Validation Errors) | (No Updates) |
If EPS2 return the status of | Update Diploma Exam Registration Request to |
---|---|
Approved |
|
Declined |
|
Lost |
|
In Progress | (No Updates) |
Validation Errors (see Possible Validation Errors from EPS2) | Treat as Lost status:
An error will also be logged for the validation error (see Logging Validation Errors) |
{Error} (that are not Validation Errors) | (No Updates) |
If EPS2 return the status of | Update Diploma Exam Registration Request to |
---|---|
Approved |
|
Declined |
|
Lost |
|
In Progress | (No Updates) |
Validation Errors (see Possible Validation Errors from EPS2) | Treat as Lost status:
An error will also be logged for the validation error (see Logging Validation Errors) |
{Error} (that are not Validation Errors) | (No Updates) |
If a Validation Error was returned from EPS2, a Warning Message will be logged in PASI as follows: