----------------------------------------------------------------------------------------------------------------------- Version List ----------------------------------------------------------------------------------------------------------------------- 04/11/2021 - Version 1.0.0 1st part: Add the AuditMessages, AuditMessage, Headers and Payload element for the XML validation 2nd part: Add version to xsd schema ----------------------------------------------------------------------------------------------------------------------- 02/08/2022 - Version 1.1.0 Add field PaymentSchemeIdentification ----------------------------------------------------------------------------------------------------------------------- 23/03/2023 - Version 1.2.0 Modify field type for ResponseCode ----------------------------------------------------------------------------------------------------------------------- 23/08/2023 - Version 1.3.0 Add field SequenceNumber 12/09/2023 - Version 1.4.0 Add auto-renewed contract data fields (OrderNumber, ProductCode, StartValidityDate, EndValidityDate, ContractExpiryDate) 21/06/2024 - Version 1.4.1 add operation id to identify the agent who trigger the reset payment ----------------------------------------------------------------------------------------------------------------------- rpe_media_settlement_post: This audit will be produced after the reception of the response from one PaymentRequest rpe_media_payment_response: This audit will be produced after the reception of the response from one PaymentRequest The unique identifier of the related customer account (may be null) In case of PaymentRequest linked to travel, there will always be the MediaSerialNumber of the corresponding card. The MediaSerialNumber can be empty if the PaymentRequest is linked to autorenew/autoreload or online shopping with a payment means. In this case, the paymentMeansId will be specified. Currency code according to ISO 4217. Identifier of the request. Carries the Acquirer Bank Response Code(s) Bank authorization reference number that can be used to discuss directly with bank. It can be display in IFS MMI of payment history. Type of action to be performed. Capture possible provided by the Payment Gateway to define if payment is first ride risk eligible. Media type e.g. EMV Identifier of the connected IFS system. Shall come from the request. OperatorId to identify the agent who trigger the reset payment. If a payment means was used for this settlement, the paymentMeansId related if a payment was unrecoverable then we approved a cit/tap payment request for this payment Overall status of the payment resource. If the payment was divided in two phases (authorization and settlement), both status are also present If the corresponding payment request contained an authorization, here is the status of the authorization If the corresponding payment request contained a settlement, here is the status of the settlement Id produced by the Payment gateway adaptor in order to allow reconciliation in reporting Approval Code used for reconciliation Authorisation Code used for reconciliation and debt recovery Sequence number for each response for tracking and mapping purposes Response Reason from Payment Gateway Code explaining the response from the Payment domain. auto-renewed contract data True when a payment was received after . auto renewed contract order number. auto renewed contract product code start date of the renewed contract end date of the renewed contract expiry date of the old contract