Payment types

to send or receive instant payments you need to know the following basic information about credit transfers and payment types (rfp) as well as the roles of the payment types docid\ ojcykdvhgpjflu3152 im credit transfer instant payments transfer funds in real time over networks like rtp®, fednow®, or crnow this uses the originate a credit transfer api message type pacs 008 purpose sends funds from the debtor (account initiating payment) to the creditor (account receiving payment) debtor fi the financial institution sending the payment creditor fi the financial institution receiving the payment type of payment push payment (initiated by the sender) key notes credit transfers are one way payments initiated by the sender cross river enforces a daily send limit for instant payments per partner crnow facilitates instant credit transfers within cross river’s network, providing faster internal partner payments refer to the diagram below for the end to end credit transfer process, showing interactions between the debtor, creditor, their financial institutions, and the instant payments network instant payments basic flow request for payment (rfp) request for payment (rfp) enables authorized pull payments by requesting funds from the debtor this uses the originate a payment request api message type pain 013 purpose allows the creditor to send a payment request to the debtor, who must authorize the payment debtor role reviews and approves the request before the transfer occurs type of payment pre authorized pull payment (initiated by the receiver through a request) key notes rfps offer a way to collect payments securely and transparently instant payments networks do not support automatic pull payments payments only proceed after debtor authorization crnow also supports rfps for internal partner payments within cross river’s ecosystem, streamlining fund requests and transfers refer to the diagram below that shows the flow from the initial request by the creditor to debtor authorization and final payment execution request for payment flow ultimate debtor and creditor roles ultimate debtor and creditor roles provide receiving banks with greater transparency about the true originator or recipient of funds these roles are essential when multiple parties are involved on either the sender (debtor) or receiver (creditor) side, clarifying which party is acting on behalf of another this ensures precise and efficient transaction processing if the debtor or creditor account is a business account, then the u ltimate debtor or creditor must also be a business account the ultimate debtor and ultimate creditor information is provided in the instant payments api example flow the sender (end user) initiates payment through the merchant’s app the merchant (ultimate debtor) facilitates the transaction on behalf of the sender you act as the debtor, affiliated with cross river cross river (sending fi) manages and processes the transaction the receiving fi receives the funds on behalf of the final beneficiary the receiver (end beneficiary) collects the disbursement this diagram shows the fund flow variations involving ultimate debtors and creditors instant payments ultimate debtors and creditors flow