> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Send a Card Payment Reminder
# Introduction
Banks send card payment reminders to prompt customers to pay their credit card bills before the due date. Failed payments or late fees might jeopardize the bank's relationship with users or even lead to churn. Consistent reminders about upcoming bills can prevent unfortunate scenarios of missed payments due to forgetfulness.
#### Advantages of sending card payment reminders
* **For customers:**
* **Avoids missed payments**: Reminders ensure customers are aware of upcoming due dates, preventing accidental late payments.
* **Prevents late fees**: Timely payments avoid incurring costly late fees, which can be a significant financial burden.
* **Maintains credit scores**: Missed or late payments can negatively impact credit scores, making it harder to secure loans or credit in the future.
* **Increased trust and satisfaction**: Reminders demonstrate a commitment to customer service and can increase trust and satisfaction with the bank.
* **For businesses:**
* **Improves cash flow**: Timely payments ensure a steady revenue stream, allowing businesses to manage their finances effectively.
* **Reduces outstanding debts**: Reminders help businesses collect payments on time, minimizing the risk of outstanding debts.
* **Enhances customer relationships**: Proactive communication about payments can improve customer relationships and build trust.
We will achieve this use case by [creating a Push campaign](/use-cases/push/send-a-card-payment-reminder#create-a-push-campaign) to remind users about pending credit card payments 5 days before the due date.
# Expected Result
Users receive a push notification about their credit card payment on their phones:
* Events must be available in MoEngage to track the action of generating a bill for a user and related information such as the card ID, bill amount, credit card name, and due date. In this example, we will name the event *Bill generated*. Also, this event should be configured to occur before we send the reminder about the due date. To understand how to track events, refer to the [Developer Guide](/developer-guide/introduction).
* Events must be available in MoEngage to track the action of bill payment by a user and related information such as the card ID, bill amount, paid amount, credit card name, and due date. In this example, we will name the event *Bill Paid*.
* The [Push channel](/user-guide/campaigns-and-channels/mobile-push/getting-started-with-mobile-push) must be configured.
* The [Linked Conditions](/user-guide/flows-cross-channel-messaging/create/create-flows/linked-conditions) feature must be enabled for your account.
# Create a Push Campaign
In this section, we will create a Push campaign to remind users about their pending credit card payments.
## Step 1: Target Users
1. On the left navigation menu in the MoEngage dashboard, click **Engage**, and then click **Campaigns**.
2. On the All campaigns page, click **+ Create campaign**.
3. Under **Outbound**, click **Push** > **Event Triggered**. 
You are taken to the first step, **Target users**, of defining your campaign.
4. Define your campaign with a name and tags. Enter the following details:
* **Team**: Select a team if your organization has teams enabled for your account. For more information, refer to [Teams in MoEngage](/user-guide/settings/account/team-management/teams-in-moengage).
* **Campaign name**: Enter a name for the campaign. For example, *Remind users about card payment*.
* **Campaign tags**: Select the required campaign tags. 
5. In the **Trigger Criteria** section, define the trigger condition.\
A user can have more than one credit card, and you must remind them specifically of the card that they have not yet paid after the bill was generated. Therefore, the check must be dynamic, not static. For a user with bills generated for cards 1 and 2, you must look for the purchase event with the attribute pointing to each card and send a reminder for the card that does not have a *Bill Paid* event. To achieve this, we must use Linked Conditions while defining the trigger condition.
6. To define the dynamic check mentioned above:
1. In the **IF user** section, select *Bill generated* and then click **+ Filter** to add the additional check.
2. In the **AND then** section, select *Has not executed* from the first list and *Bill Paid* from the **Select an event** list.
3. Click **+ Attribute** and select *Card ID* because it is a unique attribute that can help you identify the card.
4. Select the *is* operator because you want an exact match.
5. Change *Constant Value* to *Event Attribute* because this value will change with the user and the card, and so referring to the *Bill generated* event will make the check personalized for each possible situation of a user.
6. Select the *Card ID* attribute of the *Bill generated* event from the list of attributes. This can help you compare the card for which the *Bill Paid* event is coming.
7. In the **THEN trigger the message** section, define the **With Delay** option to send a reminder to the user 5 days before the due date. This is the maximum time the user will be evaluated to fulfill the conditions from when the first condition is met.\
The **Select condition** section looks as follows now: 
The selected attribute must be in the supported format for the abovementioned filter to work correctly. For more information, refer to [Create an Event-Triggered Campaign](/user-guide/campaigns-and-channels/getting-started/triggers/event/create-an-event-triggered-campaign).
8. In the **Target audience** section, select **All users**.
9. In the **Target Platforms** section, select **Android**. 
10. Click **Next** to move to the second step, **Content**, where you can define the content for your Push campaign.
## Step 2: Content
1. Select the template that you would like to use. For example, select **Basic notification**. 
2. Enter the required title and a message for the campaign. We can enter the content manually or generate it using Merlin AI. For more information, refer to [Generate Push Messages with Merlin AI](/user-guide/ai-and-intelligence/merlin-ai/merlin-ai-copywriter/generate-push-messages-with-merlin-ai).
3. Add personalization to the message using information such as the user's name, bill amount, or credit card name. Such personalization makes the message more contextual for users with multiple cards. To do the same:
1. Type *@*.
2. On the **Push Personalization** dialog box, find your event attributes, such as bill amount, credit card name, or user attributes, such as name. 
3. Click **Done**.\
You can select the attributes based on your requirements. Selecting a name and other personalization makes the message content look something as follows: 
Whenever MoEngage tries to send a message, it makes sure to check the name of the user, credit card name, and amount from the *Bill generated* event and replace those instead of `{{UserAttribute['Name']}}`, `{{EventAttribute['Credit card name']}}`, `{{EventAttribute['amount']}}` respectively.
4. Use the deep link option to take the users to the bill payment page in your app.
1. In the **Default click action** list, select *Navigate to a screen*.
2. In the **Take user to a specific screen** list, select the respective screen. 
5. Click **Next** to move to the third step, **Schedule and goals**, where you can define your campaign's schedule and goals.
## Step 3: Schedule and Goals
1. Define when to start and end this campaign and the conversion goal based on your requirements. 
2. Change the deliverability settings based on your requirements. For more information, refer to [Create Push Campaigns](/user-guide/campaigns-and-channels/mobile-push/create/create-push-campaigns). 
3. Click **Publish**.
# Conclusion
In this use case, we created a Push campaign to remind users about pending payments for their credit cards 5 days before the due date.