Daily RTP activity

report description this report lets you see all rtp payments for a single given cross river operating system (cos) partner you can use this report to reconcile between what you requested from cos and what cos actually processed term description cos cross river operating system partner cross river's immediate customer, i e you report details the table below shows the different columns included in the report together with descriptions and explanations of the information they represent column description transactionid the unique identification number for the related core transaction transactionamount the dollar amount of the payment paymentstatus the payment status in cos payment typename the core transaction type for a full list of payment types, see docid\ udr6dnnojtc vo6p6swgm paymentsource the source initiating the payment this may be one of the following api clearing house (for inbound payments) partner portal (when a partner user enters a payment request in cos explorer) ops portal (when cross river ops enters a payment request in cos explorer) partnername the name of the cos partner participating in the payment productname the cos product name for the cos account participating in the payment clientidentifier an optional unique internal identifier for the payment, defined by the partner note cos does not enforce uniqueness or idempotency based on this value it is, however, an important part of implementing a partner’s idempotency solution this value can be used to search for a payment to check if cos had successfully processed your request when in doubt this should not be done if the response indicates success it is only to be used in edge cases when there is doubt regarding the response (i e an exception occurred) for more information, see docid\ xqc2lrsg0xvv 9nmkqxkk debtorname the debtor name for the payment this can be either the cos customer or external debtor, based on the direction of the payment accountnumber the cos master account involved in the payment subaccountnumber the cos sub ledger account involved in the payment creditorname the creditor name for the payment this can be either the cos customer or external creditor, based on the direction of the payment creditoraccountnumber the creditor account number this can be the account number for either the cos customer or the external customer, based on the direction of the payment direction desc the payment direction (inbound or outbound) purpose the payment purpose referenceid the payment reference id in cos sentat the date and time the payment was executed completedat the date and time the payment completed rejectedat the date and time the payment was rejected if this field is populated, then the completedat field is always empty rtptransactionstatus status of the rtp transaction as reported by the receiving institution for a list of statuses, see the rtptransactionstatus table below confirmedtransactionstatus the rtp transaction status, as reported by the receiving institution and confirmed by cos for information on available statuses, see the instant payment docid\ a rhiqughyhmhjnm7p1u2 confirmedreasoncode the reason the payment did not complete, as confirmed by cos for information on available reason codes, see below confirmedadditionalinfo additional payment information, as confirmed by cos outbound request for payment inbound request for payment p ayment type value type description 0 credittransfer payment sent by a debtor fi to a creditor fi 2 returnrequest the originator of the original payment is requesting the funds be returned this is a non monetary transaction sending a return request is not currently supported 3 returnresponse response to a return of funds request this is a non monetary transaction the actual money movement to return funds would be done in another payment as a credit transfer this is a non monetary transaction 1 systemtimeout notification to the creditor fi that a credit transfer has timed out this is a non monetary transaction 4 remittanceadvice the ability for the debtor to send stand alone remittance information to the creditor and the ability for the creditor to send detailed invoice information to the debtor (b2b or b2c) this is a non monetary transaction 5 requestforinformation used to request additional details related to a credit transfer or a request for payment that has been received this is a non monetary transaction 6 paymentack a creditor (end user) may use a payment acknowledgement to acknowledge a credit transfer has been received and applied a creditor fi must use a payment acknowledgement to confirm the funds associated with a credit transfer previously accepted without posting (acwp transaction status), has posted to the creditor’s account this is a non monetary transaction 7 requestforpayment requests the initiation of a credit transfer from the party receiving the request this is a non monetary transaction 8 requestforpaymentresponse used to provide a business response to a request for payment this is a non monetary transaction 9 requestforinformationresponse used by the sender to provide the requested additional information in the form of an amendment to the original request for payment or credit transfer this is a non monetary transaction 10 requestforpaymentcancellation request for payment cancellation 99 unknown payment type was not recognized rtptransactionstatus status of the payment, as set by the receiving institution this applies to credit transfers and requests for payment status description actc payment has veen accepted rjct payment or payment related message has been rejected rcvd payment related message has been received by the receiving institution acwp payment instruction included the credit transfer is accepted without being posted to the creditor customer's account values for payment source value description 0 phone 1 fax 2 email 3 clearing house 4 api 5 rtp system timeout 6 ops portal 7 partner portal 8 return of funds 9 auto resend reason codes reason codes provide the reason a message did not complete and canbe found on the payment resultcode the result code will be ok if the payment was successfully sent/received code description ok completed 650 cannot parse the message 690 signature mismatch or verification error blkd payment has been blocked ac02 debtor account is invalid ac03 creditor account is invalid ac04 account closed ac05 account is blocked ac07 creditor account closed ac10 debtor account currency is invalid or missing ac11 creditor account currency is invalid or missing ac13 debtor account type missing or invalid ac14 creditor account type missing or invalid ag01 transaction is forbidden on this type of account ag03 transaction type is not supported/authorized on this account agnt incorrect agent am02 specific transaction/message amount is greater than allowed maximum am04 amount of funds available to cover specified message amount is insufficient am09 amount received is not the amount agreed or expected am11 transaction currency is invalid or missing am12 amount is invalid or missing am13 transaction amount exceeds limits set by clearing system am14 transaction amount exceeds limits agreed between bank and client be04 specification of creditor’s address, which is required for payment, is missing / not correct be06 end customer specified is not known at associated sort/national bank code or no longer exist in the books be07 specification of debtor’s address, which is required for payment, is missing / not correct be10 debtor country code is missing or invalid be11 creditor country code is missing or invalid be13 country code of debtor’s residence is missing or invalid be14 country code of creditor’s residence is missing or invalid be16 debtor identification code missing or invalid be17 creditor identification code missing or invalid ds24 waiting time expired due to incomplete order dt04 future date is not supported dupl payment is a duplicate of another payment dsoh signer is not allowed to sign for this account ff02 syntax error reason is provided as narrative information in the additional reason information ff03 invalid payment type information ff08 end to end id is missing or invalid md07 end customer is deceased narr reason is provided as narrative information in the additional reason information rc01 bank identifier code specified in the message has an incorrect format rc02 bank identifier is invalid or missing rc03 debtor fi identifier is invalid or missing rc04 creditor fi identifier is invalid or missing tm01 invalid cut off time tk01 invalid token tk02 sender token not found tk03 receiver token not found tk04 token expired tk05 token found with counterparty mismatch tk06 token found with value limit rule violation tk07 single use token already used tk08 token suspended noat receiving customer account does not support/accept this message type 1100 any other reasons reason is provided as narrative in the additional information 9909 central switch (rtp) system malfunction 9910 instructed agent signed off 9912 recipient connection is not available 9934 instructing agent signed off 9946 instructing agent suspended 9947 instructed agent suspended 9948 central switch (rtp) service is suspended