Integrations

Ways to take crypto

Sorted by how much code each one needs, starting with none. Every route below reaches the same checkout and the same dashboard — pick the one that matches what you already have.

  1. Put the checkout on your page

    Two lines of HTML render the whole checkout inside your own page. No build step, no framework, no callback.

    Best for: Anyone who can paste HTML — Squarespace, Webflow, a WordPress block, a hand-written page.

    1. Add the script tag once, anywhere on the page.
    2. Put the element where you want the checkout to appear.
    3. Point on-paid at the page you want the customer to land on.
    <script src="https://easycryptopay.xyz/embed.js"></script>

<ecp-checkout token="inv_xK9mP2rT" on-paid="/thank-you"></ecp-checkout>

    The token comes from an invoice, so something has to create one first — a payment link, the dashboard, or one API call.

    Embedded checkout docs

  2. WooCommerce

    Not released yet

    A payment method in your WooCommerce checkout. The customer pays in crypto without leaving your store.

    Best for: WordPress shops.

    1. Install the plugin and open WooCommerce → Settings → Payments.
    2. Paste a test API key and leave test mode on.
    3. Add the callback URL it shows you as a webhook, and paste the signing secret back.
    4. Place a test order, complete it from your dashboard, and watch the order move to Processing on its own.

    USD stores only for now — the API prices in USD and the plugin has no exchange rate to convert with, so it hides itself rather than charge the wrong amount. Refunds are not automated.

  3. REST API and webhooks

    Create payments, read them back, and get a signed callback when money lands. Everything the dashboard does, you can do.

    Best for: Anyone building their own checkout, or wiring payments into a system that already exists.

    1. Mint an ecp_test_ key under Manage → API keys.
    2. POST an invoice and redirect the customer to the link it returns.
    3. Verify the signature on the webhook, then mark your order paid.
    4. Swap the test key for a live one. Nothing else changes.
    curl -X POST https://easycryptopay.xyz/api/invoices \
  -H "Authorization: Bearer ecp_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "title": "Order #1042", "amount_usd": 49, "metadata": { "order_id": "1042" } }'
    Read the API docs

Libraries

You do not need one — the API is JSON over HTTPS and the whole surface is a few endpoints. These save you writing the signature check.

  • Node.jsPublished
    npm install @easycryptopay/node

    Client plus a webhook signature verifier.

  • PHPComing
    composer require easycryptopay/easycryptopay-php

    For Laravel, Magento, WHMCS and plain PHP. Written; not on Packagist yet.

  • Anything elseGenerate one
    https://easycryptopay.xyz/openapi.json

    The full API as OpenAPI. Point a generator at it and you have a client in a minute — Python, Go, Ruby, C#, Java, Rust.

Building with an AI assistant

If you are working with Claude, Cursor, Copilot or anything similar, two URLs are all it needs. Both are machine-readable, both are generated from the running code, and neither can drift from the API the way a pasted snippet does.

  • easycryptopay.xyz/llms.txt

    The whole integration in one page: endpoints, the exact webhook signature scheme, the test-mode flow, and the mistakes that are expensive. Written to be pasted into a context window.

  • easycryptopay.xyz/openapi.json

    Every endpoint, parameter and response shape, as OpenAPI. Enough for an assistant — or a code generator — to write a correct client without guessing.

Paste this to start
Read https://easycryptopay.xyz/llms.txt and add EasyCryptoPay
to this project as a payment method.

Use test mode (an ecp_test_ key) and do not touch live keys.
Verify the webhook signature over the RAW request body before
trusting any event.

Something missing? Tell us what you are building — the list is short on purpose and grows in the order people ask.