The simplest way for anyone to sell globally.

Launch your business in a day and get paid in USD-pegged stablecoins without a company or a USD bank account.

DemoTry a working storefront below,
before you build one with just a prompt
Demo
Request Demo

Start Small
Grow with Agents

Flexible plans that grow with you — no limits, no hidden fees.

Starter

For solo builders and early teams.

$25 / month

  • AI-powered automations
  • Workflow templates
  • 100 runs/month
  • Basic agent support
Popular

Pro

For teams with more control.

$60 / month

  • Everything in Starter
  • Smart triggers & scheduling
  • 1,000 runs/month
  • Shared team workspaces

Business

For scaling teams and advanced needs.

$90 / month

  • Everything in Pro
  • Unlimited runs
  • Role-based access
  • Dedicated onboarding

Start with Circle.

Build high-quality UIs and launch full apps effortlessly.

Start Free Trial
Features
Starter
Pro
Business
Monthly Price
$25
$60
$90
AI Agent Access
6 Agent
16 Agents
Unlimited + Agent
AI Skills & Actions
Basic
Advanced
Full Access
Components & Tools
Limited
Pro Components
Full Components
Project Limit
3 Projects
10 Projects
Unlimited Projects
Team Collaboration
Not included
Included
Included
Priority Support
Included
Included
Included
API Access
Not included
Not included
Unlimited + Agent
Custom Integrations
Not included
Not included
Included
AI Agent Training
6 Agent
Manual
Auto-Learning
Security & Compliance
Basic
Standard
Enterprise-Grade

Most common questions

Quick answers to your most common questions.

What is an AI Agent?
Can I train my agent to suit my workflow?
Do I need to install anything?
What tools can it integrate with?
Can I switch plans later?

Start building your product today

No credit card. No setup hassle. Just you, your workflow, and AI.

Your AI Workflow Companion

Terms of servicePrivacy policy
  1. 1Click "Get Pro Plan"
  2. 2Click "Pay Now"
  3. 3Payment received
Integration

Here’s your prompt & code

1 step integration - just copy the prompt or download the code package,
your AI agent will handle the rest.

AI Agent Prompt
Customize the Ping Business merchant-store UI for Demo Store.

Authoritative public source:
- Repository: https://github.com/PingBusiness/PingBusiness
- Branch: main
- Kit root: /merchant-store-vibe-coding-kit
- Kit page: https://github.com/PingBusiness/PingBusiness/tree/main/merchant-store-vibe-coding-kit
- Agent instructions: https://raw.githubusercontent.com/PingBusiness/PingBusiness/main/merchant-store-vibe-coding-kit/AGENTS.md

Retrieve the public repository yourself and read AGENTS.md, design/DESIGN_AGENT.md, prompts/DESIGN_PROMPT.md, docs/ESTORE_APP_API_SPEC.md, docs/SECURITY.md, and the complete source/merchant-store tree under the kit root before editing. Never use the obsolete /estore-ui tree elsewhere in the monorepo.

If you cannot retrieve the kit yourself — no repository access, no file access, and no web access, which is normal for a chat-only assistant — say so before anything else and ask me to download https://github.com/PingBusiness/PingBusiness/archive/refs/heads/main.zip and attach it to this conversation. Name the specific files you need if the whole archive is too large to attach. Do not reconstruct the kit from memory: a plausible-looking answer that does not match the real source fails only after I have deployed it, which is far worse than telling me you need the files.

Brand inputs:
- Store name: Demo Store
- Primary colour: #181D27 (near-black, for text and primary buttons)
- Secondary/accent colours: #FD4912 for accents and calls to action, #FAFAFA surfaces on #FFFFFF, #F5F5F5 borders
- Typography: Inter for headings and interface, Poppins for body copy
- Logo/assets: none attached yet — set the store name as a plain wordmark until I send a logo
- Requirements: match the storefront demo on pingbusiness.org: light surfaces, one accent colour, generous spacing, responsive from 360px up, and WCAG AA contrast. Swap any of the values above for mine when I send them.

I will attach the actual brand assets separately. Use only assets I supply or assets with verified redistribution rights.

Return a complete downloadable customized merchant-store source package, not a mockup or patch fragment. Preserve same-origin /api runtime configuration, authentication and refresh, inventory-aware cart validation, ordinary and recurring checkout behavior, authoritative checkout-status verification, read-only orders/payments, SPA routing, /healthz, and the rule that no merchant API key, Keycloak client secret, server credential, or central biz-app call may appear in browser code.

Design-layer changes only — do NOT change component structure, data flow, or scroll/overflow behaviour. In particular:
- The store name must come only from the store API (bind store?.name, left empty until it loads). Do NOT add a hardcoded store-name constant or fallback value; a hardcoded name flashes on reload before the real name arrives.
- Do NOT change the overflow/scroll of list containers (e.g. the orders/subscriptions table wrapper). Keep any overflow scoped to the existing narrow-screen media query; never set overflow-x or overflow-y unconditionally — overflow-x: auto forces overflow-y to auto, which clips the row menu and adds a spurious vertical scrollbar.

Run npm ci, the production build, the frontend secret scan, and relevant tests. Include DESIGN_REPORT.md with changed files and actual results. Preserve LICENSE, NOTICE, TRADEMARKS.md, and THIRD_PARTY_NOTICES.md; identify modified Ping Business-originated files as required by Apache-2.0.

Package the customized source/merchant-store tree only. Do not vendor a copy of the kit into it — no deployment/, keycloak/, scripts/, prompts/, docs/, design/, website/, or source/estore-app. I clone the kit for those, and every platform adapter clones it from the published repository at deploy time, so a bundled copy would be ignored anyway.

If you can run commands in this session, show me the result as you go: run npm ci and npm start in the customized source/merchant-store, then give me the exact URL the dev server prints — normally http://localhost:4200, but report what it actually printed, because Angular moves to another port when 4200 is taken. Keep it running while I give feedback so I can refresh after each change. Tell me plainly what that view does and does not prove: it shows layout, branding, typography, and responsive behaviour, but there is no estore-app behind it, so the catalogue, login, and checkout will not work and API calls fall back to http://localhost:5000. If you cannot run commands, say so and go straight to the packaged preview below instead of implying you served anything.

That dev server is a fast look, not the approval step. I still need to see the whole stack running before anything is deployed. Follow the "Local preview" section of prompts/DESIGN_PROMPT.md and include HANDOFF.md in the package. Reproduce the git clone, prepare-deployment.py --local, and docker compose commands in HANDOFF.md so I can also run them myself.

Do not ask me for my merchant identifier, store identifier, or merchant API key in this conversation — the preview step collects those. If I do give them to you and you have a working Docker daemon, you may bring the stack up yourself and give me the http://localhost address; put those values only in the 0600 file the generator writes. If your session has no Docker daemon or no container-registry access, say so directly instead of skipping this or reporting checks you did not run.

Treat my feedback as a loop: I look at the store, come back with corrections, you rebuild and reissue the package. Only once I confirm I am happy with it should we move to a real deployment.
Source Code for AI AgentDownload Code
import json
import logging
import os
import re
import time
import uuid
from datetime import datetime, timedelta
from functools import wraps
from decimal import Decimal, InvalidOperation
from typing import Any, Dict, List, Optional, Tuple
from urllib.parse import urlparse
from zoneinfo import ZoneInfo

import requests
from dotenv import load_dotenv
from flask import Flask, Response, jsonify, render_template_string, request
from flask_cors import CORS
from werkzeug.middleware.proxy_fix import ProxyFix

load_dotenv()

# -----------------------------------------------------------------------------
# Configuration
# -----------------------------------------------------------------------------
APP_PORT = int(os.getenv("ESTORE_APP_PORT", "5000"))
DEV_MODE = os.getenv("DEV_MODE", "true").lower() == "true"

# This app calls the existing ping business Flask service over the Docker network.
BIZ_APP_BASE_URL = os.getenv("BIZ_APP_BASE_URL", "http://biz-app:5000").rstrip("/")

# PaymentAsia helper access is proxied through biz-app so t-hosted
# estore deployments do not need direct network access to pa-app.
ESTORE_PUBLIC_BASE_URL = os.getenv("ESTORE_PUBLIC_BASE_URL", "").rstrip("/")
ESTORE_CHECKOUT_LANG = os.getenv("ESTORE_CHECKOUT_LANG", "")
# Default to the real PaymentAsia hosted checkout flow. This makes /checkout
# contact biz-app's authenticated pa-app proxy for signed hosted-payment fields
# and then auto-submit the browser/iframe to PaymentAsia. Simulated checkout is available only when
# explicitly enabled for isolated local testing.
# Optional CSP frame-ancestors value, for example: "'self' http://localhost:4200".
# Empty by default because many dev deployments serve Angular and estore-app from
# different ports, and the checkout return page is intentionally iframe-friendly.
ESTORE_CHECKOUT_FRAME_ANCESTORS = os.getenv("ESTORE_CHECKOUT_FRAME_ANCESTORS", "").strip()

Questions? scroll down to explore

Frequently asked questions

The questions every builder asks
before signing up.

Short answers. No legal-speak.

What is PingBusiness?

PingBusiness is an international payment operator that lets merchants quickly turn an idea into a global business - no US or EU entity, no USD bank account, no per-jurisdiction tax filing required. Accept any payment method your buyers already use - cards, e-wallets, and local payment methods, while settling revenue in USDC. Tax, VAT, chargebacks, invoicing, and receipts are all handled by PingBusiness.

How does PingBusiness work?

Merchants are provided with a PingBusiness-generated prompt that they can copy and paste into an AI assistant tool like Claude Code or Cursor to generate their own customized storefront. The merchant dashboard lets you manage multiple storefronts, products, orders, and payouts in one place.

Creating a PingBusiness merchant account requires only a swift merchant application. No business bank account needed and no waiting weeks for approval - all you need is a product and prompt to start selling.

Do I need a bank account to use PingBusiness?

No, you don’t need a bank account to use PingBusiness. You don’t even need a USD bank account to sell to US buyers. PingBusiness settles to a self-custodial USDC account , or a wallet address of your own choosing. Local bank withdrawal is available through partnered off-ramp providers when you wish to withdraw.

Do I need to register a company before using PingBusiness?

No, you can apply for a PingBusiness merchant account as an individual to set up payments, or as a Company. Neither path requires a bank account.

How much does PingBusiness cost?

A single 5% platform fee per transaction with no monthly fee, no setup fee and no test-mode charge. All fees are transparent with no surprises.

How fast does PingBusiness settle payments?

Settlement follows standard card-clearing through payment partners, typically a few business days before PingBusiness converts and routes funds to your wallet on-chain. It's faster than traditional cross-border rails (no SWIFT delays or multi-day intermediary holds).

How do I integrate PingBusiness into my app or website?

Take the PingBusiness source code package available publicly on GitHub, paste it into an AI coding tool like Claude or Cursor, and it generates a working storefront you can customize. No coding knowledge required. See here for step by step vibe-coder kit: https://github.com/PingBusiness/PingBusiness/tree/main/merchant-store-vibe-coding-kit

Which countries does PingBusiness support?

PingBusiness supports 240+ buyer countries. For the full list, contact support@pingbusiness.org.

Is PingBusiness the same as Stripe or PayPal?

No. Stripe and PayPal are payment processors with tax, VAT, and chargebacks as merchant's responsibility. PingBusiness acts as a payment operator, handling those obligations so merchants do not have to worry about tax and chargeback complications.

How does my customer pay if I’m a merchant using PingBusiness?

Buyers check out exactly like they would anywhere else - credit card, e-wallet, or local methods. USDC settlement happens on the merchant's side, invisible to the buyer.

What is a payment operator for global commerce, and do I need one?

A payment operator runs the payment layer on a merchant's behalf - accepting payments, handling tax, chargeback, invoicing compliance, and settling revenue in one consolidated form. It appears on the buyer-facing record, so the merchant isn't individually exposed to per-jurisdiction rules. For digital merchants selling outside Western markets, this removes most of the compliance overhead of selling globally.

limited intro offer

Ready to build without
boundaries?

Claim your zero-fee volume slot now and turn your idea into a running business in minutes—no company setup, no legacy banking friction.

1234 5678 9012 3456

A. MORGANVALID 01/27

4921 0042 7781 8317

L. CHENVALID 02/27

4012 8891 7720 5530

D. KIMVALID 07/27

3528 9931 0077 6654

J. MÜLLERVALID 06/27

6011 2256 7890 1122

R. PATELVALID 05/27

3714 4963 5398 4319

M. SILVAVALID 04/27

5212 7788 0091 4456

S. OKAFORVALID 03/27