Card payments (New)

cos card payments cross river's card payments solution has two key capabilities instant disbursements (push to card) for payouts, refunds, and earnings, and instant funding (pull from card) that lets customers load wallets or accounts directly from their debit cards transactions flow through participating card networks for near real time funds availability what cross river offers payment types push payment a push payment sends funds directly to a recipient's eligible debit, credit, or prepaid card the transaction originates from your platform and, via cross river, "pushes" money to the cardholder's account funds are typically available to the cardholder in real time or near real time visa calls this oct (original credit transaction) pull transactions a pull transaction debits funds from a cardholder's eligible debit or prepaid card to fund a wallet or account on cos the cardholder authorizes your platform to "pull" money from their card payment options partial payment authorization when a pull from card transaction exceeds the cardholder's available balance, cross river's partial authorization capability allows platforms to capture available funds and let customers pay the difference with another payment method—reducing abandonment and improving customer experience flexible attributes for partners with submerchants send different business types (bai codes), statement descriptors, caids, or mcc codes all in a single program as approved by the card networks cross river uses a few shared bank identification numbers (bins) for all of these activities, allowing partners to receive the benefits that come with large volume discounts payment security risk detection cross river designs its risk detection services to protect online card payments our aim is to provide our partners with peace of mind while they conduct digital transactions our services include token validation service address verification service (avs) account name inquiry ( ani ) cvv verification (card verification value) tokenization cross river uses tokens to secure debit card numbers stored by the merchant, a token is proprietary and identifies a card in place of an actual card number cross river's tokenization allows merchants to securely access payment credentials without storing pans (primary account numbers) this is compliant with pci dss (payment card industry data security standard), the set of standards established by the pci security standards council to protect environments where payment data is stored, processed, or transmitted by replacing sensitive cardholder data with non reversible tokens, cross river reduces partners' pci dss compliance scope card authorization and compliance p2c processing complies with pci standards to ensure that sensitive credit card information is protected cross river uses only encrypted token information throughout our system any card number we use to transfer funds is meant for temporary access only during a transaction request what’s new we are migrating these card payment apis to the crossriver core system (cos), where all the other payment rails (ach, wire, etc) live this provides a more seamless customer experience, due to the single connection to all our api banking services across all rails the advantages of this migration include standardization moving to a standardized platform results in standardized integrations to third party platforms, eliminating the manual bespoke workarounds in various platforms not only are these manual workarounds a pain point for our partners, but they also add points of potential failure, resulting in a lot of overhead and upkeep in addition, because the account management apis also live in cos, migrating from p2pe to cos will also increase speed and reduce the latency related to calling cos and waiting for a response on card limits scalability moving to cos increases scalability partners would be able to easily increase their volumes, due to the robust cos infrastructure another reason for this increased scalability is the introduction of asynchronous apis, which are faster because of their increased throughput and ability to handle many requests in parallel accessibility lastly, migrating from ptpe to cos will make all the other payment rails and services more accessible with all the apis hosted in the same place for more information, please see the api specs and the migration tutorial docid\ g7y21fc4eez5gqy za6ly partner impact partners are recommended to migrate from the old ptpe card payments apis to the new cos card payment apis so they can gain all the benefits of our cos cross river will provide proper guidance to aid partners with their migrations, including but not limited to docid\ vwaqrytsaamt9 wyx3xdu joint integration testing e2e testing dedicated support engineers find out more docid\ ew kpe97elksg2rkdbjfz docid 33j3psoniaj55z58yonif docid\ pqbzhl42x xkucuotiqi docid 0i53j9w0ykgvwfwzabgz5