Direct Debit Confirmation Email
- David Haskell (Unlicensed)
Summary / TL:DR: This article will introduce you to Direct Debit Confirmation Emails for a new subscription or Access service purchase in Blueshift.
3 min read
Table of contents
Capability
Send an email through Blueshift to confirm a customer's Direct Debit agreement for a new subscription or Access service purchase. This confirmation includes the amount, date, and schedule for all recurring charges.
Description
When the payment method for a subscription or Access (AMB) agreement purchase is Direct Debit, the Advantage workflow will capture such payment method and generate an event to inform Blueshift about the new payment agreement. This event then triggers a campaign in Blueshift.
Blueshift Event Name
new_direct_debit_agreement
Event Payload Parameters
Parameter | Description |
|---|---|
event | Name of triggering event |
Email of billTo customer | |
owning_org | Code for the legal entity associated with this access service |
module | Custom description thats shows if the transaction is an Access service (=AMB) or Subscription (=CIR) |
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 |
customer_department | Department for Business Address of billTo customer |
customer_company | Company Name for Business Address of billTo customer |
street1 | Street address, line 1 of billTo customer address |
street2 | Street address, line 2 of billTo customer address |
street3 | Street address, line 3 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 |
item_number | Access Service item number, if transaction involves an Access purchase |
item_description | Access Service item description, if transaction involves an Access purchase |
publication_code | Publication code, if transaction involves a subscription purchase |
publication_title | Publication title, if transaction involves a subscription purchase |
customer_account_number | The billTo customer's bank account number |
collecting_bank_id | The bank ID for the billTo customer's collecting bank |
account_holder_name | Name on the billTo customer's bank account |
first_collection_date | The date the first payment is collected |
first_renewal_date | The date the first renewal (second payment) is collected |
original_amount | Amount of first payment on Access Service or subscription |
renewal_collection_frequency | Interval in which renewals will occur |
renewal_amount | Amount to be charged for renewal of the Access Service or subscription |
direct_debit_reference_number | Unique ID for the direct debit agreement |
Sample Payload
{
"event": "new_direct_debit_agreement",
"email":"email@14west.us",
"owning_org": "983",
"module":"CIR",
"retailer_customer_id": "000068200053-000089668775",
"customer_firstname":"John",
"customer_lastname":"Doe",
"customer_department":"",
"customer_company":"",
"street1":"25 DENVER ROAD",
"street2":"",
"street3":"",
"city":"LIVERPOOL",
"state":"",
"post_code":"L32 4TG",
"country":"UNITED KINGDOM",
"item_number":"",
"item_description":"",
"publication_code":"ZHA",
"publication_title":"The Fleet Street Letter Monthly Alert",
"customer_account_number":"28130689",
"collecting_bank_id":"090132",
"account_holder_name":"John Doe",
"first_collection_date":"2020-11-09",
"first_renewal_date":"2021-10-26",
"original_amount":"49.00",
"renewal_collection_frequency":"Annual",
"renewal_amount":"99.00",
"direct_debit_reference_number":"P424945"
}Setting up a Campaign
Create a triggered campaign using the event ‘new_direct_debit_agreement'.
Set the condition “Skip Global Inclusion Segment Check” to “Yes”.
Select the associated template for your campaign.
If one campaign is used for setting up 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 customer who cancels multiple subscriptions.
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
Please follow the Transition Guidelines shared by the MarTech team during your Migration Planning workshop.
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.
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.
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 Direct Debit Confirmation Emails for a new subscription or Access service purchase in Blueshift.
Still need help?
We know this can be frustrating. To get further help please open a Support ticket.
Related Content
Level up with a Masterclass