Skip to content

Justlink

Help & FAQ

What is Justlink?

Create a fixed-amount USDC payment link on Arc, share it, and get paid in one transaction. Optional splits send portions to multiple addresses in the same settle.

How do I create a link?

  1. Connect a wallet on Arc
  2. Set title, amount, optional splits / expiry / webhook
  3. Confirm the create transaction, then share the pay link

How does the payer pay?

Open the link, connect on Arc with enough USDC (payment + gas), and confirm. When the wallet supports one-step authorization, payment can be a single transaction; otherwise approve USDC, then pay.

How do I add Arc to my wallet?

On the payment page, tap Switch to Arc — most wallets will prompt to add the chain. If that fails, add it manually with the values below (Settings → Networks → Add network).

Add Arc manually

In your wallet: Settings → Networks → Add network, then paste these values.

Network name

Arc

Chain ID

5042

Currency symbol

USDC

RPC URL

https://rpc.mainnet.arc.io

Block explorer

https://explorer.arc.io

How do I get USDC on Arc?

Payments use ERC-20 USDC (6 decimals). Network fees use native USDC (18 decimals). Keep both funded on Arc.

Mainnet: bridge or transfer official USDC onto Arc. See arc.io for network details. You need ERC-20 USDC for the payment and native USDC for gas.

ERC-20 USDC contract

0x3600000000000000000000000000000000000000

Add this token in your wallet if USDC does not appear after funding.

Are payments reversible?

No. Confirmed on-chain transfers cannot be undone by Justlink. There are no chargebacks.

Do you hold my funds?

No. Justlink is non-custodial: USDC moves from the payer to the recipients you set in the same on-chain settle.

Payment limits

Product limits: $5,000 USDC per payment link and $25,000 USDC cumulative per recipient wallet per day. Official Arc USDC only. Not financial advice. See Terms, Disclaimer, and Security.

Webhooks

Optional HTTPS webhook URLs receive a payment.paid JSON event after the payment is verified on-chain. When webhook signing is enabled, each request includes an HMAC signature header so you can verify authenticity.

Merchant API

Versioned REST under /api/v1. API keys are hashed and bound to one creator wallet. The server never holds your private key — createSession / cancel stay wallet transactions. Payment limits still apply. Mint and revoke keys on Developers. Machine-readable spec: /openapi-v1.json. Copy-paste examples live in the repo under examples/merchant-api/.

Auth

  • Call API routes with Authorization: Bearer jl_test_… (testnet) or jl_live_… (mainnet). Wrong network prefix → 401.
  • Mint / list / revoke keys with a wallet signature on Developers (or POST /api/v1/keys/mint). The plaintext secret is shown once.
  • Scopes: sessions:read|write, webhooks:read|write.

Create a payment link

  1. POST /api/v1/sessions/prepare with JSON body { "amount": "10.00" } — validates limits and returns createSessionArgs + router / chainId.
  2. From the key's wallet, broadcast on-chain createSession using those args. Read sessionId from the Created event.
  3. POST /api/v1/sessions with sessionId, title, optional memo / webhookUrl. Response includes payUrl.

Send Idempotency-Key on prepare and register so retries do not double-reserve. Cancel remains wallet-only (My links).

Webhooks

HTTPS only (no localhost). After on-chain pay is verified, Justlink POSTs payment.paid. If WEBHOOK_SIGNING_SECRET is set on the server, each request includes X-Justlink-Signature: sha256=… (HMAC-SHA256 of the raw body; legacy alias X-Arc-Pay-Signature).

{
  "type": "payment.paid",
  "sessionId": "42",
  "title": "Invoice",
  "memo": null,
  "creator": "0x…",
  "seriesId": null,
  "payer": "0x…",
  "amount": "1000000",
  "payTxHash": "0x…",
  "explorerUrl": "https://…",
  "at": "2026-10-17T00:00:00.000Z"
}

List recent deliveries: GET /api/v1/webhooks/deliveries. Retry: POST /api/v1/sessions/:id/webhooks/retry. If the payer closes the tab before client notify, server cron paid-detect still enqueues the webhook.

Common errors

  • unauthorized — missing / revoked / wrong-prefix key
  • forbidden — missing scope, or session creator ≠ key wallet
  • limit_exceeded — per-link ($5k) or daily recipient ($25k) cap
  • validation_error — bad amount, unsafe webhook URL, invalid idempotency key
  • rate_limited — slow down and retry

Still stuck?

See Support.