Authorize.Net Accept.js Payments v1.0.2

v1.0.2 (2026-09-16)

• The invoice number sent to the gateway now predicts the next order number
  the way core's AIM module does, the highest order id plus one, instead of
  reading the orders table's counter from SHOW TABLE STATUS. On MySQL 8.0 and
  later that value comes from the information_schema statistics cache, which
  refreshes once a day by default, so the same base number repeated across a
  day's orders (reported by chadlly2003 in the support thread). MariaDB reads
  it live, which is why our own test stores never showed it. The random suffix
  kept every invoice unique, so no transaction was affected; only the number
  was misleading.
• Nothing else changes: no settings change, no database change; card payments
  and the wallet hook are as in 1.0.1.