The “Split-Billed” Agency Asset: How to Track Assets Where the Client Pays the Vendor Directly But the Agency Manages

Picture this: it’s a quiet Friday afternoon, and an urgent ping lands in your agency’s Slack channel. A high-value client’s e-commerce store is down, showing a generic “domain expired” page or a connection error.

You scramble into the hosting dashboard or domain registrar, only to find that the renewal failed because the client’s corporate credit card expired days ago. Worse, the vendor’s warning emails went to a billing alias, or to a stakeholder who left the company months ago.

Your agency didn’t touch the payment. But the client is still going to ask why you didn’t catch it.

Welcome to the “split-billed” agency asset. This operational trap appears when a client insists on paying vendors such as GoDaddy, Kinsta, Shopify, or AWS directly on their own card, while still expecting your agency to monitor, manage, and guarantee uptime.

This guide covers how the liability gap works, how vendors actually behave when a payment fails, how to build early warnings that don’t depend on the vendor, and how to handle the client conversation when a card declines.

1. The Liability Gap of Client-Billed Vendors

In a clean arrangement, money and technical control sit on the same side. Either the agency bundles hosting, domains, and licenses into a retainer (agency-billed), or the client owns both the wallet and the keys (fully client-managed).

The split-billed model separates them:

[ Client's Credit Card ] ---> [ Vendor (GoDaddy / Kinsta / Shopify / AWS) ] <--- [ Agency Manages Technical Operations ]
          |                                                                              |
          +----------------------------- THE LIABILITY GAP ------------------------------+
                  (Who gets blamed when the card declines and the site goes down?)

Why clients ask for split billing

Procurement and expense rules. Many mid-market and enterprise finance teams don’t allow third parties to put recurring charges on corporate cards, or require a formal review first.
Ownership anxiety. Plenty of clients have had a bad experience with a former vendor holding their domain or hosting account. Keeping the billing profile in their own name is a way to keep legal and administrative control.
Tax and invoicing alignment. Some clients prefer SaaS and infrastructure invoices to be issued to their own legal entity, which keeps VAT and accounting records clean on their side.

The hidden trap for agencies

Split billing satisfies procurement, but it leaves the agency exposed. When a card expires or gets blocked, the vendor’s billing system retries for a while and then suspends or cancels the service. The agency can’t see or change the payment method, yet gets the phone call.

That limit on agency power is built into how vendors design access. GoDaddy’s delegate access, for example, lets account owners share access without sharing passwords, and delegates can’t view or change secure information like payment methods. The same is true of many agency-style permission tiers elsewhere: you can manage the asset, but you can’t fix the card. godaddy

When the site goes dark, stakeholders rarely blame their own accounts payable team. They ask: “Why didn’t you catch this? You manage our digital presence.”

Without a contractual boundary and a tracking process, your agency absorbs the reputational damage, the emergency troubleshooting hours, and the stress of an outage it had no financial authority to prevent.

2. What Actually Happens When a Client’s Payment Fails

“Vendors suspend quickly” and “vendors give you weeks” are both wrong, because timelines differ a lot by vendor and product. Knowing the real clock for each platform in your stack is the foundation of a good response plan. A few examples:

Domains (ICANN-accredited registrars). The Expired Registration Recovery Policy (ERRP) requires registrars to send at least two renewal notices before a domain expires and gives registrants a 30-day Redemption Grace Period before the name is dropped. The catch is that during the Redemption Grace Period, DNS resolution is disabled, so the site is down even though the domain is technically recoverable. Registrars also layer their own timelines on top: at GoDaddy, for example, expired domains are listed on GoDaddy Auctions 26 days after they expire, though not all domains follow the standard timeline. Expired Registration Recovery Policy +3
Managed WordPress hosting (Kinsta). Kinsta’s documented process retries a failed payment three days, eight days, and fifteen days after the first failure, and if the fourth attempt fails the plans and services are cancelled automatically. During suspension, all traffic and processes stop and visitors can’t load the site. Kinsta’s first failure notice goes to the email address used to log in to MyKinsta. That is the account owner’s login, not necessarily anyone at your agency. Failed Payments +2
E-commerce platform (Shopify). Shopify’s help center says a store doesn’t freeze until the bill’s due date, but once frozen, you can’t access the admin and customers can’t view the store. Recovery needs the store owner: to reactivate, you must pay outstanding charges, and if you reactivate more than 30 days after the last bill was issued, you must also pick a plan and pay for the upcoming subscription cycle. A staff or collaborator account can’t do this for the client. shopifyshopify
Cloud infrastructure (AWS). AWS warns that outdated contact information can lead to unpaid invoices and potential account suspension. Even after a past-due balance is paid, reactivation isn’t always instant: AWS re:Post guidance says it typically takes up to 24 hours for the account to reactivate after payment, and some users report longer waits that require a support case. icompaasrepost

The practical takeaway: the real window between “card declined” and “customer-visible outage” ranges from a couple of weeks to nearly immediate depending on the platform and product. Record the actual clock for each split-billed asset instead of assuming one number.

3. Setting Up “Agency Monitoring vs. Client Payment” Tags

To protect your agency from uncompensated liability, separate operational oversight from financial execution with a formal tagging system in your asset register.

Step 1: Audit your stack and tag every asset

Every domain, SSL certificate, hosting account, and plugin or software license should be recorded in whatever system you already use (Notion, Airtable, Hudu, IT Glue, or even a well-kept spreadsheet) with explicit responsibility tags:

[A-Bill / A-Manage]: Agency-managed and agency-billed. The cost is rolled into the retainer. You carry the most risk, but you also control the renewal.
[C-Bill / C-Manage]: Client-managed and client-billed. Low agency liability, but also hands-off.
[Split: C-Bill / A-Manage]: The danger zone. The client owns the billing profile and card, but the agency handles deployments, updates, DNS, and optimization.

For each split-billed asset, capture at least:

the vendor and plan,
the renewal or billing date,
who owns the account (and the login email on it),
where billing and payment-failure emails are sent,
the vendor’s failed-payment timeline (from the section above),
the client contact who can actually update the payment method.

That last field matters more than any other. When a card declines, the person you need is whoever can change it, and in a split-billed setup that is never you.

Step 2: Add a financial-responsibility clause to your contract

For assets tagged split-billed, your master services agreement (MSA) or statement of work (SOW) should say plainly who is responsible for what. A sample clause:

Client Financial Responsibility Clause: “While [Agency Name] provides technical monitoring and deployment services for [Asset Name], the client retains sole responsibility for maintaining an active, valid payment method with the underlying vendor ([Vendor Name]) and for responding to vendor payment-failure notices. [Agency Name] is not liable for service interruptions, domain lapses, or data loss resulting from failed client payments, expired billing profiles, or delayed client response to payment-failure notifications, provided [Agency Name] has notified the client of the failure in accordance with the escalation procedure in this agreement.”

Two notes. First, have a lawyer review any clause like this against your jurisdiction and your client’s contract terms. Second, a disclaimer protects you in a dispute but does nothing for the relationship in an outage, which is why the notification and escalation language matters as much as the disclaimer.

4. How to Trigger Alerts Before a Client Ignores a Renewal Notice

Relying on vendors to warn clients about failing payments is a weak plan. Notices go to whichever email is on file, and in split-billed accounts that is often an ex-employee, a shared inbox no one reads, or an address that bounces. You need an early-warning system that doesn’t depend on the vendor’s emails reaching the right person.

Put billing notices where two organizations can see them

Where the vendor allows it, add a second recipient for billing and payment-failure mail.

AWS: Datadog’s security guidance notes that all AWS accounts should have the billing, operations, and security alternate contacts configured so alerts reach the right teams. A shared billing alias with one client person and one agency person is a good fit for the billing contact. datadoghq
Other vendors: Check what the platform supports (additional billing contacts, notification recipients, or multiple account admins). Where none exist, ask the client to set up an email forward or a shared distribution list that includes your operations inbox.
Avoid individuals. Use role-based aliases (for example, billing-alerts@clientdomain.com) so a departure doesn’t silently break the notice path.

Add independent expiry monitoring

External monitors read public data (registry expiration dates, the certificate your server presents), so they work regardless of whose card is on file.

Domain expiry monitoring. Several uptime tools include this. UptimeRobot’s domain monitoring sends alerts 30, 14, 7, and 1 day before domain expiration, but it is included only in paid plans. Better Stack also offers domain expiration monitoring, with a setting to alert 14 days before expiry. Expect some noise: users report that some registrars, such as GoDaddy, auto-renew closer to expiry than the alert window, causing false positives. Treat an early alert as a prompt to verify the payment method, not as proof of failure. domain expiration monitoring +3
SSL/TLS certificate monitoring. Many monitors check this as part of regular uptime checks. According to one 2026 roundup, Better Stack builds SSL checks into its uptime monitors, Pingdom embeds SSL checks in HTTPS uptime checks, and Datadog Synthetics offers SSL tests for certificate validity and expiration. dotcom-monitor
Certificate lifetimes are getting shorter. Under CA/Browser Forum Ballot SC-081v3, the maximum validity of publicly trusted TLS certificates drops to 200 days from March 15, 2026, 100 days from March 15, 2027, and 47 days by March 15, 2029. That makes renewal failures more frequent for certificates that aren’t automated, especially paid certificates bought separately on a client’s card. Set shorter alert windows as validity shrinks. encryptionconsulting
Calendar alerts for the vendor’s billing date, not just the expiration date. For split-billed assets, put a reminder 14 days before the next charge to confirm the card on file is still valid. This catches the most common failure, an expired card, before the vendor ever tries to charge it.

+------------------------------------------------------------+
|             Multi-Layered Early Warning System             |
+------------------------------------------------------------+
| 1. Domain expiry monitoring (independent of the registrar) |
| 2. SSL/TLS certificate expiry monitoring                   |
| 3. Shared billing inbox (client + agency visibility)       |
| 4. Calendar check on the card before each billing date     |
+------------------------------------------------------------+

None of these tools can see whether a card on file is valid, and they can’t tell you a payment failed. They only tell you that an expiration date is approaching. The card check in step 4 and the shared billing inbox are what close that gap.

5. Managing Friction When a Client Card Declines

Even with good preparation, cards decline because of fraud flags, bank security blocks, or expiry. When a split-billed asset hits a payment wall, you want a scripted, professional response that fixes the problem without making the client defensive.

Step 1: Triage internally first

When you learn a payment has failed:

Check the status. Is the asset in a retry window, a grace period, or already suspended? Use the failed-payment timeline you recorded for that vendor.
Work out the urgency. A Kinsta account in its first retry cycle is a different situation from a domain already in its Redemption Grace Period, where DNS is off and fees go up.
Identify who can fix it. Find the client person with authority over the payment method, not just the day-to-day project contact.

Step 2: Send a calm, specific heads-up

Frame it as a routine operational notice that needs their billing team’s action, not an accusation. A template:

Subject: Action needed: payment update required for [Asset Name / Domain]

Hi [Client Name],

Our monitoring flagged that the most recent renewal payment for your [hosting / domain / platform] account with [Vendor Name] didn’t go through. This is usually caused by an expired card or a bank security check.

To avoid downtime for [Client Website], could you or your finance team update the payment method in your [Vendor Name] account by [date]? Here’s the direct link to the billing page: [Insert Vendor Billing URL].

Please reply once it’s done and we’ll confirm the renewal processed on our side.

Thanks,

[Your Name]

Step 3: Escalate on a schedule

If the payment method isn’t updated within about 48 hours, or sooner if the vendor’s clock is short:

Go to an executive sponsor. Contact the person who owns the budget, such as the CMO or the finance lead, not just the project manager who can’t touch corporate finance tools. Put the vendor’s deadline in the message.
Consider an “agency bridge” only if you’ve agreed to it in advance. If a critical asset is close to suspension or a domain is near auction, the agency may pay with its own card and bill the client afterward. Be aware of the constraints:
- Many billing portals only let the account owner change or add a payment method, and Shopify reactivation specifically requires the store owner. So a bridge may be impossible without the client’s involvement, or may require them to add a card you control.
- It exposes you to the client’s non-payment, so get the client’s written approval (email is fine) before you spend anything.
- If you charge an administrative fee on top of the vendor cost, state it in the contract up front. Any specific figure should reflect your own rates; there is no industry standard for this fee.
- A prepaid or spend-limited virtual card issued by the client is a cleaner alternative where their finance team allows it.

Step 4: Close the loop afterward

Once the payment goes through, confirm that the service is restored, note the incident in the asset record, and ask the client to put a recurring reminder on their side. Then ask whether the billing notice email needs to change so the next failure reaches the right people sooner.

Summary Checklist for Split-Billed Assets

Audit inventory: Identify every client asset where the client controls billing but the agency manages operations.
Record the vendor’s failed-payment timeline: Document how long each platform gives you (retries, grace periods, suspension, deletion) instead of assuming.
Name the person who can fix the card: Keep a client contact with payment authority in the asset record.
Update contracts: State that the client is responsible for keeping valid payment methods, and define your notification and escalation duties. Have a lawyer review it.
Add independent monitoring: Use third-party tools for domain and SSL expiry, and check the card on file ahead of each billing date.
Share billing notices: Route vendor billing and payment-failure emails to a role-based alias visible to both the client and your operations team.
Keep an escalation script ready: Use a calm heads-up email, a deadline, and an executive escalation path.
Agree on any emergency payment arrangement in advance: Don’t decide it mid-outage.

Originally published at https://instarenewal.com/blog/the-split-billed-agency-asset-how-to-track-assets-where-the-client-pays-the