For developers building on Circle products, post Q&A, best practices & SDK/API insights. Use Tags

Circle Products & Developer Toolings

Crypto payments have always had a fundamental problem. Once a stablecoin transaction confirms, it's done. There's no disputing it. No calling your bank. No chargeback. If a merchant doesn't deliver, if the product is defective, if the payment was made in error - the money is gone. Finality is a feature for settlement, but it's a dealbreaker for commerce.

This is why most real-world businesses still won't accept crypto. Not because of volatility - USDC solved that. Not because of speed - Arc settles in under a second. The reason is that buyers have zero protection after they pay. And merchants face no accountability for failed delivery. Traditional payments solved this decades ago with chargebacks. Crypto never had an answer.

Until now. Circle Research published the Refund Protocol in April 2025 — an open-source smart contract system that brings non-custodial dispute resolution to stablecoin payments. It works on Arc and any EVM chain. It doesn't require a centralized payment processor. And the arbiter - the party that resolves disputes - cannot steal or redirect funds. Their power is limited by the contract itself.

This post breaks down every piece of the protocol: how payments work, how disputes are resolved, the three refund paths, the debt system that handles edge cases, and why this changes the economics of accepting crypto for real-world commerce.

Every interaction in the Refund Protocol involves three roles, each with carefully constrained powers.

 is the party sending money. A customer buying a product, a client paying a freelancer, a business settling an invoice. When the payer calls pay(), they specify three things: the recipient address, the amount, and a refundTo address. That refundTo address is locked into the payment record - it's the only address that can ever receive a refund for this payment. This is critical. It means the arbiter can't redirect funds to themselves or any third party.

 is the party receiving payment. A merchant, a freelancer, a service provider. They can't touch the funds immediately. Every payment enters a lockup period - a configurable window where the funds sit in the smart contract. Once the lockup expires, the recipient calls withdraw() to claim their money. During the lockup, disputes can happen. After it, the funds are theirs.

 is the neutral third party that resolves disputes. Think of them as the on-chain equivalent of a credit card company's dispute department, but with one massive difference: the arbiter can only do two things. They can send funds back to the payer's refundTo address, or they can release funds to the recipient. That's it. They cannot send funds to any other address. They cannot take the money for themselves. The smart contract enforces these constraints.

This three-party model is what makes the protocol non-custodial. No single party has unilateral control over the funds.

A payment in the Refund Protocol follows a simple lifecycle.

 The payer approves the contract to spend their USDC, then calls pay() with the recipient, amount, and refundTo address. Funds move into the contract and a Payment record is created.

The funds sit in escrow during the lockup period. This is the dispute window.

 If no dispute is raised, the recipient calls withdraw() after the lockup expires and receives the funds.

The lockup period is the core mechanism - it gives buyers protection and merchants clarity.

1. Voluntary Refund (Recipient Initiated)

The recipient calls refundByRecipient(). Funds are returned to the payer’s refundTo address. No arbiter needed.

If a dispute occurs, the arbiter can call refundByArbiter(). If the recipient has already withdrawn funds, the arbiter covers the refund and the system records a debt.

The recipient can opt for early withdrawal by signing an EIP-712 message. The arbiter executes it and takes a fee.

If a merchant has already withdrawn funds and a refund is required, the arbiter covers it from their own balance. The protocol records this as debt owed by the merchant.

This ensures buyers are protected even after withdrawal - a critical improvement over traditional crypto payments.

The protocol is implemented as a single Solidity file (RefundProtocol.sol), using OpenZeppelin’s EIP-712.

- Has immutable token and arbiter addresses

Escrowed funds currently earn no yield, which is a known tradeoff.

- Merchants avoid blanket chargeback fees  

- Arbiters become a new on-chain service layer  

It brings the benefits of traditional finance protections without sacrificing crypto’s core advantages.

- Early withdrawal requires EOA wallets  

- Arbiter cannot redirect funds, but trust is still required  

- Lockup period is configurable per recipient  

1. https://circle.com/blog/refund-protocol-non-custodial-dispute-resolution-for-stablecoin-payments  

2. https://github.com/circlefin/refund-protocol  

3. https://github.com/circlefin/arc-escrow  

4. https://docs.arc.network/arc/references/contract-addresses  

5. https://docs.arc.network/arc/references/sample-applications  

Stablecoin payments are fast, cheap, and global. The one thing they’ve been missing is buyer protection. The Refund Protocol adds it - without giving up custody, transparency, or decentralization.

The next time someone says crypto can’t support real commerce because there are no chargebacks -- point them here.

Built on Arc. Protected by the Refund Protocol.

The Refund Protocol: How Circle Brought Chargebacks to Crypto Without Giving Up Custody

Home

Forum

Events

Content

Courses

People

Contributors

Albums

Groups

Chat

Channels

Not being used

Help

Join the global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make the economy work for everyone.

Arc House

Profession

Join a global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make that economy work for everyone. 

Arc House | Build the economic OS for the internet with us

Copyright

Terms of Service

Privacy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via noreply@arc.network if you need support.

Pending Approval

Login to the The Arc Community Hub community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community complete your profile using verifiable and real information.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Arc House.

Thanks for your interest in joining Arc House. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via noreply@arc.network for any questions.

Accounts are unapproved when profile information cannot be verified or when activity patterns indicate spam, inorganic participation, or behavior that undermines trust in the program.

To strengthen your profile for future consideration, sign in with a verified LinkedIn account, use real and current profile information, and participate constructively in other community spaces.

Commercial customers should raise concerns through their support channel.

https://www.arc.network/community-guidelines