# No Backup Payment Alert

A self-service component that warns subscribers when their default payment method has no backup on file. The alert only appears when it's relevant — if the subscriber already has a valid backup method, the component stays hidden.

When shown, it displays the subscriber's card details (brand and last four digits) and a configurable CTA to add a backup method. Fully configurable through the Page Builder — heading, description, colours, and CTA destination are all prompt-driven.

<figure><img src="https://430995084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSe5wc9RXUPzSYeMZJDNj%2Fuploads%2FhD9dpvyYM3v1EG3W5Sri%2FScreenshot%202026-03-24%20at%2013.15.54.png?alt=media&#x26;token=297b7a82-3624-4c18-9c48-f7b42e817955" alt=""><figcaption></figcaption></figure>

The component is built to be used alongside [Component: Saved Payment Methods](https://app.gitbook.com/s/AIj7bFbTc7K2038CWL50/component-library/self-service-components/component-saved-payment-methods "mention"), however it can be used anywhere within Limio Self-Service.

## How it works

The component reads the subscriber's payment methods via the Limio SDK. It checks whether a default payment method exists and whether any other non-expired methods are on the account. If there's a default but no backup, the alert renders with the subscriber's actual card details injected into the copy via template variables (`{{brand}}`, `{{last4}}`).

Payment methods without expiry dates — like Direct Debit, PayPal, or Bank Transfer — are treated as valid backups, so the alert won't fire unnecessarily for those payment types.

In the Page Builder, the component renders with placeholder values so it can be positioned and styled without needing live payment data.

## Configuration

Everything is configurable through Page Builder prompts:

* **Heading and description** — fully customisable copy with `{{brand}}` and `{{last4}}` template variables
* **CTA button** — configurable text and destination URL (e.g. link to your add-payment-method page)
* **Colours** — background, border, and text colour to match your brand or convey the right level of urgency

## Placement

Designed to sit alongside the saved-payment-methods component on a self-service payment management page. It matches the same grid layout (724px on desktop, full-width on mobile) for visual consistency.

## Why it matters

Failed payments are the leading cause of involuntary churn. Proactively prompting subscribers to add a backup method before their primary card fails reduces failed payment rates and the support overhead that comes with them.

{% hint style="warning" %}
**Zuora users:** Zuora does not automatically fall back to backup payment methods when the default fails. You need to enable [Cascading Payment Methods](https://docs.zuora.com/en/zuora-payments/payment-orchestration/cascade-payment-methods/overview) for that. Without it, having a backup on file won't prevent a failed billing run.
{% endhint %}

***

{% hint style="info" %}
**This is a Labs feature.** We're experimenting with this and it's not yet part of the core platform. Interested in early access or want to help shape it?

[Request access →](mailto:hello@limio.com?subject=Labs%20—%20No%20Backup%20Payment%20Alert)
{% endhint %}