I have a question regarding the testing of Credit Card application.I wanted to know how the issuing bank ( Credit Card Issuing Bank) gets the data from the merchant Bank.I am interested in knowing what all softwares and databases the issuing bank will use to convert the data received from the acquiring banks to create individual credit card statements and what all functional tests the QA person will be performing.Somebody worked on Credit Card Module in the financial industry will be able to answer my question.
As far as formats go, I think it varies. When I worked in eCommerce, though, the way it worked was they did a batch processing of all transactions at the end of the day. So there were cards being autheticated all day, a hold was placed on the funds on the card by the merchant bank, and then there is a batch performed which sends all transactions to the issuing banks at the end of the day.
So if there was a charge and refund done before this batch took place, the issuing bank would never even see it. At the same time, if you tried to charge someone's card like 5 times and it put them over their limit, then you'd need to wait until all of the holds were removed before your card would work properly again.
Whether it's gotten better or not, I don't know, this was liek 4 or 5 years ago.
[ QUOTE ]
Speaking personally, Brent, I have never seen a case where a charge and a reversing transaction posted immediately after one another did not both appear on my next statement.
[/ QUOTE ]
Really? We got this quite often. Now is this with a gateway service or the merchant bank itself? I don't know if these are functionally different or not. I'd have to think hard, it's possible this is how it worked with Bank of America. I can't remember exactly. I think with the payment gateways, though, they worked on batches. Like BoA would be a merchant bank whereas something like Authorize.net would be a gateway, right?