MCP INTEGRATION

Eight steps to take a payment. Or one sentence.

Payments.ai MoR is built to be set up by an agent instead of by you. It opens the account, wires the checkout into your app, turns on tax collection, and starts taking money. You show up to get paid, not to get set up.

The way it works now

You do all of it, in a browser

  1. Create an account with a payments provider and choose a plan.

  2. Submit your business for verification: legal entity, tax ID, ownership, bank account.

  3. Wait for approval before anything can go live.

  4. Generate API keys, then keep test and live credentials straight across every environment.

  5. Read the integration docs and pick which checkout primitive fits your app.

  6. Wire the webhooks: stand up an endpoint, subscribe to events, verify signatures, handle retries.

  7. Work out tax: where you owe it, where you have to register, and who files the returns.

  8. Test, swap keys, go live, and hope nothing silently 400s in production.

None of this is the product you set out to build. Most of it happens outside your editor, in tabs, on a day you meant to spend shipping.

The way it should work

One sentence. Zero clicks.

Your AI Agent
Use the Payments AI skill from github.com/paymentsai/Payments-AI-skills to set up payments for this app.
  • Your agent opens the accountThere is no signup form for you to fill in.

  • It reads your products and pricesOut of the code you already wrote.

  • It ships a working sandbox checkoutKeys, webhooks, and tax collection included.

  • It switches you to live and takes moneyNo form, no dashboard, no click from you.

The only thing you eventually do yourself is verify your identity to withdraw the money. Nothing before that needs a human.

  • Free to build
  • 2.7% + $0.30 when you take a payment
What your agent does for you

Nine jobs that used to be yours

Each of these is exposed to agents as a documented step, so the work happens inside the tool you are already building in.

  1. Opens the account

    Your agent creates the Payments.ai account on your behalf, using the project details it can already see. You never touch a signup form.

    Done for you
  2. Registers what you sell

    Products, prices, currencies, and billing intervals get created from the code and config in your repo, so the catalog matches the app.

    Done for you
  3. Issues and stores the keys

    Test and live credentials are written into your environment, scoped correctly, instead of copied out of a dashboard and pasted somewhere.

    Done for you
  4. Wires the checkout

    A hosted checkout is connected to your app in sandbox mode, with the success and cancel paths pointed at routes that exist.

    Done for you
  5. Subscribes to the webhooks

    Your agent creates the endpoint, subscribes to the events your app actually handles, and verifies signatures on the way in.

    Done for you
  6. Turns on tax collection

    Sales tax and VAT are calculated and collected at checkout wherever you sell. You do not write rate tables or threshold logic.

    Done for you
  7. Runs a test payment

    A sandbox transaction goes end to end and reports back, so the first thing you see is a payment that worked rather than a checklist.

    Done for you
  8. Switches on live payments

    When the sandbox run passes, the same agent moves you to live mode and real charges start settling to your balance. No approval queue in between.

    Done for you
  9. Stays available afterward

    Adding a plan, changing a price, or pulling revenue numbers is another sentence in the same session, not another trip to a settings page.

    Done for you
What actually moves off you

The part that needs a lawyer stops being your problem

Selling internationally is rarely blocked by payment code. It is blocked by tax registration, compliance, and who answers for a disputed charge.

  • You're not the merchant of record

    A registered, tax-compliant merchant of record is the seller on each transaction and appears on your customer's statement. Tax, VAT, and GST registration, filing, and remittance aren't yours.

  • No foreign entity to register

    Sell in 190+ countries without incorporating abroad, registering for VAT in Germany, or getting a GST number in Australia.

  • Tax collected at checkout

    Sales tax and VAT are calculated and collected on every sale. Across the US, EU, and UK they are also remitted for you, so there is nothing for you to file in those markets.

  • Disputes handled without you

    When a customer disputes a charge, you don't assemble evidence and you don't pay the dispute fee. It runs on the merchant-of-record side.

Coverage note: tax is collected at checkout everywhere you sell, and collected and remitted for you across the US, EU, and UK. Other markets are collect-only, with the remittance obligation still yours. Tell us where you sell and we will tell you which bucket each market is in.

PRICING

Free to build.

You pay 2.7% + $0.30 when you take a payment.

  • No setup fee, no monthly minimum, no PCI fee.

  • Sandbox, test payments, and the full agent setup cost nothing.

  • 2.7% + $0.30 is the processing rate. Tax handling, BNPL, and payouts are priced separately.

  • Ask us for the exact numbers on your setup before you build on them.

WHERE THE SENTENCE WORKS

Type it wherever you already build

The setup skill is a document at a URL, so any agent that can read a page and run tools can follow it. These are the surfaces we build against.

  • Claude Coworkweb & desktop
  • Claude Code
  • Cursor
  • Codex
  • Devin Desktopformerly Windsurf
  • Lovable
  • v0
  • Any MCP-capable agent
THE ONE THING YOU DO YOURSELF

You show up to get paid, not to get set up.

An agent can open the account, build the checkout, and collect live payments. What it cannot do is prove who you are. So the single human moment lands at the end, when you want the money out.

Verify your identity once, add a payout destination, and withdraw. Everything before that already happened without you.

Identity verification is required at withdrawal because a real, regulated entity is carrying the risk on every transaction. It is a rail requirement, not a form we invented.

THE BET

Agents are going to build most of what gets sold online.

So we are building the payments company with the fewest blockers in front of an agent: open an account, wire webhooks, run tests, make test mode behave, and take real money, all without stopping to ask a human for something.

Open your agent, point it at github.com/paymentsai/Payments-AI-skills, and watch it finish.

No credit card required · Sandbox checkout in minutes · Identity verification required to withdraw funds