Overview

How does Paygrid enable chain-abstracted payments?

Paygrid combines intents, solvers, and payment-specific optimizations across a vertically integrated stack. It's designed to protect the interests of payment operators, payers, and payees from the moment of signing the payment intent all the way to final block inclusion, leaving you to focus on the application layer and the end-user UX you aim to enable.

The easiest way to think about it, is to think of payments as workflows with business logic. A workflow is a sequence of actions that take place to complete a lifecycle of a payment from initiation to completion. It's about the "how" of a payment. Workflows can act like recipes, you can use pre-made ones or make your own.

Example scenario

Let’s examine the overall steps for a simple user flow to send a one-time chain abstracted payment, imagine an online website where a user can buy a product such as e-commerce case:

1. Payer intent:

   • A buyer wants to purchase a product priced at $100.

   • They have USDC on Ethereum Mainnet and prefer to pay with it.

2. Payer UX:

   • The buyer connects their wallet and selects USDC on Ethereum as their payment method.

   • They just need to sign a single message authorizing the payment, no gas fees involved.

3. Operator:

   • The operator creates and signs the intent with the necessary details, including the seller information who prefers to receive USDT on Polygon.

   • The operator submits the CAPI to Paygrid for processing via an API or SDK.

4. Paygrid Gateway Node:

   • Solves the CAPI into intent executions, considering all necessary workflow requirements and pathway.

5. Intent Execution:

   • Paygrid captures payers funds on source.

   • Perform workflow actions as needed.

   • Final amount is transferred to the payee on destination: $100 USDT on Polygon.

For Operators

Integrating and performing the above scenario and other workflows is generally a straightforward process in less than 30 minutes:

• First time setup: Gateway Node registration and configuration.

• Capture signature from payers on payment.

• Use the SDK to send the payment intent to a node.

• Listen for payment progress updates.

You essentially offload all the infrastructure considerations and their costs over to Paygrid, and send payment intents instead.