0.12.0 - Worldpay XML and time zones

Analyzer

• Event and arrival times are used only when they are ISO 8601 with a time zone; anything else is removed from the event and reported once (TIMESTAMP_IGNORED), so ordering never depends on the time zone of the computer running the analysis.
• Times that a provider documents without a time zone and that are read as UTC (CCBill, Trust Payments) are marked "UTC assumed" in the timeline and the Markdown report, and a TIME_ZONE_ASSUMED warning appears when they are analyzed together with another provider's times.

Web app

• Findings show their documentation link for every provider, not only Stripe and Adyen. Links are shown only for https hosts that a provider manifest cites as official documentation, the same check the error decoder uses.
• The unsafe retry finding links the idempotency documentation of PayPal, Square, Mollie and Checkout.com as well.

Providers

• Worldpay XML is analyzed:
  • WPG paymentService replies (error codes, order status with lastEvent, the standard ISO8583ReturnCode values) and order notifications, linked by order code. Amounts follow the documented exponent; partial captures and refunds use the journal amount. Paste WPG documents without their DOCTYPE line, which is rejected for safety.
  • cnpAPI cnpOnlineResponse transaction responses with the 379 documented payment transaction response codes and the request validation codes.
  • WPG requests, reports, batch files and other replies are recognized and reported as unsupported. Extended ISO 8583 codes are shown with Worldpay's description but not decoded, because the WPG documentation does not tie them to a table.
• Checkout.com no longer appears as a 0.4 alternative for records whose only Checkout.com trait is a pay_ id, such as Razorpay payment entities. A bare pay_ id now scores 0.3 (documented length) or 0.15 (other lengths), below a record with documented fields.