EDC Batches not settling even though RMS says it is settled

Also, I just found out from Microsoft that even though an approval code is entered during a transaction, the card will still show settled in the report and go through. The way that you find out it is a bad approval code is when you don't get the funding!!!

"CD" wrote:

Hello

Where are you based?

We use a company that authorises all their transactions via broadband. This rules out having to 'settle' your CC transactions at the EOD. Everything is banked immediately and there is a web service where you can check this online immediately.

Let me know where you are based and I will see if we can assist you with this option.

If you are using the internal EDC setup in RMS out of the box you will always have to settle your batch. Out of the Box RMS only supports a direct conenction(no direct dial) There are ways to resend your batch but its not something for the average joe(requires SQL Scripting) Call Vital, They are the ones that are actually processing your cards BA is just a middleman saying thank you for your money.

Are you getting any errors when settling? Are you using the Direct method in RMS or a 3rd party software like PCHarge? Is there a specific card type that is not working?

Let me know.

Thanks, Maurice

Can you please post the SQL scripts to "resend" the EDC batch?

As far as I know some of the information (CC number) gets changed or rather encrypted differently after RMS "thinks" that the EDC batch has been settled.

P.S. I am using the RMS internal EDC processing.

It doesnt resend the batch it just changes the status so you can manually resend it, You need to make sure that the batch number is the correct one. I have not tested this SP-2 of RMS.

Update visanetauthorization set status=0 where Visanetbatchid= #

# would be whatever batch you are trying to resend, and the RMS batch and your processors batch may not be the same.

Status 0=Open

I recently (had to) try "resettling" a batch because RMS though it was settled but it actually wasn't.

The problem is that after RMS settles a batch or "thinks" it settled a batch it changes the encrypted CC number. When you change the status field to 0 in the VisanetAuthorization table it will attempt to settle it but error out due to an incorrect/wrong CC number.