# Transaction Stages for a pending Transaction source: https://developer.mastercard.com/cross-border-services/documentation/api-ref/transaction-stages_notused/index.md Effective 31 March 2020 in the test environment, and 30 June 2020 in production, the following are the list of Stages for the Pending status: | Stage | Description | |-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Processing | Transaction has been accepted and is being processed. This is the standard and most common pending stage. | | EligibleForSettlement (new) | This stage will only be seen by OIs who are set up for settlement of Pending. Transaction has been accepted, passed initial system validations, and has been passed to the receiving provider. If the transaction is in this stage at any time before the settlement cutoff, the transaction will be settled. For example, if a transaction was in the EligibleForSettlement stage, and then went to OriginationResponseRequired at the time of cutoff, a debit would still be created for settlement and shown on the Settlement Reconciliation File. | | Note: No other pending stage will trigger settlement. | | | CreditInProgress | This is a legacy stage for OIs who are not yet set up for settlement of Pending. Transaction has been accepted, passed initial system validations, and has been passed to the receiving provider. | | OriginationResponseRequired (new) | Transaction has been accepted, passed initial system validations, but has been held due to a Request for Information (RFI). The OI should respond to the RFI in order to allow the transaction to continue processing. | | Ambiguous | The transaction has initially been accepted but a processing anomaly occurred. Note that certain amount fields will be blank in the response. The transaction status updates can be found via the Retrieve Payment API or the transaction reporting provided. If the transaction receives a status update, be it any new pending stage or a status of SUCCESS, the amount fields that were previously blank will be provided with the new response. | | Any other value | While Mastercard Cross-Border Services attempts to limit the number of pending stages sent to the OI, some receiving Institutions may provide different pending stage values than what is listed above. It is suggested that the OI treat the unknown stage as you would "Processing" and contact the support team if details on the exact meaning of the response are required. | Below is the legacy list of Stages for the Pending status until the new values become effective: | Stage | Description | |------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Processing | Transaction is being processed. | | InProgress | The transaction has been submitted to the destination system, we are now waiting for it to process it. This is a generic stage when connected to a destination party that uses an asynchronous processing model. | | AcceptedInProgress | The outcome of the transaction is already known to be successful, however some additional processing is still required to close the transaction. The transaction summary is not available at this time, and you should wait for a final Successful status to announce the sending end-user that the transaction was successful. | | RejectedInProgress | The outcome of the transaction is already known to be rejected, however some additional processing is still required to close the transaction. The transaction rejection reason code is not available at this time, and you should wait for a final Rejected status to announce the sending end-user that the transaction was failed. | | WaitingForSendingInput | An action on the source side is required to continue the transaction, i.e. an advice of charge was provided, waiting for user confirmation | | AmendRequested | The destination system requested the sender to update some transaction details, as it is unable to complete it with the current data. A typical case would be requesting an update on a misspelled beneficiary's name or address. In this case, the stage specific fields contains the fields to update, with their current values. | | VerificationRequired | The transaction is blocked due to an inconclusive sanction list screening operation. The sending service provider's compliance officer is invited to resolve the case with the sanction list filtering system provider directly. The transaction will be resumed automatically when the case is resolved. Such a stage is only possible if the sending service provider delegates sanction list filtering tasks. | | Ambiguous | The transaction has initially been accepted but a processing anomaly occurred so further processing and validation is required to see if it can be sent to the destination system. Please note, due to the processing anomaly certain amount fields will be blank in the response. The transaction status updates can be found via the Retrieve Payment API or the transaction reporting provided. If the transaction moves to a status of SUCCESS, the amount fields that were previously blank will be provided with the status update. | | any other value | A compliant client MUST be able to accept any other value in addition to those listed here. Even if such a value can't be explicitly understood, the sending system must consider it as if it was in the "Processing" stage |