Hi,
On our merchant email receipt our Invoice number is showing up as something like 16017 - UTrgLL but we just want it to show up as 16017. Does anyone know how to fix this?
Thanks!
Hi,
On our merchant email receipt our Invoice number is showing up as something like 16017 - UTrgLL but we just want it to show up as 16017. Does anyone know how to fix this?
Thanks!
"merchant email receipt" ... from whom?
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
the receipt comes from authorize.net
The invoice number sent to Authorize.net is specifically intended to include a random set of letters after the main "number" for the purpose of ensuring uniqueness. This prevents the (relatively rare, but still real) possibility of two customers placing an order at exactly the same moment on your store and sending the same anticipated invoice number to Authorize.net for processing. Authorize.net won't accept two transactions of the same number. And, since Zen Cart v1.xx doesn't actually assign an order number until AFTER the payment is completed, it must guess the next number. It's that guess that creates the possibility of duplicates. Hence the random letters added for uniqueness.
As far as Authorize.net is concerned, the invoice number DOES include those random letters. As such it's very appropriate for them to include those letters in the email.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.