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 daily rtp activity /#enum values for payment type 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 idempotency 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 request and response codes 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 for a list of values, see confirmedadditionalinfo below outbound request for payment inbound request for payment enum values for payment type typename value description paymenttypes 0 credit transfer paymenttypes 1 system timeout paymenttypes 2 return request paymenttypes 3 return response paymenttypes 4 remittance advice paymenttypes 5 request for information paymenttypes 6 payment ack paymenttypes 7 request for payment paymenttypes 8 request for payment response paymenttypes 9 request for information response paymenttypes 10 request for payment cancellation paymenttypes 99 unknown values for payment source typename value description paymentsource 0 phone paymentsource 1 fax paymentsource 2 email paymentsource 3 clearing house paymentsource 4 api paymentsource 5 rtp system timeout paymentsource 6 ops portal paymentsource 7 partner portal paymentsource 8 return of funds paymentsource 9 auto resend confirmedadditionalinfo values