TGU: Release notes 25-08-2026

The main focus of this release is fixing several cases regarding orders with status verify . We recently investigated some cases of orders showing strange behavior regarding handling authorizations and captures with orders in this state. To clarify, we have made the following changes:

• If an order is captured before going to verifybecause the payment method does not support authorising orders, nothing changes. The order is captured and the moneyflow is registered. If the order is approved, the status will simply change to captured. If the order is declined, a refund will be initiated.
• If an order is authorised and then goes to verify, the TGU will automatically capture any authorisation before it expires to make sure the order can still be completed. This will fix cases where an authorisation expires quickly, like PayPal payments with intent=CAPTURE for example.
• • If the order is approved before the authorisation expires, the TGU will try to uphold the original intended capture time. If the intended capture time has passed, the authorization will still capture the authorization if automatic capturing was enabled and the order will be captured. If automatic capturing was disabled, the order will status be authorised and the order can be captured/voided as usual.
  • If the order is denied before the authorisation expires, the TGU will void the authorisation and the order will be declined.
  • If the authorization was captured to prevent expiring and then approval will change the status to captured and send out a captured notification.
  • If the order is denied after capturing the authorisation, a refund will be initiated

• Floa: Correctly format the Phone number to prevent errors