Pc Charge A Settlement Error Has Occurred
Contents |
a major data loss with PcCharge. When settling the current batch for the day, a settlement error occurs. Error: Intermediate Batch, must close before settling batch. Now the weird part of it all is that there are multiple batches that had not been settled for at least a weeks worth of transactions. pccharge technical support But those other batches were sayed to be settled by pccharge no problem. Visanet/Vital is saying that the
Pc Charge Pro Troubleshooting
batches that were supposedly settled in PcCharge were not settled but I have approvial numbers for each transaction. My feeling is that we could've been attacked
Pccharge Error Codes
by a hacker or virus, and the only reason I say that is because when I look at the batches in the Batch Utility, nothing can be made out, no approvials, no credit card numbers, no expiration date, no nothing. Is it possible I
Pc Charge End Of Life
have lost all the transactions for that week and if so how can this be repaired? Thanks to anyone taking the time to listen. Thanks Again, Joe Email: , Apr 27, 2005 #1 Advertisements Greg Williams Guest Joey, Check your backups from the previous nights and see when the data was corrupted. You should be able to recover much of the data or at least find out when this problem started occurring. You can also work with PC Charge tech support to try and find the data in the PC Charge data files. "" <@discussions.microsoft.com> wrote in message news:... >I have sustained a major data loss with PcCharge. When settling the current > batch for the day, a settlement error occurs. Error: Intermediate Batch, > must > close before settling batch. Now the weird part of it all is that there > are > multiple batches that had not been settled for at least a weeks worth of > transactions. But those other batches were sayed to be settled by pccharge > no > problem. Visanet/Vital is saying that the batches that were supposedly > settled in PcCharge were not settled but I have approvial numbers for > each > transaction. My feeling is that we could've been attacked by a hacker or > virus, and the only reason I say that is because when I look at the > batches > in the Batch Utility, nothing can be made out, no approvials, no credit > card > numbers, no expiration date, no nothing. Is it possible I have lost all > the > transactions for that week and if so how can this be repaired? Thanks to > anyone taking the time to listen. > > Thanks Again, > > Joe > Email: > Greg Williams, Apr 28, 2005 #2 Advertisements Yuri Bey Guest Your employee ran through a credit card that you have not signed up for. The PCCharge will not settle the batch and it put in intermediate batch. I had similar situation and I had to call PCCharge to salve this problem. The transaction ne
creates a log of settlements in plain-test format and stores the log in the PCCharge installation directory. The file (named Settle.log) will contain the settlement response from the processor and the time.date of the settlement. The PCCharge Auto-Settle utility can be used on the computer on which PCCharge is located, or a computer with read/write access (full permissions) to the PCCharge installation directory. The Auto-Settle utility is primarily intended for use with one account. When used with multiple accounts, PCCharge will attempt to settle the batches in the order their respective accounts appear in the software. If a settlement attempt fails, the Auto-Settle utility will not continue on http://www.accountantforums.com/threads/pccharge-wont-settle-visanet-vital.96181/ to the next account. We highly recommend that you check your Settled Batch Report after using the utility with multiple accounts. Arts Management's thoughts on having PCCharge Auto-Settle We strongly recommend you close the batch using Theatre Manager's End of Day process, rather then having your Merchant Provider or PCCharge auto-close the batch. This is particularly important if you are running web sales. There are complications with having the merchant http://www.theatremanagerhelp.com/book/export/html/1583 close your batch. For Example: You run your end of day at the end of your shift. At that time Theatre Manager includes all of the sales to be deposited from that moment back to the last time you ran the deposit process. This is the information you would be providing your accounting department. After you run your deposit the web listener continues to process sales. It processed transactions till midnight and then deposits the credit cards. Those sales are NOT in the deposit information you are providing accounting. They won't be in the deposit until you run the deposit the following evening at which time the next days sales will also be included. If there is ever a discrepancy between your monthly bank statement and Theatre Manager's End-of-Day reports, it can much harder to trackdown and resolve in a quick and timely fashion. Another disadvantage is errors in the batch. If the batch has too much money or not enough money to match Theatre Manager you have no opportunity to correct the issue before you deposit. You are sending it to the bank and won't be able to locate differences until the account department finds them. By closing the batch at the box office there is
press the SETTLE CREDIT payment button. Credit Card Payment Method 2. Select The Action Select the card entry method to start the transaction. Card Entry Method Selection http://www.amigopos.com/help8/processing_cc_transactions.htm 3. Swipe The Card Swipe the customer card. If the card is swiped without an error, skip the next three steps and refer to Waiting For The Transaction Results. If the card cannot be swiped, the card number and expiration date must be entered manually, as described below. Waiting Card Swipe (Mercury Pay or Datacap NETePay Interface) pc charge 4. Enter The Card Number Manually When the customer's card cannot be swiped, the number must be entered manually using the on-screen keypad. Press the Enter Card Number Manually button to display the keypad, enter the card number and press the Continue button. Keyed Entry Screen 5. Waiting For The Transaction Results Amigo Pos will pc charge a send the transaction request to PCCharge Payment Server. The time remaining before a timeout error occurs is displayed on screen. If using IP processing, the transaction should be completed in under 10 seconds. Dial-up processing can take over 1 minute. If a timeout error occurs, a red error screen will appear. A timeout error most likely indicates that a local network or internet disruption has occurred. Amigo Pos will display a successful transaction with a green background, an unsuccessful transaction with a red background, and a duplicate or partial auth transaction with a yellow background. The transaction can be immediately captured or adjusted by pressing the Add Tip (or Capture) button. Transaction Results 6. Completing The Transaction Note that every Pre-Authorized transaction must be captured, even if the gratuity is zero. To add a gratuity, press the ADD GRATUITY button. If the ADD GRATUITY button is not visible, press the down arrow under the transactions button group until the ADD GRATUITY button appears. Credit Card Transactions The Transaction ID can be found at the top of the signature slip