At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Reservation of seats is not permitted. Ticket bookings via the Internet must be confirmed within the 15-minute time frame allowed for each transaction to be completed. If such confirmation is not made within this period, the transaction time expires and the transaction will be deemed incomplete. Any seats allocated will be automatically returned to the system and be available for sale on a "first-come-first-served" basis.
Log in to your PayPal account.
In your account tab
You will see a short cut bar View all of my transactions you can select dates ranging from certain months and days from and to.
With a show tab.
The best solution is to have tech support remove the offending transaction from the batch, and then settle the batch. Since it is just a pre-auth, you'll need to run a post-auth to complete the transaction anyway, so it's not a big deal in this case. In the case of it being an actual sale transaction, you would have to remove the transaction from the batch, and then re-run it through PCCharge as a post-auth.
If you don't want to deal with VFI's tech support (I wouldn't either), then depending on your version, you may have more options. If it's a later version 5.7.x and up, there is a batch utility that will allow you to remove the transaction by yourself. If you are using an older version that does not include the batch manager utility, you could rename the batch file (in case you need it later) and in the case of 2 transactions, re-run them in directly in PCCharge as post-auths. Verify that the correct transactions are in in the batch, and then settle as normal. (just as an FYI, pcc tech support will not rebuild any batches with less than 50 transactions. So it might not be a bad idea to learn the batch manager and/or renaming files if you are sticking with PCC).
Your only option is to have it print out automatically after every 32 transactions, print out after every transaction, or print out only when there was an error with the transmission.
That parameter is Comm Journal and you can get to it by going to Function 7, option 4. That should give you a fax parameter table. You want options 12 and 13. Set 13 to "1" if you want it to print out every 32 transactions. Set that to "2" if you don't. Set 12 to 1 for Comm Journals Off, 2 for Always, and 3 for Incomplete Only (errors).
×