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.

Credit Card Processing

  1. How to Process a Force Credit Card Transaction?
  2. Credit Card Processing Frequently Asked Questions
  3. Payware PC Server Actively Refuses Credit Card Transaction
  4. Does Elliott Encrypt Credit Card Number in The Database?
  5. How to Reverse Credit Card Sales?
  6. Credit Card Transaction Time Out
  7. Procedure to Process Credit Card by Reference ID
  8. How to Charge a Credit Card If Pre-Authorized for the Wrong Customer
  9. Payware Connect Communication Error
  10. What Happens if Credit Card PreAuth Is Not Followed by Completion?
  11. Credit Card Processing Error: Chk Viawarp For Dupl
  12. What Does Error Code 2029999 Mean in Payware Connect SIMEvent.Log File?
  13. I Receive "A call to SSPI failed, see inner exception" Message During Credit Card Processing
  14. Credit Card Payments in Elliott but Not in Payment Gateway
  15. Feature - Support for Verifone Point Devices with Card Chip Technology
  16. Error with Payware Connect - The remote certificate is invalid according to the validation procedure
  17. How to Find Orders That Have Been Pre-Authorized for Credit Card Charge
  18. Feature - Online Credit Card Interface Level 2 Support
  19. How to Handle and Prevent Credit Card Duplicate Charges
  20. Invalid Tran Counter [99...99] with POINT Interface When Charging a Credit Card
  21. How to Set Up MX915 POS Device for Static Network IP Address
  22. Receive "Input parameter INVOICE assigned invalid value" with POS Credit Card Charge
  23. How to Reprint a Credit Card Receipt
  24. Does Elliott Support Credit Card Pre-Authorization Transactions?
  25. What Is the Credit Card Authorization Member Field for?
  26. Selling Non-Approved Items Can Cause Credit Card Processing TERM ID ERROR

Feedback and Knowledge Base