Skip to main content
On this page

Subscriptions and Recurring Payments focuses on protecting recurring revenue while respecting customer consent, credential lifecycle, provider requirements, and merchant retry policy. This page describes the concepts involved, not a public schema or batch-file specification.

What the use case covers#

Business information domains#

The capability can use subscription and invoice lifecycle context, recurring charge attempts and outcomes, approved credential status, recovery actions, customer communication state, and later commercial outcomes. The authoritative source for each concept depends on the merchant's billing, payment, and customer systems.

DEUNA confirms the deployment-specific mapping and any supported file or API interface during enablement. Do not infer a required column, enum, or delivery format from this overview.

Readiness and control#

  • Separate the customer-approved setup from later merchant-initiated execution.
  • Preserve consent, credential, subscription, invoice, charge, and outcome lineage.
  • Define recovery eligibility, timing, maximum attempts, communication, and cancellation behavior.
  • Reconcile an unknown outcome before another financial attempt is created.
  • Keep credential secrets and unnecessary personal data outside analytics and free-text inputs.
  • Measure recovery, involuntary churn, customer impact, cost, and dispute outcomes together.

Continue with Recurring Commerce, Subscriptions, and Source Mapping Guidance.