Skip to main content
Who invoices media is set per transaction by its billing party:
  • Interchange-cleared (agent) — Scope3 finance issues the media invoice and it carries the bank remittance details to pay against.
  • Operator-billed — the seller or connected platform bills the account operator directly.
  • Advertiser-billed — the seller or connected platform bills the advertiser directly.
For compatibility, agent projects to legacy Decisioned, while operator and advertiser both project to legacy Routed. That projection is lossy: Routed cannot distinguish the operator from the advertiser. Billing party remains the authority for who invoices; routingType does not say whether optimization happened or which adapter/execution path was used. For a seller-sponsored buyer, the sponsoring seller fixes this authority at provisioning time: prepay selects Interchange-cleared agent, while credit selects seller direct-billed operator. The sponsored account remains the seller’s governed account, and the buyer cannot change that billing choice.
Platform/IU fees are a separate billing stream from media. For organizations whose IU Rate Card and charging feature are enabled, Scope3 issues a separate fee invoice and may collect it through the invitation-only card rail. Existing accepted media-pricing arrangements remain separate and unchanged.
Sponsored prepay uses the existing media invoice/deposit funding and account-capacity mechanisms. It does not make platform-fee card collection an automated media-funding flow. Sponsored credit is seller direct billing, not a Scope3-granted credit line.
Keep your billing info current for Scope3-issued media or platform-fee invoices — who the invoice is addressed to and where it is sent. Manage it in Account settings → Plan & Billing → Payment & invoices or via the API (updates are admin-only):
Authenticate every request with Authorization: Bearer $SCOPE3_API_KEY.

​
What Scope3 needs for its invoices

The minimum for an invoice you can pay — and that your accounts-payable team will accept — is a payer name and a payer address. Beyond that, keep these current so invoices route correctly:

​
Where the remittance details come from

Bank remittance details are printed on each Scope3-issued invoice — you do not need to request them separately, and you should always pay against the details on the invoice you received. Scope3 maintains a bank account per invoicing currency, so the remittance details match the currency you are billed in. A card-collected platform/IU fee instead follows the saved-card flow shown in Plan & Billing.

​
When invoices arrive

Scope3-issued invoices follow your billing cycle and payment terms. A media invoice covers only Interchange-cleared activity; operator- and advertiser-billed media follows that counterparty’s invoice process. Questions about a Scope3 invoice go to the finance contact listed on it.

​
Billing activity

The Invoice activity section at the top of the Invoices tab on the org Billing page shows invoice activity as it happens — status, what it’s for, currency, amount, and due/paid date — via Get invoice activity. It’s empty until your organization has an issued IU fee invoice; media invoice activity and other reserved row kinds do not have producers yet.

​
Task reference

Get billing info

GET /billing/info — current contact, address, tax ID

Update billing info

PUT /billing/info — keep invoicing details current

Get invoice activity

GET /billing/invoice-activity — invoice activity as it happens