Commerce Media
How to Build a Financial Media Network Without Moving Data
Published · Last updated
Next scheduled review:

Keep the ledger, consent store, audience engine and measurement inside the bank's perimeter; export only segment IDs, offer placements and aggregated reports. Start with card-linked offers, which transfer no data, add onsite media when the app has a shopping surface, and add offsite only through an owner-controlled bidder and a clean room. Every live bank network already works this way.
Key facts
- The law sets the boundary, not the vendor. Regulation P lets a bank share nonpublic personal information with a non-affiliated third party only after notice and a reasonable opportunity to opt out, with a 30-day window by mail or after electronic acknowledgement (12 CFR 1016.10); the service-provider and joint-marketing exception requires a contract that limits the third party's use of the data (12 CFR 1016.13).
- Card numbers stay out of the ad stack. PCI DSS v4.0.1's future-dated requirements became mandatory on 31 March 2025 (usd AG, 2025); every live network targets on merchant, category, spend and recency, never on the primary account number.
- The biggest bank network exports nothing. Chase Media Solutions runs cash-back offers in Chase's own channels only, charges when a customer views and purchases, and reports 84 million customers and $11.2 billion of merchant spend driven in 2025 (chase.com, accessed 17 October 2026).
- Banks are already restricting platform access. Cardlytics stopped reporting monthly active users on 1 January 2025 because newer bank partners do not provide equivalent user data, and Bank of America campaigns concluded in January 2026 (Cardlytics 10-K, FY2025; Cardlytics, 4 March 2026).
- In the EU, marketing use of payment data needs its own consent. The EDPB's guidelines on PSD2 and GDPR distinguish PSD2's contractual consent from GDPR consent for further processing (EDPB Guidelines 06/2020, final version, December 15, 2020).
- The category is growing fast enough to justify the build. US financial media network ad spend is forecast to rise from $680 million in 2025 to $3.15 billion in 2028 (eMarketer, January 2026).
Definition
Owned financial media network: a bank's or payments company's advertising business in which transaction records, consent state, audience construction and purchase matching all run on infrastructure the bank controls, and only segment identifiers, offer placements and aggregated reports leave that boundary.
This is the pattern described for the live networks in Financial media networks explained and listed in the commerce media networks directory. The alternative, giving a platform the transaction feed, is the model banks are leaving.
The three boundaries
A bank media network has three boundaries that an auditor will test. Drawing them first makes every later decision easier.
Boundary 1: the cardholder data environment. The primary account number, expiry and authentication data live here under PCI DSS. Nothing in the media stack should touch them. Transactions reach the media stack as tokenized events with merchant, category, amount, date and a customer token. If the media stack can reverse the token, it is in PCI scope.
Boundary 2: the bank's data perimeter. Nonpublic personal information, in GLBA terms, includes any information a consumer provides to get a financial product and any information from a transaction (12 CFR 1016.10). Audience building, offer matching and purchase measurement happen inside this perimeter. The question for every component is whether it needs records or only counts.
Boundary 3: the advertiser interface. Advertisers and agencies see audience sizes, offer placements, campaign reports and, where overlap analysis is wanted, a clean room. They never see records. United states that "advertisers cannot access the personally identifiable information" of its customers and that segments are "aggregated and anonymized" (United, 7 June 2024); Marriott calls its platform "consent-based, with easy opt-out options" (Hospitality Net, 12 June 2025). A bank should be able to make the same two statements on day one.
Reference architecture
Diagram by AdSovereign, CC BY 4.0.
The zones map to components a bank already has (core, consent, CRM) and components it must add (audience engine, offer engine, onsite decisioning, bidder, clean room, measurement). What differs from a retail stack is the strictness of the B–E boundary and the absence of a shared pixel or customer file. For how retailers do the same with loyalty data, see Shopper data monetization; for the clean room options, see Clean room architectures compared.
Launch in eight steps
- Map the legal bases. For US customers: Regulation P notice and opt-out status per customer, affiliate versus non-affiliate sharing, the §1016.13 exception and the contracts it requires, FTC Safeguards Rule controls for any processor. For EU and UK customers: GDPR lawful basis for marketing profiling (consent in practice), PSD2 Article 94 contractual consent for the payment service itself, ePrivacy and PECR for messaging. Output: a data-use register that says, per data element and per use, which basis applies. The rules in depth are in GLBA and advertising with bank data.
- Classify the data. Three tiers: PCI data (never in the media stack), nonpublic personal information (inside the perimeter only), derived attributes (category spend bands, recency, merchant flags) that may feed segments. Decide which categories are excluded entirely: health, pharmacy, gambling, religious and political merchants, and any category a state law treats as sensitive. Pharmacy networks already exclude prescription data for this reason; see Ad tech compliance: PCI, HIPAA, SOC 2.
- Build the consent store before the audience engine. One record per customer with: Reg P opt-out state and date, marketing opt-in for third-party offers, offsite advertising opt-in or opt-out, channel preferences, and the version of the notice shown. Revolut shows ads only in a dedicated section behind a third-party marketing opt-in (The Media Leader, 2023); that is the simplest pattern to audit.
- Design segments with minimum sizes. Every segment has a floor (commonly 1,000 or more customers) below which it cannot be sold or reported, and a definition that uses derived attributes only. Keep a segment registry with owner, definition, floor, creation date and the consent flags it requires. This registry is what the regulator asks for.
- Start with card-linked offers. Offers need a merchant sales motion, an eligibility engine and settlement, but no third-party data transfer: the merchant funds a cash-back amount, the bank matches the purchase in its own ledger and credits the customer. Chase charges only when a customer views and purchases (chase.com, accessed 17 October 2026); Mastercard's network uses the same unit and distributes through issuers such as Citi (Marketing Dive, 1 October 2025). Decide early whether to rent the merchant network (Mastercard, Kard, Cardlytics) while owning the decisioning and the data.
- Add onsite media when there is a surface. Sponsored search and display earn only where customers browse. Klarna's $180 million of 2024 ad revenue came from a shopping surface inside its app, sold through a self-serve manager (Payments Dive, 19 March 2025). A bank without a marketplace or offers hub should not expect onsite revenue from a balance screen.
- Add offsite only through owned bidding and a clean room. Offsite means sending a segment ID, never a transaction attribute, in bid requests from a bidder the bank controls, and measuring through a clean room where brand and bank each keep their records. PayPal runs offsite on its own transaction graph of more than 430 million accounts (PayPal, 17 September 2025) and is the only payments company doing so; most banks will treat offsite as phase three. For EU banks the bidder and clean room must also meet the residency and sovereignty tests in EU sovereign ad tech.
- Measure with holdouts from day one. Closed-loop attribution is automatic for offers (the purchase is the billing event), so the question buyers will ask is incrementality. Build randomised holdout groups into the offer engine, report lift with confidence intervals, and align definitions with the IAB/MRC retail media guidelines of January 2024 even though they were written for retailers (IAB, January 2024). Chase sells incremental-lift reports as a product for this reason.
Partner, white-label or own: what each means for the data
4 of 4 rows
Download JSONTable by AdSovereign, CC BY 4.0.
Platform inside your app (revenue share) | Platform receives a transaction feed or runs inside the bank | Platform | Platform in bank channels | Platform on the feed | Reg P §1016.13 service-provider contract with use limits; data-return and deletion on exit | Cardlytics in Bank of America and Wells Fargo; Kard for fintechs |
Card network distribution | Bank keeps records; network matches on its own permissioned data | Network and bank | Bank and network channels | Network attribution | Participation agreement; consent language aligned | Mastercard Commerce Media with Citi; Amex Offers |
White-label stack, bank-hosted | Bank | Bank, on vendor software | Bank | Bank | Software license; vendor has no data access or only support access with logging | Not publicly disclosed by any bank |
Owned stack (built or acquired) | Bank | Bank | Bank | Bank | Internal; processors only under §1016.13 | Chase (Figg, 2022 → Chase Media Solutions, 2024); Citi (Kard, 2026, pending) |
The direction of travel is down the table. Chase acquired Figg in 2022 and launched its own network in 2024 (Business Wire, 3 April 2024); Citi agreed to acquire Kard on 13 August 2026 (Citigroup, 13 August 2026); Cardlytics' disclosures show the platform model losing data access and its largest campaigns. The economics of each option, with editable assumptions, are in the commerce media business case template.
The 24-item launch checklist
24 of 24 rows
Download JSONTable by AdSovereign, CC BY 4.0.
1 | Data-use register (element × use × legal basis × jurisdiction) | Legal, Data | Register | Signed register, review log |
2 | Reg P notice updated to describe offers and advertising uses | Legal | Privacy notice v.n | Notice version history, delivery records |
3 | Opt-out mechanism and 30-day window implemented | Digital | Opt-out flow | Test records, opt-out counts |
4 | §1016.13 contracts for every processor touching NPI | Procurement | Contracts | Executed contracts with use-limit clauses |
5 | EU/UK: GDPR consent for marketing profiling, separate from PSD2 | Legal, DPO | Consent text and records | Consent logs, DPIA |
6 | DPIA or equivalent risk assessment | DPO | DPIA | Signed DPIA |
7 | PCI scope statement: media stack outside CDE | Security | Scope diagram | QSA sign-off |
8 | Tokenization of customer and card identifiers before the media stack | Engineering | Token service | Token map access logs |
9 | Excluded merchant categories list | Compliance | Exclusion list | Change log |
10 | Segment registry with floors and definitions | Data | Registry | Registry exports per quarter |
11 | Consent store schema with versioning | Engineering | Schema | Schema and migration history |
12 | Offer engine eligibility rules referencing consent flags | Engineering | Rules | Unit tests, rule change log |
13 | Onsite decisioning logs (what was shown, to which token, why) | Engineering | Logs | Retention policy, sample audit |
14 | Offsite bid request template with no transaction attributes | Engineering | Template | Schema review, sample requests |
15 | Clean room with aggregation thresholds and query logging | Data | Clean room config | Threshold settings, query logs |
16 | Holdout design and lift methodology document | Analytics | Methodology | Published methodology |
17 | Reporting API returns aggregates only | Engineering | API spec | Schema review |
18 | Access control: who can query records vs aggregates | Security | IAM policy | Access reviews |
19 | Vendor support access: logged, time-boxed, no data export | Security | Policy | Session logs |
20 | Customer-facing explanation of how ads use data | Marketing, Legal | Help page | Published page |
21 | Complaint and deletion handling tied to consent store | Operations | Runbook | Ticket records |
22 | Incident response covering the media stack | Security | Playbook | Tabletop record |
23 | Quarterly review of segments, exclusions and contracts | Compliance | Calendar | Minutes |
24 | Exit plan: data return and deletion for every processor | Procurement | Exit clauses | Contract text |
What the regulator will actually look at
Published enforcement in this area is thin, so the practical test is the one the bank's own examiners and auditors apply. Expect questions on four things: whether the Reg P notice describes the advertising use and whether opt-outs are honored in the offer engine; whether any processor receives nonpublic personal information without a §1016.13 contract; whether card data is in the media stack's scope; and whether the bank can show, for a given customer, what was displayed and on what basis. The architecture above is designed so each question has a log behind it. For the finance-sector precedent on the compliance side of a programmatic deployment, see Case: finance ad tech compliance.
FAQ
Do we need customer consent to show card-linked offers? In the US, offers shown in the bank's own channels on the bank's own data generally do not require sharing nonpublic personal information with a non-affiliated third party, so the Reg P opt-out is not triggered by the display itself; it is triggered if a processor or partner receives the data outside the §1016.13 exception (12 CFR 1016.10). In the EU, profiling payment data for marketing needs a GDPR basis separate from PSD2 (EDPB Guidelines 06/2020). Most live networks add an explicit marketing opt-in anyway.
Can we use a third-party platform without giving it our transaction feed? Yes, if the platform runs inside the bank's perimeter or receives only segment IDs. Cardlytics' 2025 10-K shows that newer bank partners already withhold user-level data, which is why it stopped reporting monthly active users (Cardlytics 10-K, FY2025). Put the data-access terms in the contract before the integration.
Is the card number ever used for targeting? No. Every live network targets on merchant, category, spend band and recency, and the media stack sits outside the PCI DSS cardholder data environment. PCI DSS v4.0.1's future-dated requirements have been mandatory since 31 March 2025 (usd AG, 2025).
Can we run offsite ads on bank data? Only through a bidder the bank controls, sending pseudonymous segment IDs with no transaction attributes, and measuring through a clean room. PayPal is the only payments company doing this at scale, in the US since 29 April 2025 and in Germany and the UK since 17 September 2025 (PayPal, 17 September 2025). Chase has chosen not to.
How long does a launch take? Chase launched Chase Media Solutions in April 2024, about two years after acquiring Figg in 2022 (Business Wire, 3 April 2024). A bank renting the merchant network and owning the decisioning can run a first offers campaign faster; the consent store and data-use register are the critical path, not the ad tech.
Continue reading
Use the commerce media guide to compare the related operating models, definitions and evidence before making this decision.
How this works on owned infrastructure
The architecture above has one requirement that most rented platforms cannot meet: the audience engine, offer decisioning, bidder and measurement run inside the bank's perimeter, and partners touch only a clean room and an aggregates API. AdSovereign is an enterprise, on-premise RTB stack (DSP, SSP, exchange, DMP and clean room) built for that deployment, including bank-hosted installation, logged support access with no data export, and bid request templates that carry segment IDs only. The architecture and security pages describe the deployment model; use cases lists the configurations we recommend and the ones we do not; the pilot page describes a 60-day evaluation. This page stays neutral; the product is mentioned only here.
Sources
- eCFR, 12 CFR 1016.10, Regulation P limits on disclosure of nonpublic personal information. https://www.ecfr.gov/current/title-12/chapter-X/part-1016/subpart-B/section-1016.10
- eCFR, 12 CFR 1016.13, exception to opt-out requirements for service providers and joint marketing. https://www.ecfr.gov/current/title-12/chapter-X/part-1016/subpart-C/section-1016.13
- usd AG, "PCI DSS v4.0.1: Are You Ready for the Future-dated Requirements?" (2025). https://www.usd.de/en/pci-dss-future-dated-requirements/
- EDPB, Guidelines 06/2020 on the interplay of PSD2 and GDPR (final version, December 15, 2020). https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_202006_psd2_afterpublicconsultation_en.pdf
- Chase Media Solutions site (accessed 17 October 2026). https://www.chase.com/mediasolutions/home
- Business Wire, "Chase launches Chase Media Solutions" (3 April 2024). https://www.businesswire.com/news/home/20240403664648/en/
- Cardlytics, Form 10-K FY2025. https://www.sec.gov/Archives/edgar/data/1666071/000166607126000010/cdlx-20251231.htm
- Cardlytics, Q4 and FY2025 results (4 March 2026). https://www.businesswire.com/news/home/20260304946746/en/Cardlytics-Announces-Fourth-Quarter-and-Full-Year-2025-Financial-Results
- Marketing Dive, Mastercard Commerce Media (1 October 2025). https://www.marketingdive.com/news/mastercard-bigger-grab-commerce-media-dollars-new-network/761568/
- Citigroup, Kard acquisition (13 August 2026). https://www.citigroup.com/global/news/press-release/2026/citi-expands-customer-engagement-commerce-media-capabilities-kard-addition
- PayPal Newsroom, Offsite Ads in Germany and the UK (17 September 2025). https://newsroom.paypal-corp.com/2025-09-17-PayPal-Expands-Offsite-Ads-to-Germany-and-the-UK
- Payments Dive, Klarna F-1 advertising revenue (19 March 2025). https://www.paymentsdive.com/news/klarna-buy-now-pay-later-bnpl-merchant-advertising-revenue/742883/
- United Airlines, Kinective Media launch (7 June 2024). https://united.mediaroom.com/2024-06-07-United-Launches-Airline-Industrys-First-Media-Network
- Hospitality Net, Marriott Media launch (12 June 2025). https://www.hospitalitynet.org/news/4127669.html
- The Media Leader, Revolut ad offering (2023). https://uk.themedialeader.com/fintech-challenger-revolut-ready-to-experiment-with-agencies-on-ad-offering/
- IAB, final IAB/MRC Retail Media Measurement Guidelines (January 2024). https://www.iab.com/guidelines/final-iab-mrc-retail-media-measurement-guidelines-available-for-download/
- eMarketer, "The State of Financial Media Networks 2026" (January 2026). https://www.emarketer.com/content/state-of-financial-media-networks-2026