Introduction

About this guide

This guide has been written to explain each of the Payment Statuses on MCS. Below describes each of the statuses and the situations in which they appear. A Service Request’s payment status can be viewed via Analytics > Finance – Reconciliation Report.

Payment Statuses

CONFIRMED

• The payment has been taken successfully.
• A successful notification has been received from the payment provider.
• The User/Customer is redirected back to the MCS Form.
• The Service Request (SR) is submitted successfully.

FAILED

• The payment has failed (e.g. incorrect card details, insufficient funds, or provider rejection).
• An unsuccessful notification has been received from the payment provider.
• The User/Customer is redirected back to the MCS Form.
• The Service Request is not submitted.

TRANSFERRED

• The User/Customer has been redirected to the third‑party payment provider’s site.
• No payment notification has been received by MCS.

This can occur if the User/Customer:

• Successfully completes payment but does not return to MCS (e.g. closes the browser or navigates away).
• Does not complete payment (or payment fails) and is not redirected back to MCS.

In all Transferred scenarios, the Service Request is not submitted.

FAILED_TO_CONFIRM

• The initial payment request has been successfully passed to Civica via a web service call.
• The User/Customer is redirected back to MCS, indicating that a payment has likely been completed.
• On redirect, MCS makes a second API call to validate the transaction / authorisation code returned by the payment provider.
• This validation checks that the payment is secure and confirmed, with the result stored in the QueryAuth table.

A FAILED_TO_CONFIRM status occurs when:

• The confirmation API does not return a successful validation, or
• The expected transaction / authorisation value is not available in QueryAuth at the time of checking.

This may happen due to temporary unavailability of the confirmation API, or Timing delays, where the QueryAuth record has not yet been created when the validation call is made.

In this state:

• The payment may have been taken successfully by the provider,
• However, MCS cannot securely confirm the transaction,
• Therefore, the Service Request is not submitted.