Skip to content

PAYMENT ENGINE V2

Crypto payments that behave like real infrastructure.

Create invoices, receive across EVM networks, Bitcoin, and TRON, and keep every financial movement traceable—from chain observation to ledger entry and webhook delivery.

One V2 API. Exact accounting. No monthly commitment to begin.

LIVE PAYMENT FLOWAPI V2

Invoice #PC-2048

$4,280.00

USDT on BSC
  1. Destination allocated00:01
  2. Transfer observed00:02
  3. Finality reached00:03
  4. Ledger credited00:04
  5. Webhook delivered00:05
Payment completeevt_7fb…3d2
API/api/v2/*
ACCOUNTINGImmutable double-entry ledger
WEBHOOKSHMAC-SHA256 signed

ONE RELIABLE FLOW

Every handoff is explicit.

PayCoinPro keeps payment state, chain state, accounting, and delivery separate—so a retry never becomes a second financial effect.

  1. 01

    Create an invoice

    Send integer minor units and an idempotency key. V2 returns one invoice for one intent.

  2. 02

    Let the customer pay

    A hosted checkout presents an exact quote and a destination for the selected asset and network.

  3. 03

    Wait for real finality

    Overlapping scanners observe the transfer, match it, and advance only after the network policy is satisfied.

  4. 04

    React with confidence

    The ledger posts atomically, then the durable outbox delivers your signed webhook with retry history.

BUILT AROUND THE MONEY

Less dashboard theatre. More operational control.

Receive where customers already hold value

  • EVM-compatible networks
  • Bitcoin receiving
  • TRON receiving
  • Stablecoin-ready checkout

Control outbound movement

  • Reserved balance before signing
  • Allowlist, 2FA, and approval policy
  • Isolated EVM signing boundary
  • Reconciliation through finality

Automate without losing evidence

  • Replay-safe signed webhooks
  • Idempotent mutations
  • Delivery and retry history
  • Optional BNB → USDT on BSC

FOR DEVELOPERS

A contract your integration can trust.

Money is represented as integer strings, every mutation is idempotent, and the OpenAPI contract is generated from the same schemas that validate requests.

Read the API documentation
Integer moneyScoped credentialsOpenAPI contractTest and live isolation
POST /api/v2/invoicesapplication/json
curl -X POST https://app.paycoinpro.com/api/v2/invoices \
  -H "Authorization: Bearer pc_test_••••" \
  -H "Idempotency-Key: order-2048-create" \
  -H "Content-Type: application/json" \
  -d '{
    "fiatAmount": "428000",
    "currency": "USD",
    "orderId": "order-2048"
  }'
201 Created · inv_01K…B2Q

SECURITY BY STRUCTURE

Trust comes from boundaries you can explain.

Private-key operations sit behind an isolated signer boundary. Balances come from the ledger—not caches, provider responses, or webhook success. Administrative and payout decisions retain evidence for review.

Review our security approach
  • Signing isolated from the web application
  • Exact reservations before payouts
  • Network finality and reorg handling
  • Auditable jobs, retries, and manual review

The practical questions.

Which networks can receive payments?

Payment Engine V2 supports receiving on EVM-compatible networks, Bitcoin, and TRON. Automated payouts and sweeps currently operate on EVM-compatible networks.

How does PayCoinPro prevent duplicate charges?

Mutation requests use idempotency keys, and financial effects are protected by domain rules, database constraints, and an immutable double-entry ledger.

Can incoming funds be converted automatically?

The first supported conversion is optional native BNB to USDT on BSC. It is opt-in and off by default.

Is PayCoinPro non-custodial?

No. PayCoinPro is a custodial payment gateway. The platform operates receiving and movement infrastructure, while merchants control when and where approved payouts are sent.

START WITH A REAL FLOW

Create one invoice. See the whole system work.

Use the sandbox to test checkout, confirmation, balance updates, and signed webhook delivery before you move real value.