FAQs

What is Paygrid’s Payment Stack?

Our goal with Paygrid’s payment stack is to provide a secure and flexible solution for different payment models and wallet management capabilities, all while remaining fully compliant and non-custodial.

What is the Embedded Wallets API?

Embedded Wallets API:

• Non-custodial wallets that allow you to take actions on behalf of the user, which can enable 1-click payment flows with minimal web3 jargon and customizable UX.

• Create invisible wallets in the background without user interaction. Eg: Create accounts for users with standard email or social login and use the API to create a wallet.

• Display wallet balances and common actions like deposit and withdraw (crypto and/or fiat), sample UX prototype.

What is the Payments API?

Allows you to easily create and manage any payment flow, across multiple supported networks with a single API/SDK.

Payments API use cases:

• One-time Payments: Process one-time payments across supported networks.

• Recurring Payouts: Schedule recurring payouts from embedded wallets, for example B2B payments. Sample UX prototype.

• Subscription Payments: Allow your users to accept subscriptions and pull funds from non-custodial wallets like MetaMask, for example a SaaS service or E-commerce case. Sample UX prototype.

• All payments have built-in capabilities:

  • Finding the best routes and executing cross-chain settlements.

  • Multi-party payouts and payment splitting, and can combine fiat and crypto for a single payment.

  • Batch processing.

  • Customized payment models for platforms and marketplaces (we can help).

What are the supported digital currencies?

We can currently support any native and ERC-20 standard tokens including stablecoins such as USDT, USDC, PYUSD and DAI. You have the flexibility to configure the digital currencies that best suit your requirements.

Do you support on/off ramping?

Yes. You can use our partner network, or do it yourself, or use a mix of both to expand your coverage. You can review our list of fees and coverage.

How can I reconcile payments and keep track of their status?

We provide webhooks and a configurable payment reference field for that.

• Webhooks: You receive webhooks for payment related events and notifications (success, cancellations, failure with reason, etc).

• Payment reference field is configurable, and can refer to an invoice in your internal system.

• Used together, you can reconcile payments and process additional steps on your application backend.

How does Paygrid enforce security?

We take security seriously and approach it by design:

• We deploy a payment gateway on-chain owned by you to interface with our open source Grid Payment Protocol.

• You are the primary signer for all initiated payment requests but its possible to delegate Paygrid to handle actions on your behalf for ease of operations.

• Token approvals are handled using Permit2 mechanism.

• We enforce strict access controls at gateway level so only you as the operator can manage your integration and data.

• We don’t hold custody or approvals of funds nor does the protocol smart contracts, reducing the attack surface.

What compliance and KYT/AML protection does Paygrid provide?

We provide built-in transaction monitoring to protect against AML and fraud.

• Real-time fraud detection, risk scoring, and sanctions list screening for all payments.

• Automated address screening to identify risky wallets.

• You can configure additional custom compliance rules based on your business and legal requirements.

• These security policies are applied at protocol level for maximum security.

What is the expected pricing?

• For pilot projects: No cost, with a defined scope and timeline to test the solution.

• Post-pilot pricing: Pay-as-you-go 0.5% transaction processing fee. Then it can be lowered with volume-based discounts to leave room for your own margins + a fixed subscription amount. We’re happy to explore something that works for both of us, as our priority now is to make our early adopters happy and successful.