Certifyd Blog

Inside Spitfire Audio’s Shift to Scalable Royalty Payments Powered by Tipalti

Spitfire Audio moved from manual, spreadsheet-driven royalty payouts to automated mass payments with Tipalti, cutting processing time from weeks to minutes. The case highlights a larger challenge:scalable settlement.

Certifyd

Inside Spitfire Audio’s Shift to Scalable Royalty Payments Powered by Tipalti

Royalty payments can look simple from the outside.

A product sells, revenue comes in, and the people who contributed get paid.

Behind the scenes, creator businesses can be managing hundreds or thousands of payment relationships, different royalty arrangements, payment details, reporting periods and administrative requirements.

For Spitfire Audio, that complexity had become a significant operational burden.

The UK company, known for producing virtual instrument and sample libraries used by composers and music creators, had been processing royalty payments through manual workflows built around spreadsheets.

According to a recent Digital Music News case study, processing those payments could take weeks.

Spitfire eventually moved its royalty disbursement operation to Tipalti Mass Payments, reducing processing time from weeks to minutes.

The change is a useful example of something that often receives less attention than royalty rates themselves:

The infrastructure used to calculate, administer and deliver creator payments matters.

Spreadsheets Work Until They Don't

Many creator businesses begin with relatively simple relationships.

A few collaborators. A handful of releases. A manageable number of transactions.

At that scale, spreadsheets can work.

Someone records what was earned, calculates what each participant is owed, verifies payment information and sends the money.

But growth changes the equation.

More products create more transactions. More collaborators create more obligations. International participants introduce different payment requirements. More reporting periods create more administrative work.

Eventually, the challenge isn't simply having enough money to pay royalties.

It's reliably knowing who is owed what, why they are owed it and whether the payment was completed.

That's an infrastructure problem.

Automation Removes Administrative Friction

Spitfire's move to Tipalti demonstrates the immediate benefit of automating the payment layer.

Work that previously consumed weeks of finance-team effort can be processed much more quickly when payment administration is handled by infrastructure designed for scale.

That reduces repetitive manual work and allows staff to spend less time moving information between spreadsheets and payment systems.

For a growing creator business, that matters.

But there is another problem sitting upstream from the payment processor.

Before money can move, someone has to determine the obligation.

Who participated in the work?

What percentage belongs to them?

What revenue does the agreement apply to?

Has everyone accepted the arrangement?

Have permissions changed?

Has the payment already been made?

Payment automation solves an important part of the problem.

Creator economics begins earlier.

Every Royalty Starts With a Relationship

Every royalty payment represents a relationship.

A composer may contribute to a sample library.

A producer may own a percentage of a recording.

A collaborator may participate in revenue from a derivative work.

A rights holder may retain an upstream share.

The payment at the end is simply the financial expression of those relationships.

That means scalable royalty infrastructure needs two things:

a reliable record of the relationship and a reliable way to settle it.

The music industry has traditionally separated those functions across contracts, royalty systems, spreadsheets, rights databases and payment processors.

That fragmentation is one reason royalty administration becomes increasingly complicated as businesses grow.

Where Certifyd Approaches the Problem Differently

Certifyd is not involved in Spitfire Audio's Tipalti implementation.

But the case illustrates a problem closely related to the infrastructure Certifyd is being built around.

Certifyd starts further upstream.

Creators and collaborators can establish participation in a work, define splits and preserve those relationships alongside the work itself. Permissions and derivative relationships can also become part of that record.

Conceptually, the chain becomes:

Work → Participants → Rights → Splits → Commerce → Settlement

Instead of reconstructing the economic relationship when it's time to pay somebody, the goal is for that relationship to already exist.

That is an important distinction.

From Payment Processing to Network Settlement

Tipalti demonstrates how much efficiency can be gained by automating traditional mass-payment infrastructure.

Certifyd takes a different architectural approach.

When commerce occurs through Certifyd, the relationships surrounding the work can inform how value is divided. Settlement can then occur using Bitcoin and the Lightning Network.

This changes the role Certifyd has to play.

Rather than requiring Certifyd to become the central custodian holding creator funds and processing every payout, a creator, publisher or other network participant can operate payment infrastructure under their own control.

Collaborators can receive their share through compatible Lightning payment endpoints without every participant having to operate identical infrastructure.

Bitcoin provides the settlement asset.

Lightning provides a fast payment rail suitable for smaller internet-native transactions.

Certifyd provides the context connecting the transaction to the work, participants and economic relationships behind it.

The distinction is less about replacing one payment processor with another and more about changing where the payment relationship lives.

Paying Someone Is Different From Knowing Why They're Being Paid

Consider a work with four contributors.

Their splits are established when they collaborate.

Later, one contributor creates a derivative work. The necessary permissions are obtained and the original rights holders retain an agreed participation in the derivative.

The derivative is then purchased.

Several economic relationships can now exist around one transaction.

A conventional payment system can move the money once it receives instructions.

But something still has to know:

Who gets paid?

How much?

Why?

Which work created the obligation?

Which earlier work is connected to it?

What permissions established that relationship?

That's where provenance, permissions and splits intersect with settlement.

Derivative Works Make This More Important

Modern creative work doesn't always stop with the original release.

Music is remixed.

Samples are reused.

Fans create adaptations.

Artists collaborate.

AI tools make entirely new forms of derivative production possible.

Each derivative can introduce another layer of rights and economic participation.

Certifyd's approach is to preserve the relationship between original works and derivatives rather than treating every new work as an isolated object.

Where clearance is required, approval can become part of that relationship.

Where an upstream percentage applies, that economic relationship can remain connected as the derivative moves into commerce.

The payment obligation therefore has provenance.

Settlement Should Be the Last Step

A lot of payment technology begins when money needs to move.

Creator infrastructure can begin when people agree to work together.

Contributors are identified.

Splits are established.

Permissions are granted.

Rights relationships are recorded.

Then commerce happens.

If those relationships are already understood by the infrastructure, settlement becomes the final step in a chain rather than a separate accounting exercise.

That's where Bitcoin and Lightning become particularly interesting.

They're not simply alternative payment methods.

They make it possible to build internet-native settlement into a network where independently operated participants can transact without requiring Certifyd to custody the money moving between them.

Two Different Infrastructure Problems

The Spitfire case therefore exposes two related but different problems.

The first is:

How can a company efficiently pay a large number of creators?

Tipalti addresses that problem by automating and scaling payment operations.

The second is:

Can the relationships between independent creators, rights holders and works determine how value should move when commerce occurs?

That's closer to the problem Certifyd is tackling.

One improves the efficiency of a centralized payout operation.

The other explores whether economic relationships can become part of the creator network itself.

Both matter.

But they're different layers of the stack.

Creator Businesses Are Becoming Infrastructure Businesses

As creator businesses grow, they eventually encounter many of the same infrastructure problems as much larger enterprises.

Identity.

Rights.

Contracts.

Payments.

Reporting.

Compliance.

Commerce.

The difference is that the underlying assets are creative works and the participants may be independent creators spread around the world.

The answer doesn't necessarily have to be one giant company performing every function.

Payment providers can move money.

Rights administrators can provide rights services.

Publishers can provide publishing services.

Creators can operate their own infrastructure.

Network participants can provide services to one another.

What matters is whether the relationships between those participants remain understandable and accountable.

Beyond Faster Royalty Payments

Spitfire Audio solved a concrete operational problem.

A royalty process that previously took weeks could be reduced to minutes through automation.

That's meaningful progress.

But as the creator economy becomes more interconnected, the next challenge isn't only making payments faster.

It's making the economic relationships behind those payments easier to establish and preserve.

Who contributed?

What did they agree to?

What rights exist?

What percentage applies?

What permissions were granted?

What happened to the work afterward?

And when value moves, can those relationships help determine where it should go?

That's where royalty processing begins to become creator infrastructure.

Because ultimately, every royalty payment has to answer the same question:

Why is this person owed this money?

The stronger the connection between the work, the relationship and the settlement, the less of the creator economy has to be reconstructed after the fact.


Certifyd covers developments in music, intellectual property and creator commerce and examines what they mean for the infrastructure connecting creators, rights, relationships and economic participation.