Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Features and Overview
  • Receivables Tech Glossary
  • Receivables Metrics Formulae

Multi-Tenant


  • Multi-Tenant Login

Account Hierarchy


  • Account Hierarchy

Multi Business Entity


  • Managing Receivables for Customers from Multiple Business Entities

Account Receivables


  • AR Dashboard
  • Collector Queue
  • Receivables View

Payment Failure Recovery


  • Payment Failure Management
    • Data Visibility
    • Automating Payment Failure Management

Management and Configurations


  • User Management
  • Configuring Account Statement
  • Configuring Reminder Invoice List
  • Configuring Collection Status
  • Configuring Self Serve Client Portal
  • Configuring Ledger Statements
  • Use Your Own SMTP Server

Communications


  • Automations
  • Email and SMS Templates

Reports


  • Receivables Reports
  • PFR Reports

Analytics


  • Receivables Analytics
  • Payment Metrics
  • Payments

Customers


  • Managing Customer Details
  • Self Serve Client Portal
  • Configure Multiple Languages
  1. Receivables
  2. Payment Failure Recovery
  3. Payment Failure Management
  1. Receivables
  2. Payment Failure Recovery
  3. Payment Failure Management

Payment Failure Management

Introduction

Payment failures occur for customers whose payments are collected either by automatically charging their card or debiting their account via direct debit. Payments can fail for multiple reasons, such as insufficient funds, invalid cards, expired cards, and more. When payments fail, retries are activated and operate in the background.

Payment Failure Management

For Receivables, every customer is unique; therefore, our approach is to engage them and transform their payment failures into successes. As a result, the offering revolves around provisioning multiple cohorts of customers based on their payment patterns, retries, payment methods, email engagement, overdue status, aging buckets, and other value-added fields.

It is an easy and engaging three-step process: Identify the cohort, Engage with the cohort, and Recover from the cohort.

Payment Failure Recovery comprises the following segments:

  1. Data visibility
  2. Automating payment failure management

// Feedback summary: // - Use American English spellings (e.g., "aging" instead of "ageing"). // - Use "and" instead of "&" in running text. // - Use the Oxford comma in lists. // - Use em dashes (—) for parenthetical statements, not double hyphens or en dashes. // - Use sentence case for headings unless referring to UI elements. // - Use consistent casing for UI labels. // - Use parallel structure and punctuation in bullet and numbered lists. // - Clarify passive or wordy sentences for directness and clarity. // - Tone is generally clear and instructional, but can be more concise and direct in some places. // - No date format issues found. // - Markdown and formatting are consistent.

Was this article helpful?