RefreshDECLINE RECOVERY

Retry declined
charges on your terms

Build merchant-defined retry rules and apply them where they matter. Scope each rule to a subscription type, invoice category, one-time purchase, specific product, amount range, or customer segment. For each attempt in the rule, set the delay, toggle Account Updater refresh, and pick which email or SMS notifications go out before or after. Use custom schedules or hand the timing off to AI. Up to four attempts within thirty days.

Move across the attempts

Merchant-defined
recovery logic

  • 6 Rule Scopes

  • 4 Attempts per rule

  • AI Optional

Setting2HOW IT WORKS

Three steps, fully
merchant-controlled

Define a rule, configure the attempts, and Worthy runs the sequence on every matching decline. Rules can be merchant-wide or narrow to one segment. Nothing happens by default. You decide what gets retried, how often, and what the customer hears about it.

step 01

Define the rule

Pick what the rule applies to: a subscription product line, invoice category, single product SKU, amount range, or customer segment. Rules can chain, so a charge that matches multiple rules runs the most specific one.

step 02

Configure each attempt

Pick what the rule applies to: a subscription product line, invoice category, single product SKU, amount range, or customer segment. Rules can chain, so a charge that matches multiple rules runs the most specific one.

step 03

Recovery runs automatically

Every charge that matches an active rule enters its recovery sequence the moment it declines. Worthy executes the attempts on schedule, fires the configured notifications, and emits webhooks at every step. Stops on first success.

Rule BuilderRULE BUILDER

Build the schedule
yourself or let AI build it

Pick the delay between attempts, the Account Updater behavior, and the customer notifications for each step. Custom mode gives you full control. AI mode reads the customer's purchase history and sets the delays for you, retraining as new charges complete.

ATTEMPT 1

active
  • Notify customer 4 hours before retry

  • Refresh card via Account Updater

    EMAIL

  • Notify customer if retry fails

    EMAIL

ATTEMPT 2

active
  • Notify customer 4 hours before retry

  • Refresh card via Account Updater

    EMAIL

  • Notify customer if retry fails

    EMAIL

ATTEMPT 3

active
  • Notify customer 4 hours before retry

  • Refresh card via Account Updater

    EMAIL

  • Notify customer if retry fails

    EMAIL

ATTEMPT 4

active
  • Notify customer 4 hours before retry

  • Refresh card via Account Updater

    EMAIL

  • Notify customer if retry fails

    EMAIL

Rule_1

DELAY

+24 hours

Subscription_recoverywhencharge.type === "subscription

Switch this rule to AI auto-optimize and Worthy picks the delay for each attempt from the customer's purchase history.

CommandAI AUTO-OPTIMIZE

Worthy reads each customer's actual payment rhythm

Switch any rule to AI mode and Worthy stops using fixed delays. Instead, it analyzes the customer's prior purchase activity, picks the days and times their charges typically succeed, and schedules each attempt accordingly. The model retrains every twenty-four hours. Recovery rates run roughly twenty to thirty percent higher than fixed schedules on most segments.

Recovery performance uplift

AI-optimized retry timing increases recovery rates compared to fixed payment schedules.

0%

AI AUTO-OPTIMIZE

FIXED SCHEDULE

0%

AI AUTO-OPTIMIZE

RECOVERY RATE

+0%

DIFFERENCE

RELATIVE LIFT

GlobalOBSERVABILITY

Every rule, every
retry, every dollar

Track recovery rate by rule, attempt, and mechanism. Filter by scope to compare subscription recovery against invoice recovery, or compare AI mode against custom schedules. Drill into any charge to see which rule fired and how the sequence ran.

Laptop CodeDEVELOPER API

Define rules through code

Manage every rule through the API. Define the scope, set the attempt schedule, and ship rules through your existing release process. Per-charge overrides supported.

Create a rule that scopes recovery to subscription charges.

  • scope picks which charges this rule applies to.

  • mode is custom or ai_optimize.

  • mode is custom or ai_optimize.

  • mode is custom or ai_optimize.

{
  "name": "subscription_recovery",
  "priority": 2,
  "scope": {
    "match": { "charge.type": "subscription" }
  },
  "mode": "custom",
  "attempts": [
    {
      "delay_seconds": 86400,
      "account_updater": true,
      "outreach": {
        "before": { "hours": 4, "channels": ["email"] },
        "after": { "channels": ["email"] }
      }
    },
    {
      "delay_seconds": 345600,
      "account_updater": true,
      "outreach": {
        "before": { "hours": 12, "channels": ["email", "sms"] },
        "after": { "channels": ["email", "sms"] }
      }
    }
  ]
}		

PAIRS WELL WITH

Decline Recovery sits next to the rest of your acceptance stack

Network Tokenization keeps card credentials current between billing cycles. Smart Routing picks the best processor for every retry. Subscriptions wires Decline Recovery rules into every billing cycle automatically.

Network Tokenization

Network-issued tokens that auto-update with the card. Reduces declines at the source so recovery runs less often.

Smart Routing

Every retry runs through the processor most likely to approve it. Pairs naturally with rule-based recovery.

Subscriptions

Recurring billing with Decline Recovery rules built into every cycle. Pick the rule per plan or per product.

Decline Recovery

Merchant-defined retry rules scoped by subscription, invoice, one-time purchase, product, amount, or customer segment.

FlashREADY WHEN YOU ARE

Recover the revenue
that should already be yours

Apply for a Worthy account and configure Decline Recovery rules through the dashboard or API. No contracts, no setup fees, no engineering team required. Talk to sales for a custom package or volume pricing.