Urgent.News

What's breaking now, across thousands of outlets.

Tech

Auditing the Gaps Around Recurly's Own Dunning

Recurly ships a serious dunning system. Automated retries, account updater integrations, and configurable campaigns handle the mechanical core of failed-payment recovery competently, and teams evaluating their stack should start from that respect rather than from a sales pitch. The interesting question for an operator is narrower: where does the platform's machinery stop, and what quietly falls…

Recurly's automated dunning system handles the technical aspects of failed-payment recovery effectively. When evaluating a billing stack, the focus should shift to identifying where the platform's capabilities end and the gaps begin. A gap audit examines a one-month period of failed renewals, categorizing each outcome into three groups: recovered by the platform, recovered with human intervention, and never recovered.

The human-intervention category offers the most insight. By examining twenty of these cases closely, patterns emerge showing situations where judgment, timing, or conversation successfully resolved issues beyond the platform's capabilities. The never-recovered group is also significant. Some cases are final due to closed accounts, replaced cards, or customers who have moved on.

Others are soft failures that aged out of the campaign window, had schedules misaligned with the customer's payment frequency, or received unspecific messages that failed to prompt action.

Addressing these gaps does not require replacing the billing platform. Instead, it involves adding layers of reading and responding to the existing machinery. This could include classifying declines as they occur rather than waiting for monthly reports, running outreach in parallel with retries, and adapting the response cadence based on customer behavior instead of sticking to a fixed schedule.

When conducting a gap audit, it is crucial to sample honestly by pulling the actual data as it happened, not just the cases that stand out. Separating configuration issues from coverage issues before making any purchases is also essential. Issues with campaign timing, updater connections, or notice sequences are often settings that can be easily fixed. Coverage problems, however, require a fundamentally different approach, as no platform setting alone can create a conversation or sequence a response.

Audits should be performed quarterly to account for platform updates, changes in card usage, and evolving churn patterns. Maintaining an accurate, current map of billing platform capabilities helps teams identify where their recovery efforts should focus. This approach, as advocated by Swipe Again, emphasizes auditing first to gain a deeper understanding of renewals and then layering additional reading and response mechanisms on top of the existing platform to effectively close the identified gaps.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Serving Sage-A1.5 on an RTX 4090: one broken flag, one queue, and a self-check mode to measure

Run Sage-A1.5 as a research agent on your own card and the surprises are not in the model. They hide in a reasoning flag, a request limit, a token budget and one system prompt string.

  • Sage-A1.5 runs efficiently on a single RTX 4090 with compressed 22 GB GGUF file
  • Reasoning flag and sub-agents may cause compatibility issues with llama.cpp
  • Verification mode improves accuracy on BrowseComp benchmark from 72.5% to 82.9%

How we check every hour that our PDF API stores nothing

Every hour, a script sends a document with a unique marker through our public API, then searches our logs, temp files, containers and database for it.

  • Hourly script tests PDF API for no document storage
  • Unique marker placed in HTML document for detection
  • Test results published publicly for transparency

How to clean a supplier product CSV before importing to Shopify

By Zijian Xiao A supplier spreadsheet can look perfectly readable and still need work before you import it. Product names sit under unfamiliar headers, a price uses a decimal comma, and an SKU has…

  • Make a copy of original CSV to avoid data loss
  • Identify relevant columns for title, SKU, price, barcode
  • Export corrected CSV in UTF-8 format for Shopify import

How to scrape Workday job postings (and the 2,000-job trap)

Thousands of large employers (Nvidia, Salesforce, Adobe and much of the Fortune 500) publish their jobs on Workday. Unlike Greenhouse or Lever, Workday has no documented public API and no global…

  • Workday job postings scraped via JSON endpoint with tenant, data center, and site name
  • 2,000-job wall limits total listings; duplicate entries risk if pagination ignored
  • Relative dates require detail endpoint for accurate posting dates

More from Sunday 8 November →