Skip to main content

Transactional Push Notifications - Automatic Purchase Confirmations

Learn how transactional push notifications work. Complete guide to automatic transaction confirmations, customizing stamp and multipass card messages, using the # placeholder, and best practices for real-time alerts.

Michael Francis avatar
Written by Michael Francis
Updated this week

Transactional Push Notifications

Overview

Transactional push notifications are automatic alerts sent to customers immediately after loyalty card transactions. These system-generated messages confirm actions like earning stamps, adding points, redeeming rewards, or updating balances, providing real-time feedback on customer activity.

What transactional push notifications do:

  • Confirm transactions instantly (points earned, stamps added, rewards unlocked)

  • Build customer confidence in the loyalty programme

  • Provide immediate gratification for purchases

  • Keep customers informed of their progress

  • Reinforce the value of your loyalty programme

Unlike manual push notifications or scheduled campaigns, transactional notifications are triggered automatically by customer actions and send without your intervention. For most card types, these messages are system-generated and cannot be edited. However, stamp cards and multipass cards offer limited customisation options.


Before You Begin

Important to understand:

  • Transactional push notifications are automatic - they send when transactions occur

  • Most are system-generated and cannot be edited

  • Only stamp cards and multipass cards allow limited customisation

  • The # placeholder is mandatory in editable messages (used for dynamic values)

  • Customers must have cards installed to receive transactional notifications

Card types covered:

  • Stamp Cards - Partially editable

  • Multipass Cards - Partially editable

  • Cashback Cards - System-generated only

  • Discount Cards - System-generated only

  • Gift Cards - System-generated only

  • Coupon Cards - System-generated only

  • Membership Cards - System-generated only

  • Reward Cards - System-generated only


Understanding Transactional Push Notifications

What Are Transactional Notifications?

Transactional push notifications are automated messages triggered by specific customer actions:

Common triggers:

  • Customer makes a purchase and earns stamps/points

  • Customer reaches a reward milestone

  • Card balance changes (points added or deducted)

  • Reward is redeemed or used

  • Visit is added to a multipass card

  • Gift card balance is updated

  • Membership status changes

Key characteristics:

Automatic delivery:

  • Sent immediately after transaction

  • No manual intervention required

  • Triggered by system events

  • Real-time customer feedback

Transaction confirmation:

  • Verifies action was completed

  • Shows what customer earned or redeemed

  • Updates current balance or status

  • Builds trust and transparency

System-managed:

  • Most cannot be edited or customised

  • Ensure consistency across customer base

  • Professional, standardised messaging

  • Reduces risk of errors in critical communications

Why Transactional Notifications Matter

Customer benefits:

  • Instant confirmation - Customers know their action was recorded

  • Progress tracking - See how close they are to rewards

  • Motivation - Immediate gratification encourages repeat visits

  • Trust building - Transparency in loyalty programme operation

Business benefits:

  • Engagement - Keeps customers thinking about your programme

  • Automation - No manual effort required

  • Consistency - Every customer receives same clear messaging

  • Satisfaction - Reduces customer service inquiries ("Did my points post?")

Example scenario: Customer buys coffee → Earns stamp → Receives notification: "Great! You earned 1 stamp. 7 more until your free coffee! ☕" → Customer feels progress and motivation to return.


Card Types and Editability

System-Generated Only (Cannot Edit)

The following card types use system-generated transactional push notifications that cannot be customised or edited:

Cashback Cards

Transactional notifications sent:

  • Points/cashback earned after purchase

  • Cashback balance updated

  • Tier progression achieved

  • Cashback redeemed or used

Why not editable:

  • Involves monetary values requiring precise accuracy

  • Financial transaction confirmations need standardisation

  • Reduces risk of confusion about cash value

Discount Cards

Transactional notifications sent:

  • Discount applied to purchase

  • Discount card activated or used

  • Discount level or tier changes

Why not editable:

  • Discount percentages must be communicated accurately

  • Standardised messaging prevents confusion

  • Clear terms required for legal compliance

Gift Cards

Transactional notifications sent:

  • Gift card balance loaded or updated

  • Gift card purchase confirmed

  • Balance used or deducted

  • Remaining balance after transaction

Why not editable:

  • Financial instrument requiring precise messaging

  • Balance accuracy is critical

  • Regulatory and accounting considerations

Coupon Cards

Transactional notifications sent:

  • Coupon earned or unlocked

  • Coupon redeemed or used

  • New coupons available

  • Coupon expiration reminders

Why not editable:

  • Offer terms must be clearly communicated

  • Standardised messaging prevents misunderstandings

  • Legal compliance for promotional offers

Membership Cards

Transactional notifications sent:

  • Membership activated or renewed

  • Membership tier changes

  • Membership benefits unlocked

  • Expiration notices

Why not editable:

  • Membership terms require accuracy

  • Status changes must be clearly communicated

  • Benefits and access levels need precision

Reward Cards

Transactional notifications sent:

  • Points earned from purchases

  • Transaction amount credited

  • Reward level achieved

  • Points expiration notices

Why not editable:

  • Point values and calculations must be accurate

  • Reward thresholds require standardised messaging

  • Financial accuracy is paramount

For all these card types: System-generated messages ensure accuracy, consistency, and compliance. While you cannot edit the transactional push notifications, you can still send manual push notifications for marketing, promotions, or customer engagement.

Partially Editable Cards

Only stamp cards and multipass cards allow limited customisation of certain transactional push notifications.

Stamp Cards - Partially Editable

Editable notifications:

  • ✅ Stamp earned notification

  • ✅ Reward earned notification

Non-editable (system-generated) notifications:

  • ❌ Reward redeemed confirmation

  • ❌ Card completed notification

  • ❌ Other system transactions

What you can customise:

  • Message text when customer earns a stamp

  • Message text when customer earns a reward (completes card)

  • Tone and wording (within character limits)

  • Emoji usage (optional)

Customisation location: Card Settings → Information section

Multipass Cards - Partially Editable

Editable notifications:

  • ✅ Balance change notification (visits added or removed)

Non-editable (system-generated) notifications:

  • ❌ Multipass activation

  • ❌ Bonus points earned

  • ❌ Multipass expiration

  • ❌ Other system transactions

What you can customise:

  • Message text when card balance changes

  • Applies to visits added or visits removed

  • Tone and wording (within character limits)

  • Emoji usage (optional)

Customisation location: Card Settings → Information section


Customising Stamp Card Transactional Push

What You Can Edit

For stamp cards, you can customise two specific transactional push notifications:

1. Stamp Earned Notification

  • Sent when customer earns a stamp after purchase

  • Confirms stamp was added

  • Shows progress toward reward

2. Reward Earned Notification

  • Sent when customer completes the card (earns final stamp)

  • Celebrates milestone achievement

  • Notifies reward is now available

Accessing Stamp Card Settings

Step-by-step navigation:

  1. Navigate to your dashboard

  2. Go to Cards or Loyalty Cards section

  3. Locate and select your stamp card from the list

  4. Click Edit or Settings

  5. Find the Information section (may be a tab or section within settings)

  6. Scroll to transactional push notification fields

Editing Stamp Earned Notification

To customise the message sent when customers earn stamps:

  1. In the Information section of your stamp card settings

  2. Locate the "Stamp Earned" or "Transaction Push" field

  3. Click in the text box

  4. Type your custom message

  5. Include the # placeholder where you want the stamp count to appear

  6. Save your changes

The # placeholder:

  • Represents dynamic value (number of stamps earned)

  • Mandatory - must be included in message

  • Cannot be removed or altered

  • System replaces # with actual stamp count when sending

Default system message example: "You earned # stamp(s)!"

Custom message examples:

Basic customisation:

  • "Great! You earned # stamp! Keep collecting! ☕"

  • "Nice! # new stamp added to your card 🎉"

  • "Awesome! You just earned # stamp toward your reward ⭐"

More personality:

  • "Yay! # stamp closer to free coffee! You're doing great! ☕"

  • "Woo-hoo! # stamp earned! We love seeing you! 🎉"

  • "Thank you! # stamp added—you're on your way! ⭐"

With progress encouragement:

  • "# stamp earned! Keep going—you're almost there! 🎯"

  • "Fantastic! # stamp added to your collection! ☕"

  • "Excellent! # stamp earned—rewards are coming! 🎁"

Message guidelines:

  • Keep it under 100 characters for optimal display

  • Place # where the number makes sense grammatically

  • Add emoji for personality (one maximum)

  • Match your brand voice and tone

  • Make it encouraging and positive

Editing Reward Earned Notification

To customise the message sent when customers complete their card:

  1. In the Information section of your stamp card settings

  2. Locate the "Reward Earned" or "Card Completed" field

  3. Click in the text box

  4. Type your custom message

  5. Include the # placeholder if it references stamp count

  6. Save your changes

Default system message example: "Congratulations! You earned a reward!"

Custom message examples:

Celebratory:

  • "🎉 Amazing! You completed your card! Your free coffee is ready!"

  • "Congratulations! # stamps earned = 1 free item! Claim it today! 🎁"

  • "You did it! Free coffee unlocked! Visit us to redeem! ☕"

Action-focused:

  • "Reward unlocked! Come redeem your free item this week! 🎉"

  • "Card complete! Your free coffee awaits—don't forget to claim it! ☕"

  • "Success! # stamps = 1 free item! Visit us to enjoy your reward! 🎁"

Appreciative:

  • "Thank you for your loyalty! Enjoy your well-earned free coffee! ☕"

  • "You're amazing! Your reward is ready—thanks for being a loyal customer! 🎉"

  • "We appreciate you! # stamps collected—come claim your free item! ⭐"

With urgency:

  • "Reward ready NOW! Visit us this week to claim your free item! 🎁"

  • "Card complete! Come enjoy your reward before [date]! ☕"

  • "Free item unlocked! Visit us soon—rewards don't last forever! 🎉"

Testing Your Custom Messages

Before finalising:

  1. Save your custom messages

  2. Issue yourself a test stamp card

  3. Install the card on your device

  4. Process a test transaction (add stamp via scanner app or dashboard)

  5. Check your device to see the notification

  6. Verify:

    • Message displays correctly

    • # placeholder is replaced with correct number

    • Character length doesn't truncate message

    • Emoji appears properly

    • Tone matches your brand

Refine if needed:

  • Shorten if message is cut off

  • Adjust emoji placement

  • Rework unclear phrasing

  • Test on both iOS and Android if possible


Customising Multipass Card Transactional Push

What You Can Edit

For multipass cards, you can customise one transactional push notification:

Balance Change Notification

  • Sent when visits are added to the card

  • Sent when visits are removed from the card

  • Confirms balance update

  • Shows current remaining visits

Non-editable multipass notifications:

  • Bonus points earned

  • Multipass activation

  • Multipass expiration

  • Other system events

Accessing Multipass Card Settings

Step-by-step navigation:

  1. Navigate to your dashboard

  2. Go to Cards or Loyalty Cards section

  3. Locate and select your multipass card from the list

  4. Click Edit or Settings

  5. Find the Information section

  6. Scroll to transactional push notification field

Editing Balance Change Notification

To customise the message sent when card balance changes:

  1. In the Information section of your multipass card settings

  2. Locate the "Balance Change" or "Transaction Push" field

  3. Click in the text box

  4. Type your custom message

  5. Include the # placeholder where you want the visit count/balance to appear

  6. Save your changes

The # placeholder:

  • Represents the dynamic balance value (visits remaining or added)

  • Mandatory - must be included in message

  • Cannot be removed or altered

  • System replaces # with actual number when sending

Default system message example: "Your balance changed. Visits remaining: #"

Custom message examples:

Visit added:

  • "Great! Visit added! You have # visits remaining on your pass 🎉"

  • "# visits left on your multipass—keep enjoying! ☕"

  • "Thank you! # visits remaining. See you again soon! ⭐"

Encouraging progression:

  • "Awesome! # visits left to use—make the most of your pass! 🎯"

  • "# more visits on your multipass! We love seeing you! 🎉"

  • "Visit logged! # remaining—you're getting great value! ☕"

With urgency (if expiration applies):

  • "# visits remaining! Don't let them expire—visit us soon! ⏰"

  • "You have # visits left—use them before [date]! 🎁"

  • "# more chances to visit! Make them count! 🎉"

Appreciative tone:

  • "Thanks for visiting! # visits remaining on your pass 🎁"

  • "We appreciate you! # more visits to enjoy ☕"

  • "You're valued! # visits left—keep coming back! ⭐"

Message guidelines:

  • Message applies to both additions and removals

  • Keep generic enough to work in both scenarios

  • Focus on remaining balance (# visits left)

  • Under 100 characters for best display

  • Encourage continued use of the multipass

Testing Multipass Messages

To preview your custom message:

  1. Save your custom message

  2. Issue yourself a test multipass card

  3. Install the card on your device

  4. Process a test transaction:

    • Add a visit via scanner app or dashboard

    • Check notification on your device

  5. Test removal too:

    • Remove a visit to see notification

    • Verify message works in both scenarios

  6. Evaluate:

    • Does message make sense for additions?

    • Does message make sense for removals?

    • Is the # placeholder replaced correctly?

    • Does emoji display properly?


Best Practices for Custom Transactional Messages

Keep It Clear and Concise

Transactional messages should:

  • Confirm the action clearly

  • Show the result (stamps earned, visits remaining)

  • Be easily understood at a glance

  • Focus on the transaction, not marketing

Effective:

  • "# stamp earned! 2 more until your free coffee! ☕" ✅

Too complex:

  • "Congratulations on completing another successful transaction at our establishment where we value your loyalty..." ❌

Match Your Brand Voice

Casual/friendly brands:

  • "Yay! # stamp earned! You rock! 🎉"

  • "Awesome! # visit logged—you're the best! ☕"

Professional brands:

  • "# stamp earned. Thank you for your continued loyalty ⭐"

  • "Visit confirmed. # remaining on your multipass 🎁"

Fun/playful brands:

  • "Woo-hoo! # stamp! You're stamp-tastic! 🎉"

  • "# visit down! Keep the good times rolling! ☕"

Stay consistent:

  • Match tone of other customer communications

  • Align with brand personality

  • Keep consistent across all transactional messages

Use the # Placeholder Correctly

Grammatically correct placement:

Good:

  • "You earned # stamp!" (singular/plural handled by system)

  • "# visits remaining on your card"

  • "Great! # stamp added to your collection"

Awkward:

  • "You earned stamp #" (number at end is confusing)

  • "#—that's how many visits you have!" (unclear)

The system handles singular/plural:

  • "# stamp" becomes "1 stamp" or "2 stamps" automatically

  • Don't write "stamp(s)" - system adjusts

  • Trust the system to format correctly

Encourage Continued Engagement

Motivate return visits:

  • "# stamps earned! Keep collecting for your reward! 🎯"

  • "# visits left—see you again soon! ☕"

  • "You're # stamps closer to free coffee! 🎉"

Create momentum:

  • "Halfway there! # more stamps to go! 🎯"

  • "You're on a roll! # visits remaining! ⭐"

  • "Great progress! # stamps toward your reward! 🎉"

Test Thoroughly

Always test before launching:

  • Test on your own device first

  • Check both iOS and Android display

  • Verify message length (not truncated)

  • Confirm # placeholder works correctly

  • Test edge cases (1 stamp vs. 10 stamps)

  • Ensure emoji displays correctly

Common issues to check:

  • Message too long and cuts off

  • # placeholder removed accidentally

  • Grammatical awkwardness with numbers

  • Emoji doesn't display on certain devices

  • Tone doesn't match brand


Troubleshooting

"I can't find the transactional push field in my card settings"

Possible causes:

Wrong card type:

  • Only stamp cards and multipass cards have editable fields

  • Other card types (cashback, gift, discount, etc.) don't have this option

  • Verify you're editing a stamp or multipass card

Wrong section:

  • Must be in Information section of card settings

  • Not in Design, Settings, or other sections

  • Scroll through Information section carefully

Old card version:

  • Card may have been created before this feature was available

  • Try creating a new card to access the feature

  • Contact support if issue persists

"My custom message isn't appearing in notifications"

Check these factors:

Message not saved:

  • Ensure you clicked Save after entering message

  • Return to settings to verify message is still there

  • Re-save if necessary

Using test/preview card:

  • Card preview doesn't trigger real notifications

  • Must use actual issued card with real transactions

  • Issue card to yourself and test with real stamp/visit

System caching:

  • Changes may take a few minutes to propagate

  • Wait 5-10 minutes after saving

  • Process new transaction to trigger updated message

Card not reinstalled:

  • If customer had card before your edit, they may need to reinstall

  • Updates should push automatically but reinstall guarantees latest version

"The # placeholder isn't being replaced with numbers"

Most common cause: Placeholder removed or modified

Check:

  1. Return to card settings

  2. Verify # symbol is present in message

  3. # must be exactly as typed (no spaces, no modifications)

  4. Re-add if missing

  5. Save and test again

If # is present but still not working:

  • Try removing and re-typing the #

  • Ensure no hidden characters around it

  • Copy a working example and modify from there

  • Contact support if problem persists

"Message displays incorrectly on customer devices"

Message truncated:

  • Message is too long (over 100-120 characters)

  • Shorten message and test again

  • Prioritise most important information first

Emoji doesn't display:

  • Some older devices don't support all emojis

  • Try a different, more common emoji

  • Or remove emoji entirely

Grammar issues with numbers:

  • System handles singular/plural automatically

  • Ensure your phrasing works with any number

  • Test with 1, 2, and 10 to verify grammar


Limitations and Considerations

What You Cannot Edit

For all card types:

  • Cannot edit most system-generated transactional notifications

  • Cannot change transaction logic or triggers

  • Cannot customize notification timing (always immediate)

  • Cannot prevent transactional notifications from sending

For stamp and multipass cards:

  • Can only edit specific notifications (stamp earned, reward earned, balance change)

  • Cannot edit other transactional notifications

  • Cannot remove the # placeholder

  • Cannot change when notifications trigger (only message content)

Character Limits

Optimal length:

  • 60-100 characters ideal

  • Up to 120 characters effective

  • Beyond 120 characters risks truncation

What happens if too long:

  • Message cuts off with "..." on lock screen

  • Beginning of message shows, end is hidden

  • Customer must open notification to read full message (less ideal)

Best practice:

  • Front-load most important information

  • Keep concise and scannable

  • Test on actual devices to see real display

System-Generated Accuracy

Why most notifications cannot be edited:

  • Ensures accuracy of financial information

  • Maintains consistency across all customers

  • Prevents errors in critical communications

  • Complies with legal and regulatory requirements

You can still:

  • Send manual push notifications for marketing

  • Use campaigns for promotions and engagement

  • Customize your overall brand messaging

  • Personalize interactions through other channels


FAQ

Q: Can I disable transactional push notifications entirely? A: No. Transactional notifications are built into the loyalty card system to confirm customer actions. They cannot be disabled. They are critical for customer trust and programme transparency.

Q: Will customers receive both transactional AND my manual push notifications? A: Yes. Transactional notifications are separate from manual push campaigns. Customers receive transactional confirmations automatically, plus any manual messages you send. Consider total notification frequency to avoid overwhelming customers.

Q: Can I customize transactional notifications for different customer segments? A: No. Custom transactional messages apply to all customers with that card type. Everyone receives the same transactional message. For segment-specific messaging, use manual push campaigns.

Q: What if I want to test my custom message without affecting real customers? A: Issue a card to yourself, install it on your device, and process test transactions. Your test notifications only go to you, not to customers.

Q: Can I add customer names to transactional notifications? A: No. Custom transactional messages don't support merge fields or personalisation beyond the # placeholder. For personalised messages, use individual customer messaging from profiles.

Q: Will my custom message appear in the customer's card Latest Updates section? A: Yes. Transactional notifications appear both as push notifications on the device and in the Latest Updates section of the customer's loyalty card.

Q: What happens if I delete the # placeholder by accident? A: The message will still send but won't include the stamp/visit count. Always include # to show customers the specific transaction result. Re-add it and save to fix.

Q: Can I use multiple # placeholders in one message? A: Use only one # placeholder per message. Multiple instances may cause display issues or confusion.

Q: Do custom transactional messages work on both iOS and Android? A: Yes. Custom messages appear on both platforms. Test on both if possible to ensure consistent display and emoji support.

Q: If I change the message, will it apply to customers who already have cards installed? A: Yes. The next time they earn a stamp or visit, they'll receive the updated message. Previous notifications remain unchanged, but new transactions use the new message.


Related Articles

  • Push Notifications - How Automated Messages Work - Setting up automated campaigns

  • Creating Stamp Cards - Complete stamp card setup guide

  • Creating Multipass Cards - Complete multipass card setup guide

  • Push Notification Delivery Time - Understanding when notifications arrive

  • Troubleshooting Push Notification Delivery Issues - When customers don't receive notifications


Need help customising transactional push notifications? Contact support for assistance with message configuration or troubleshooting notification display issues.

Did this answer your question?