# Display Smart Subscriptions
source: https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-subscription-controls/index.md

## Overview {#overview}

While cardholders are viewing their transactions within your banking app, you can provide them with the ability to **view** and **manage** their subscriptions.

**Smart Subscriptions** is a solution available within the Consumer Clarity and Smart Subscriptions APIs that delivers recurring--payment and subscription information directly to your digital banking channel. Providing this information to your cardholders lets them manage their subscriptions from a centralized and trusted source.

Take a look at our [API Reference](https://developer.mastercard.com/consumer-clarity/documentation/api-reference/index.md#apis) information for details about the Smart Subscriptions fields and values relevant to your specific needs.

## Transaction View {#transaction-view}

Typically, you display the Smart Subscriptions response data in your banking app in a **transaction view**. This shows the cardholder whether a particular transaction in their list of transactions is a subscription that can be managed.

### Show a subscription in transaction view {#show-a-subscription-in-transaction-view}

When you display transactions to your cardholder, you can also provide any subscription information associated with a transaction in a transaction view. This image shows an example of how you can display the response data for `recurringPaymentType` and `frequency` in your banking app:
![Transaction View in Response Data](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/transaction-view.png)
Note: We currently accept up to 50 transactions per request. When sending multiple transactions, they must all be sent against a single unique card. Subscription information can only be retrieved for a unique card.

## Subscription Hub View {#subscription-hub-view}

The Subscription Hub lets cardholders view and manage all their subscriptions from a centralized location within your digital banking application. This service streamlines subscription oversight and enhances user control, providing your cardholders with a comprehensive user experience.

The Subscription Hub provides these key features:

* **User's subscription list** : Each subscription listing includes detailed context, such as the available management actions (for example, **Cancel** and **Change plan**), previous payment history, next payment date, and ongoing or recently completed actions.

* **Upcoming payments**: You can provide users with a view of upcoming subscription payments to ensure they are aware of them, which reduces surprises of recurring charges.

* **Monthly spend summary**: You can also provide users with a total of the amount spent on subscription transactions per calendar month.

* **Real-time updates**: Webhooks communicate the status of subscription actions in near real time.

Since the Subscription Hub service is delivered through the Consumer Clarity API, you can incorporate other assets or functionality within your banking application (such as spend tracking) for an enriched, personalized experience for your users.

#### How Subscription Hub works {#how-subscription-hub-works}

There are two aspects to implementing the Subscription Hub: the **data sharing flow** and the **real-time API flow**. The data sharing flow is a prerequisite for the real-time flow.

##### Data sharing flow {#data-sharing-flow}

The **data sharing flow** is an ongoing background process required to enable the real-time flow.

1. On a regular schedule, you must provide Ethoca with a batch of transaction data for all users that have access to the subscription hub functionality. The data required is a limited set of transaction-related fields and the payment account identifier. This data is used only for the purpose of delivering this service.

2. Ethoca processes the transaction data to identify subscriptions for each user's payment account and persists this information for reference.

3. During the [real-time flow](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-subscription-controls/index.md#real-time-api-flow), Ethoca uses the account identifier you provided to reference and return the subscription listings persisted for the user.

4. You then display the subscription listings and contextual details through your banking application to meet user needs.

##### Real-time API flow {#real-time-api-flow}

The **real-time API flow** occurs when a user signs in to your banking app and wants to view subscriptions.

1. A user signs in to their banking app and visits the Subscription Hub page.

2. You send Ethoca an API request to the `/listings` endpoint with an identifier that represents the user's payment account.

3. Ethoca looks up the account identifier and responds back with the subscription listings that are currently stored against the account identifier.

4. You display the subscription listings to the user so they can view and interact with them further, if they want, such as requesting a **Cancel**.

5. Then, if a user opts to perform an action, such as **Cancel** , you can take them into the action flow through the [Subscription Actions endpoint](https://developer.mastercard.com/consumer-clarity/documentation/use-cases/index.md#managing-a-subscription).

Diagram diagrams-sub-cntrl-hub-flow

For more information about the the **data sharing flow** and the **real-time API flow** , see [Data sharing for Smart Subscriptions](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/tips-for-sending-requests/index.md#data-sharing-for-smart-subscriptions).

### Create an engaging Subscription Hub {#create-an-engaging-subscription-hub}

When you create a Subscription Hub, we recommend you at least include a list of a cardholder's active subscriptions. This list can display the merchant or service name, the subscription amount, the billing frequency, and a management call-to-action, such as **Cancel**.

A more advanced experience might also include upcoming payment details, like expected charges in the next 14 days or by calendar month. You can also include things like subscription spend tracking, a history of user actions, and other recent subscription-related transactions.

## Take Action on Subscriptions {#take-action-on-subscriptions}

Smart Subscriptions empowers your cardholders by letting them manage their subscriptions within your banking application.

75% of chargebacks related to subscriptions occur because a cardholder is unable to cancel a subscription. Smart Subscriptions provides the ability to **Cancel** a subscription, along with other actions such as **Upgrade** , **Downgrade** , **Pause / Resume** , and **Retention offers**.

Here is some best practice guidance for how you can implement a **Cancel** flow based on the response data returned in the Consumer Clarity API. The guidance shown is for both the automated and self-serve cancellation flows.

* **Automated cancellation**: We perform the cancellation directly with the merchant on behalf of the cardholder.

  ![Transaction View in Response Data](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/automated-cancellation.png)

<br />

* **Self-serve cancellation**: We provide instructions and links to the action page on the merchant's website where cardholders can cancel the subscription themselves. This is most common in cases where the subscription is paid through a third party, such as Apple Pay, Google Pay, or PayPal.

  ![Transaction View in Response Data](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/self-serve-cancellation2.png)

## Next Steps {#next-steps}

* [Display Transaction Details](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-transaction-details/index.md) offers tips for how to display all transaction detail response data in your banking app.
* [Display Merchant Details](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-merchant-details/index.md) suggests different ways you can use the merchant detail response data in your banking app.
* Understand the policies for [Caching the Response Data](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/caching-response-data/index.md) you receive from the Consumer Clarity API.
* Review [Tips for Sending Requests](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/tips-for-sending-requests/index.md) for suggestions to consider when sending your requests.