Significant programming and accounting changes would be required by Kiva to process such a transaction. I just don't see that Kiva stands to benefit much at all by taking on such a project.
in this imaginary world....
programming changes are minimal depending on how 'automatic' kiva would wish it to be.
my vision for KSC in this instance.... would be manual and require similar to the following
KSC1 has 75 loans each with an 'identifier field' attached to that loan and transactions which labels them as KSC1
KSC2 has 55 loans each with an 'identifier field' attached to that loan and transactions which labels them as KSC2
KSC3 has 30 loans each with an 'identifier field' attached to that loan and transactions which labels them as KSC3
a querry on the identifier field for KSC2 and KSC3 would pull up all the loans and transactions related to those two accounts - then a change from KSC2, KSC3 to KSC1's ID would then allow them all to fall into KSC1's account history and balances.
probably a couple more things out there that might have to be done - but it's really not too much more complicate than that. Now kiva's reasons (legal/historical/etc) behind not allowing such a thing to happen are just their wishes - as for the process to let it happen - not so involved.
since I'm not inside kiva's database - I could be way off base - but I feel certain I'm close.
