Skip to content

Credit Card Payments in Elliott but Not in Payment Gateway

Q - Yesterday, we processed two credit card payments through A/R Credit Transaction Handle.  They were declined.  Today, when we reconciled the A/R Credit Card Log from yesterday with the Payment Gateway (Solupay), they didn't match.  The difference is caused by these two declined credit card transactions.  The credit cad payments show up in the Elliott Customer Account Inquiry screen. But they are declined on the Payment Gateway.  See sample screen below.

The sample credit card log report below shows the declined transactions. Why did they end up as payment records in Elliott?

A - In your scenario, there were four attempts try to charge this credit card in Elliott.  The first two interfaced with Solupay (the payment gateway) and were declined. The last two did not interface with Solupay, and the system let them be posted in Elliott because the user chose to do so. 

As you may or may not know, in A/R -> Credit Card Trx Processing, in field “21. Approval No,” you don’t have to press F4 to interface with Solupay.  See sample screen below:  

If you just press Enter, the system will come up with the message, “You failed to press F4 to interface with Payware Connect. Are you sure?” See sample screen below: 

The default is “No.”  But if you choose “Yes,” then the system will let you proceed. Our system allows this to happen so we can handle exception situations.  For example, if for some reason you processed a transaction through Solupay or any other method without going through Elliott, then you should enter Elliott to report your credit transaction manually without interfacing again. Otherwise, you will double the amount that will be charged to the customer.

If you take a look of the sample credit card log report above, the last two entries have no PW-Trx-ID. That implies that these two transactions were not interfaced with Solupay.

Feedback and Knowledge Base