Balance and ledger models

balance models at a glance three balance models categorize partner managed programs the model depends on who holds the funds and the ledger location card only bin sponsorship docid\ z5zkbyq txaz 1bvhxbyg fbo subledger model docid\ z5zkbyq txaz 1bvhxbyg fbo pooled account model docid\ z5zkbyq txaz 1bvhxbyg cross river holds funds no yes (fbo) yes (fbo) fdic insurance for individual customer balances no (customer funds not at cross river) yes (pass through) yes (pass through) daily balance file no yes no balance visibility/sync n/a partner syncs customer balances into fbo account subledgers partner provides balance file for reconciliation daily transaction file yes yes yes chargeback file yes yes yes all partner managed programs require daily transaction files docid\ bvd4wcnis6zulo9cp6s5k for monitoring balance visibility requirements depend on whether cross river holds customer funds refer to reporting and compliance docid\ i4b iqavcqfp9m1611twc for other applicable reports choosing your model the right model depends on your program structure card only bin sponsorship cross river does not hold customer funds fbo subledger model cross river holds funds and maintains subledgers while you sync balances choose this model if you require access to cross river payment rails other than ach subledgers are fully routable accounts that provide access to all cross river payment rails pooled fbo account model cross river holds funds and you maintain the ledger with daily files all models where cross river holds funds require balance visibility this ensures fdic pass through insurance applies refer to balance visibility docid 3npvk0jfosqrv4rbiaasf for regulatory context card only bin sponsorship cross river only sponsors the bin and facilitates network settlement customer funds live elsewhere, at a different bank, in pre funded accounts, or sourced just in time from external systems, such as warehouse credit lines this model is used in bin sponsor credit card programs, where cross river holds no funds characteristics cross river does not hold customer funds no fbo account at cross river for customer balances no balance file or balance sync required no pass through fdic insurance for individual customers use this model when customer funds stay at a different financial institution your program uses external funding sources you need cross river's bin but not its banking infrastructure balance synchronization since cross river does not hold funds for this model, there is no need to synchronize balances reconciliation checks this model has no fbo reconciliation requirements cross river operations contacts you each business morning they provide the amount due for settlement fund your network settlement accounts on time with the exact settlement amount fbo subledger model cross river holds customer funds in a pooled fbo account you maintain your program ledger externally you also update individual customer balances in cos at the subledger level through daily balance files docid\ bvd4wcnis6zulo9cp6s5k cross river becomes the system of record through these subledgers characteristics cross river holds funds in an fbo account (maintains subledgers in cos) you sync balance changes to subledgers each customer has a subledger in cos supports all payment rails no daily balance file required (transaction file still required) balance file requirements sync balance changes through the core/v1/transactions docid\ n4nww9wntwf93qt vdlvh endpoint sync at least once daily high volume programs may need multiple syncs per day each sync reflects net balance changes at the subledger level an implicit subledger acts as a clearinghouse for reconciliation balance synchronization if you use the subledger model, you must synchronize balances in cross river we require this model the implicit subledger balances all other subledgers the system posts net credits as debits to the clearinghouse net debits post as credits from it small residual or timing differences may appear these accumulate in the implicit subledger they represent your program level net position use your fbo account's implicit subledger as a clearing house each customer subledger that changed during the day posts one book transfer that transfer goes against the implicit subledger this keeps the load light each changed subledger updates only once per cycle the number of transactions does not matter reconciliation checks subledger balances must match your internal customer balances total subledger balances must reconcile with the fbo balance total debits must equal total credits within rounding tolerance cross river operations contacts you for major discrepancies cross river will also alert you if funds do not cover network settlement fbo pooled account model cross river holds customer funds in a pooled fbo account you maintain your program ledger externally you provide individual customer balances to cross river through daily balance files docid\ i4b iqavcqfp9m1611twc these files give cross river visibility into beneficial ownership for fdic pass through insurance characteristics cross river holds funds in an fbo account you or your processor maintain the program ledger a daily balance file maps each customer id to a balance the file satisfies the fdic beneficial owner identification requirement balance sync requirements you or your processor provide the file, depending on who holds the program ledger the file must show each customer's insured balance that cross river holds deliver the file daily via sftp use csv format according to cross river specifications the file must reconcile to the total fbo balance balance synchronization post daily net balance updates into your fbo these updates must reflect all activity external to cross river that affected any card balances from your program reconciliation checks confirm your total fbo account balance matches the sum of all card balances from your program this amount must also match what you report in the daily card balance file