RTC Inbound Success
This section describes the expected message flow for an inbound RTC transaction.
This is the standard flow of Electrum’s inbound RTC service offering.
Your bank’s flow might look slightly different if you have implemented additional or bespoke steps based on your business needs.
PayInc initiates the validation phase by sending a
pacs.008:RtcVerificationRequestmessage to Electrum. Electrum returns an acknowledgement (ACK, HTTP200).Electrum sends you an
inboundCreditTransferAuthorisationmessage (CreditTransferschema) and you return an acknowledgement (ACK, HTTP200).You respond to Electrum with an
inboundCreditTransferAuthorisationResponsemessage (PaymentStatusReport) and Electrum returns an acknowledgement (ACK, HTTP 200).Electrum sends a
pacs.002:RtcVerificationResponseto PayInc and PayInc returns an acknowledgement.PayInc initiates clearing by sending a
pacs.008:RtcCreditTransferRequestmessage to Electrum. Electrum returns an acknowledgement..Electrum sends an
inboundCreditTransferCompletionmessage (PaymentStausReportschema) to you. You return an acknowledgement (ACK, HTTP200) to Electrum.Electrum sends a
pacs.002:RtcDeliveryStatusReportmessage to PayInc and PayInc returns an acknowledgement.
A bank can use the inboundCreditTransferCompletion to complete all necessary processing within their systems, including the initiation of posting instructions to the core ledger system.
Alternatively, Electrum also offers the option of sending a Posting message in order to update the core ledger system.