Extend Payment Authorization

Overview

This task finds orders with a payment authorization (reservation) that expires within the next five days and asks the payment provider to extend it. Use it when orders stay open longer than the provider keeps an authorization - for example backorders, pre-orders or products made to order - so the payment can still be captured when the goods ship.

Identifier

When to Use

Enable this task when you need:

• Expiring authorizations extended without opening each order in the Omnium UI
• Payments on long-running orders kept capturable until delivery
• A payment provider that supports extending authorizations (see Supported payment providers)

Configuration Properties

This task has no configurable properties. The five-day window is fixed, and the task applies to all payment methods. Which payments it finds depends on the authorization expiry date stored on each payment (authorizationExpires on the order's payments). These payment type settings affect the task:

Behavior

Which payments the task extends

The task extends a payment when all of these apply:

1. Its authorization expiry date has not passed yet and is before midnight (UTC) five days from today
2. The payment is still active in Omnium - for example, it is not voided and not all of its transactions failed
3. Part of the authorized amount is not captured yet
4. The order has no earlier extension error for the same payment method (see Retry after an error)

Every run checks all orders with an expiry date in the window. The task does not limit itself to orders changed since the last run.

What It Does

1. Searches for orders with a payment whose authorization expires within the window
2. For each payment that qualifies, asks the payment provider to extend the authorization
3. When the provider extends the authorization:
   • Adds an authorization transaction to the payment with the comment "Extended authorization time"
   • When the provider returns a new expiry date, clears the expiry dates on the order's existing authorization transactions and stores the new date on the new transaction
   • Adds an event log entry: "Extended authorization time for transaction <transactionId>"
4. When the extension fails, adds an error to the order (see Error Handling)
5. Saves the updated orders in batches

The run result reports the number of extended authorizations and the number of errors.

Supported payment providers

Other payment providers do not support extending an authorization:

• Skipped without changes: Authorize.Net, Bonus Points, NGenius, PayEx, PayPal, Vipps (Legacy), Vipps ePayment, Webhook payment, B2B account balance, cash, payment terminals, gift cards, and empty payment types
• Order error "not implemented": Aera, Aera Invoice, Atome, Avarda, Dintero, Generic Payment, Netaxept, Nets Easy, Qliro, Resursbank, Shopify Payments, Stripe, Toss, Zaver, and vouchers

Prerequisites

• Payments must have an authorization expiry date. Some providers set it when the payment is authorized; otherwise use the Set Authorization Expires workflow step with Authorization time in days on the payment type
• The payment type must be configured with valid provider credentials

Side Effects

• Adds authorization transactions to extended payments
• Replaces the authorization expiry date on the order when the provider returns a new one
• Adds event log entries for extended authorizations
• Adds order errors for failed or unsupported extensions
• Adds a failed authorization transaction when the provider rejects the extension

Error Handling

The order error has the key PaymentExtendAuthError<PaymentMethodName>, where <PaymentMethodName> is the payment's Payment Service (paymentMethodName), for example PaymentExtendAuthErrorWalley. Its severity is error. When the provider rejects the extension, Omnium also records a failed authorization transaction with the provider's error message on the payment, and the provider may add its own error to the order.

Retry after an error

While the order has a PaymentExtendAuthError<PaymentMethodName> error, the task skips that payment method on the order. An error marked as solved still counts. Remove the error from the order to have the next run try again, as long as the authorization has not expired yet.

Example Configuration

{
    "ImplementationType": "ExtendPaymentAuthOrderScheduledTask",
    "Schedule": "0 2 * * *",
    "IsDisabled": false
}

Recommended Schedule

Run once a day (0 2 * * *). An authorization enters the five-day window several days before it expires, so a daily run reaches it in time. After a failed extension, the task does not try that payment method on the order again until you remove the error.

Related Tasks

• Set Authorization Expires - Set the authorization expiry date that this task reads
• Remove Authorization Expires - Clear the expiry date after capture
• Payment Settlements - Retrieve settlement data from payment providers
• Payments - Payment provider configuration