Transaction management

use cross river card payments transaction management apis to push or pull funds to or from a debit card use the get endpoints to find out about a specific transaction or many transactions the post calls require a credit card token register with cross river apis the endpoints listed in this table are described in detail in the sections below action api call description transaction management docid\ wboa2sa1cfmr2woynicv8 post /api/transaction sends funds (push) to a specific debit card transaction management docid\ wboa2sa1cfmr2woynicv8 post /api/pulltransaction pulls funds to a specific card from a payer transaction management docid\ wboa2sa1cfmr2woynicv8 get /api/transaction returns a list of transactions sent from a merchant to a payee transaction management docid\ wboa2sa1cfmr2woynicv8 get /api/pulltransaction returns a list of transactions sent from a payee to a merchant transaction management docid\ wboa2sa1cfmr2woynicv8 returns push transaction details of a specific transaction transaction management docid\ wboa2sa1cfmr2woynicv8 get /api/pulltransaction/{transactionid} returns pull transaction details of a specific transaction send funds to a payee sends a payment or payout to a card use this endpoint for both domestic and international transactions transactions are classified as domestic or international based on the country of the card issuer transactions made with non us card issuers are considered international international transaction highlights if a transaction involves a cross border payment, then ofac screening overview is mandatory the ofac screening api checks the identity of the sender and allows the transaction accordingly the foreign exchange rates api call is recommended for more information, see international transactions original credit transactions (octs) reversals can occur only under specific circumstances, and at the discretion of the card issuer once the funds have been delivered to the cardholder, octs cannot be reversed through the card payments api for assistance in requesting a reversal on a specific transaction, please contact your cross river relationship manager download cross river's oct fraud submission protocol https //archbee doc uploads s3 amazonaws com/qt8sssvjnfadir3z gd2j rka isbmpasoaqngcyf 1 20240908 143210 pdf for a complete list valid values for businesstype and their meanings see business types request funds from a payer pulls funds from a registered card you also use this call for account funding transactions (aft), which pull funds from a specific account for use in a non merchant account for example, use this to load a prepaid card, top up a wallet, or fund a person to person (p2p) money transfer the api response includes the card token, amount transferred, and a transaction status that indicates success or failure for a complete list valid values for businesstype and their meanings see business types docid\ as4cyj0dxhz1 mvnoyj2v get push transactions returns a list of transactions, and their details, for payments sent from a merchant to a payee add query parameters to filter the response the api returns to all get calls use pagination to control presentation of your results response attributes the response attributes for this call are the same as for transaction management docid\ wboa2sa1cfmr2woynicv8 get pull transactions returns a list of transactions where a merchant (the payee) takes funds from an end consumer (the payer) add query parameters to filter the response the api returns to all get calls use pagination to control presentation of your results response attributes the response attributes for this call are the same as for transaction management docid\ wboa2sa1cfmr2woynicv8 get push transaction details by transaction id returns details of a specific transaction where a merchant (the payer) sends funds to an end consumer (the payee) use the transactionid attribute as the transaction identifier response attributes the response attributes for this call are the same as for transaction management docid\ wboa2sa1cfmr2woynicv8 get pull transaction details by transaction id returns details of a specific transaction where a merchant (the payee) takes funds from an end consumer (the payer) use the transactionid attribute as the transaction identifier response attributes the response attributes for this call are the same as for transaction management docid\ wboa2sa1cfmr2woynicv8 related topics card payments ofac screening overview foreign exchange rates api references card management ofac foreign exchange rates request and response codes error codes tutorials originate a push transaction originate a pull transaction