Document toolboxDocument toolbox

Blueshift Subscription Credit Card Decline Email

Summary / TL:DR: This article will introduce you to Subscription Credit Card Decline emails in Blueshift.

3 min read


Table of contents


Capability

Send an email to a customer to inform them that the credit card used for their subscription payment was declined.


Description

When a customer's credit card gets declined for a subscription payment, the card and order information are sent to Decisions. The Decisions workflow captures the update and generates an event to inform Blueshift about the action. This event then triggers a campaign in Blueshift.


Blueshift Event Name

subscription_creditcard_decline


Event Payload Parameters

Parameter

Description

Parameter

Description

Parameter

Description

event

Name of triggering event

publication_code

16-digit code that identifies a publication

retailer_customer_id

Concatenation of [Advantage billTo customer number]-[Advantage billTo emailId]

customer_firstname

First name of billTo customer

customer_lastname

Last name of billTo customer

street1

Street address, line 1 of billTo customer address

street2

Street address, line 2 of billTo customer address

city

City of billTo customer address

state

State of billTo customer address

post_code

Postal code of billTo customer address

country

Country of billTo customer address

delivery_code_detail

Postal delivery method

final_expire

The issue date of the last issue the customer will receive, including advance renewals.

email

Email of billTo customer

promotion_code

Promotion code affiliated with the order

cc_order_number

The order number affiliated with the credit card decline

message_code

Code that identifies the type of decline (non-AR or AR decline)

order_balance

The amount remaining due of the original total product cost

order_total

The total amount of the credit card decline

publication_title

Publication title, if transaction involves a subscription purchase

cc_last_digit

Last four digits of the credit card used

card_expiration

Expiration date of the credit card used

card_code

Code that identifies the type of credit card used

billing_key

Promo code starting with "B" that is auto-generated by the ARP310 process (the process that captures declined customers).

currency

Currency type for this order

control_group_date

Date of credit card decline

renewal_flag

Renewal flag associated with the credit card decline

reject_code

Code that identifies the reason for the credit card decline

member_category

If associated with a membership, the member category that the decline is under.

owning_org

Code for the legal entity associated with the product/item


Sample Payload

 

{ "publication_code": "PRL", "retailer_customer_id": "000126242783-004232532112", "customer_firstname": "KEVIN", "customer_lastname": "BLAKE", "street1": "98 S WATER ST", "street2": "", "city": "NEW HAVEN", "state": "CT", "post_code": "65192822", "country": "UNITED STATES", "delivery_code_detail": "ME", "final_expire": "2022-08-01", "email": "email@14west.us", "promotion_code": "P19BW437", "cc_order_number": "SJ671420", "message_code": "NM", "order_balance": "125.49", "order_total": "125.49", "publication_title": "Profits Unlimited", "cc_last_digit": "4463", "card_expiration": "2020-08", "card_code": "VI", "billing_key": "B08219UM", "currency": "US$", "control_group_date": "2020-08-24", "renewal_flag": "", "reject_code": "", "member_category": "", "owning_org": "", "event": "subscription_creditcard_decline" }

Setting up a Campaign

  1. Create an event triggered campaign using the event ‘credit_card_decline’.

  2. Set the condition “Skip Global Inclusion Segment Check” to “Yes”.

  3. Select the associated template for your campaign.

  4. If one campaign is used for setting up a mailing for multiple publications, set the condition “User can be in the campaign journey” to “Multiple times concurrently”.This will allow you to send an email to a individual customer who cancels multiple subscriptions at different times.


Reporting

The event name in the payload will be passed in the mailing activity events. This will be available in the reporting platform for filters.


Things to Consider When Planning your Migration and/or Setup

  1. Please follow the Transition Guidelines shared by the MarTech team during your Migration Planning workshop.

  2. If you have an existing Message Central Auto Delivery (BCL) Cancellation workflow on Advantage, your new Blueshift workflow has already been set up on Advantage and is ready to send events.

  3. If you never had an Auto Delivery Cancellation workflow on Advantage, there is no longer a need to share the new campaign ID with the Advantage team during initial set up. The same event category can be used for multiple campaigns, segments, etc. without Advantage configuration support.

  4. The Auto Delivery Cancellation workflow will account for all owning orgs associated with your Blueshift instance. Please note: additions of new owning orgs must be reported to the MarTech team so it can be added to your Blueshift instance.


Wrap up

You should now have a better understanding of Subscription Credit Card Decline emails in Blueshift.

Still need help?

We know this can be frustrating. To get further help please open a Support ticket.

Click here to open a ticket


Related Content


Level up with a Masterclass

Evolve course title

Get started!

Evolve course title

Get started!


 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.