Fair escrow for both sides

Trust the rules, not the other person.

PayNode protects the client when work is not delivered and protects the builder when delivered work is ignored.

Clients lock the agreed payment in a smart contract. Builders submit their work through the platform. Clear deadlines, review periods, refunds, revisions, and settlement rules keep either side from holding complete control.

Step 01Create Project
Step 02Lock Payment
Step 03Deliver Work
Step 047-Day Review
Step 05Approve or Claim

What PayNode solves

Online work creates risk for both sides.

A builder may finish the work and never get paid. A client may fund a project and receive nothing. PayNode replaces open-ended trust with clear rules that both sides can understand before the project begins.

For Clients

No delivery means a refund path.

If the project deadline passes and the builder has not submitted any work, the client becomes eligible to recover the locked payment.

For Builders

Delivered work cannot be ignored forever.

After delivery, the client has 7 days to respond. If no action is taken, the builder becomes eligible to claim the escrowed payment.

Balanced by design

PayNode does not give complete control to either side.

The builder cannot receive payment without delivering the work, and the client cannot keep a completed delivery unpaid forever.

Before delivery

The project deadline protects the client.

The builder must submit work before the agreed project deadline.

After delivery

The 7-day review period protects the builder.

The client must approve, request a revision, or raise a dispute within 7 days.

During revision

The payment stays locked.

Revised work starts a fresh 7-day review period.

The core of PayNode

How the escrow handles real project scenarios

These four rules are the foundation of the contract and explain how PayNode protects both participants.

Scenario 01Protects the Client

The project deadline passes with no delivery

If the builder does not submit any work before the project deadline, the client becomes eligible to refund the locked payment from the smart contract.

Result: the client can recover the escrowed funds.

Scenario 02Protects the Builder

The client does not respond after delivery

When the builder submits the work, a separate 7-day review period begins. During those 7 days, the client can approve, request a revision, or raise a dispute.

Result: if the client takes no action before the review period ends, the builder becomes eligible to claim the escrowed USDC directly from the smart contract.

Scenario 03Protects Quality

The client requests a revision

A revision request closes the current review period. The payment remains securely locked while the builder works on the requested changes.

Result: no payment is released while the project is in revision.

Scenario 04Protects Both Sides

The builder submits revised work

After the builder submits the updated delivery, a new 7-day review period begins for the revised work.

Result: the client receives a fresh review window, while the builder is protected from an endless unpaid review cycle.

Two different clocks

Project deadline and review period are not the same.

The project deadline applies before delivery. The 7-day review period applies only after the builder submits work.

Project deadline

Before the first delivery

This is the agreed amount of time the builder has to submit the project. It can be 5 days, 10 days, or another duration selected for that project.

No delivery by this deadline → the client can refund.

7-day review period

After each delivery

Once work is submitted, the client receives exactly 7 days to approve it, request a revision, or raise a dispute.

No response within 7 days → the builder can claim.

One link for builders

A PayNode profile is more than a portfolio.

It brings skills, completed projects, client ratings, social links, and wallet-based payments together in one shareable professional identity.

Share one profile on X, Discord, Telegram, LinkedIn, GitHub, or a personal website.

Receive project invitations through the same public link.

Accept USDC tips from people who want to support your work.

Build visible reputation through completed projects and ratings.

PayNode builder profile
A shareable PayNode profile combining skills, social links, project history, ratings, project requests, and USDC tips.

Product walkthrough

A simple project flow

The user-facing process stays simple, while the contract applies the rules in the background.

1

Create the agreement

The client defines the project, budget, project deadline, delivery expectations, and revision limit. The payment is priced in USDC.

Creating a PayNode project
The client defines the project terms, budget, deadline, and revision rules.
2

Lock the payment in escrow

The client funds the smart contract before work begins. The builder can see that the agreed payment is secured.

Funding a PayNode escrow project
The agreed payment is locked before the builder starts working.
3

Submit the work

The builder submits delivery notes and links to the final work. This action begins the 7-day review period.

Submitting work through PayNode
Submitting a delivery starts the client's 7-day review period.
4

Approve, revise, dispute, or wait

The client can approve the work, request a revision, or raise a dispute. If the client does nothing for 7 days, the builder becomes eligible to claim the payment.

PayNode project review and payment
Approval releases payment. No response for 7 days enables the builder's claim path.

Builder reputation

Successful work becomes public credibility.

Every completed project and client rating can strengthen the builder's profile and help future clients make a more confident hiring decision.

A strong profile creates long-term value.

High ratings and successful project history act as visible proof of reliability. Builders can keep sharing the same link as their reputation grows.

More trust before a new project
A visible history of completed work
One link for projects and tips
Reputation that grows over time
PayNode builder rating
Client ratings and completed projects strengthen the builder's public reputation.

Security rules

Simple rules users can understand before they connect a wallet.

The most important protections are visible and predictable. Users do not need to understand contract code to understand their rights.

The builder cannot receive the project payment before submitting work.

The client cannot keep a completed delivery unpaid forever.

The client can refund after the project deadline if no delivery exists.

The payment remains locked while a revision is active.

Every revised delivery starts a new 7-day review period.

Project payments, refunds, settlements, and tips use USDC only.

PayNode will never ask for a seed phrase or private key.

Review every wallet request before signing and use only the official PayNode application.

Built on Arc Network

Programmable rules make the escrow predictable.

PayNode uses Arc Network to turn deadlines, review periods, revisions, refunds, and settlement into transparent smart contract rules instead of private platform decisions.

Questions

Frequently asked questions

The essential rules to understand before starting a project.

What is the difference between the project deadline and the 7-day review period?+

The project deadline is the time the builder has to submit the initial delivery. The 7-day review period starts only after a delivery is submitted and gives the client time to approve, request a revision, or raise a dispute.

What happens if the builder misses the project deadline?+

If no delivery has been submitted before the project deadline, the client becomes eligible to refund the locked payment from the smart contract.

What happens if the client ignores a submitted delivery?+

The client has 7 days to respond. After that review period expires, the builder becomes eligible to claim the escrowed USDC directly from the smart contract.

What happens when a revision is requested?+

The current review period closes and the payment remains locked. When the builder submits the revised work, a new 7-day review period begins.

Can the builder receive payment without delivering work?+

No. The escrow rules require a delivery before the normal approval or review-expiry settlement path can be used.

Can the client keep the payment locked forever after delivery?+

No. The 7-day review period prevents an inactive client from holding the builder's payment indefinitely.

Which payment asset does PayNode support?+

PayNode uses USDC for project escrow, settlement, refunds, and tips. Native network tokens and other ERC-20 tokens are not supported for these payments.

Where can developers find the technical implementation?+

The public GitHub repository contains the contract code, application architecture, implementation details, and development history.

One link. Fair rules. Secure payment.

Build your reputation, receive tips, start protected projects, and get paid through a balanced escrow workflow.