CASS 15: What now? Practical next steps for payment and e-money firms

Preview text: CASS 15: What now? Practical next steps for payment and e-money firms 96 Is your…

Tuesday, Jun 2, 2026 at 10:08 AM EasternHubSpot

fscomCASS 15: What now? Practical next steps for payment and e-money firms

Image not available

No image available for this email.

Subject: CASS 15: What now? Practical next steps for payment and e-money firms
Preview text: CASS 15: What now? Practical next steps for payment and e-money firms 96 Is your…
From: marketing@fscom.co
Brand: fscom
ESP: HubSpot
Sent: Tue Jun 2, 2026, 10:08 AM ET
Sent to: Colombia (blog.fscom.co)
Size: 39 KB
Images: 4
Links: 4, 1 of them buttons
Subject length: 70 characters

Against fscom's usual

Sent in the 10 AM hour, which holds 10% of its emails; 61% arrive in the 9 AM hour. The subject is 70 characters; its average is 44.

Email headers

What the brand's servers put on this email. Our receiving servers, the address we subscribed with and unsubscribe links are left out.

From: Marketing fscom <[email protected]>
Reply-To: [email protected]
Subject: CASS 15: What now? Practical next steps for payment and e-money firms
Date: Tue, 2 Jun 2026 15:08:54 +0100
Message-ID domain: bf05x.hubspotemail.net
Return-Path domain: bf05x.hubspotemail.net
DKIM signature: d=bf05x.hubspotemail.net s=hs1; d=fscom.co s=hs2-2934033
List-Unsubscribe: Present, one-click
Feedback-ID sender: HubSpot

from 4f2owc.bf05x.hubspotemail.net [108.179.149.250] by our receiving server with ESMTPS

Other sending headers (names only): X-HS-Cid, X-Report-Abuse-To

	Jun 12, 2026 9:02 AM	fscom's Top News Stories of the Week
	Jun 10, 2026 6:57 AM	Webinar reminder: Practical next steps under CASS 15
	Jun 5, 2026 9:02 AM	fscom's Top News Stories of the Week
	Jun 2, 2026 10:08 AM	CASS 15: What now? Practical next steps for payment and e-money firms (this email)
	May 29, 2026 9:01 AM	fscom's Top News Stories of the Week
	May 22, 2026 9:02 AM	fscom's Top News Stories of the Week
	May 18, 2026 11:01 AM	A development at fscom we wanted to share directly with you