Vai al contenuto
Beta privata · Non ancora aperto al pubblico. Gli account sono solo su invito. Richiedi l'accesso →
AywaPay

Sviluppatori

Documentazione API

Tutto il necessario per accettare criptovalute con AywaPay: crea fatture, invia pagamenti e verifica le callback.

Per iniziare

  1. Richiedi l'accesso (siamo in beta privata: con l'invito apri il tuo account) e aggiungi un negozio, poi attiva l'autenticazione a due fattori.
  2. Apri la scheda API del negozio e crea la sua chiave segreta. Facoltativamente, consenti solo gli IP del tuo server.
  3. Imposta lo Status URL del negozio: è lì che inviamo in POST ogni cambiamento delle fatture.
  4. Crea le fatture dal tuo server e indirizza il cliente all'invoice_url restituito.

URL di base

https://api.aywapay.com/api/v1

Autenticazione

api_key come parametro di query in ogni richiesta. Non inserirlo mai in un browser o in un'app.

Ogni risposta è in JSON: { "status": "success", "data": { … } } oppure { "status": "error", "data": { "code": 103, "message": "…" } }.

Invoices

Create an invoice

GET/api/v1/invoices/new

Creates a payment request and returns the link of the hosted payment page. Price it in fiat (the customer picks the coin) or in one coin.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
order_number*Your order id. Unique per store; repeating it is refused unless return_existing=1.
order_name*What the customer pays for, shown on the payment page.
source_currency + source_amountFiat price, e.g. USD and 49.99. Converted at the current rate.
currency + amountOr a crypto price in one coin, e.g. BTC and 0.001. currency alone fixes the coin of a fiat invoice.
allowed_psys_cidsComma list of coins the customer may choose, e.g. BTC,USDT_TRX. Coins whose minimum the order does not reach are left out.
callback_urlWhere status changes are POSTed (default: the store's Status URL). Add ?json=true for a JSON body.
success_callback_url / fail_callback_urlExtra callbacks for paid and failed invoices.
success_invoice_url / fail_invoice_urlWhere the payment page's "Back to store" button goes.
emailCustomer email: the payment link and receipt are sent there.
descriptionShown under the order name.
expire_minMinutes before the invoice expires (default: the store's setting, else 60).
return_existing1 = an existing order_number returns that invoice instead of an error.
Request
curl -G "https://api.aywapay.com/api/v1/invoices/new" \
  -d source_currency=USD -d source_amount=49.99 \
  -d order_number=1042 --data-urlencode "order_name=Pro plan" \
  --data-urlencode "callback_url=https://yourshop.com/callback?json=true" \
  -d api_key=$AYWAPAY_SECRET_KEY
Response data
{
  "txn_id": "65f1c0ffee00000000000001",
  "invoice_url": "https://pay.aywapay.com/invoice/65f1c0ffee00000000000001",
  "invoice_total_sum": "0.5512"
}

Get an invoice

GET/api/v1/invoices/:id

Full invoice: status, coin, address, amounts, confirmations and transactions.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/invoices/:id" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{
  "invoice": { "txn_id": "…", "status": "completed", "psys_cid": "LTC",
    "amount": "0.5512", "received_amount": "0.5512",
    "remaining_amount": "0", "wallet_hash": "ltc1q…",
    "expected_confirmations": 6, "tx_url": ["…"], "tx_id": ["…"] },
  "active_invoice_id": "…"
}

Withdrawals & payouts

Send a withdrawal or a mass payout

GET/api/v1/operations/withdraw

Sends crypto from your balance. The network (gas) fee is taken in the same coin. Can be turned off per store (Stores & API → API).

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
psys_cid*Coin, e.g. USDT_TRX.
type*cash_out (one address) or mass_cash_out (many).
to*Address, or comma list for mass_cash_out.
amount*Amount, or comma list in the same order as to.
feePlannormal (default) or priority.
Request
curl -G "https://api.aywapay.com/api/v1/operations/withdraw" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "id": "65f1c0ffee00000000000002", "type": "cash_out", "status": "pending",
  "psys_cid": "USDT_TRX", "currency": "USDT", "amount": "25.00", "fee": "1.25",
  "wallet_hash": "T…", "tx_url": "", "tx_id": [] }

Estimate the network fee

GET/api/v1/operations/fee/:psys_cid

Fee of a withdrawal before you send it.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
addresses*Comma list of recipients.
amounts*Comma list of amounts.
feePlannormal or priority.
Request
curl -G "https://api.aywapay.com/api/v1/operations/fee/:psys_cid" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "fee": "0.0000021", "psys_cid": "LTC", "currency": "LTC", "plan": "normal" }

Fee and commission of a withdrawal

GET/api/v1/operations/commission/:psys_cid

What the withdrawal costs in total: network fee plus any commission.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
addressesComma list of recipients.
amountsComma list of amounts.
typecash_out or mass_cash_out.
Request
curl -G "https://api.aywapay.com/api/v1/operations/commission/:psys_cid" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "commission": "0", "fee": "0.0000021", "feeUnit": "LTC", "plan": "normal",
  "plans": { "normal": { "value": "0.0000021" }, "priority": { "value": "0.0000042" } } }

Fee plans of a coin

GET/api/v1/operations/fee-plan/:psys_cid

Details of the normal and priority plans.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/operations/fee-plan/:psys_cid" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "normal": { … }, "priority": { … } }

Balances, operations & coins

Balance of one coin

GET/api/v1/balances/:psys_cid

Available balance of your account in that coin.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/balances/:psys_cid" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "psys_cid": "LTC", "currency": "LTC", "balance": "0.0510" }

List operations

GET/api/v1/operations

Invoices, deposits and withdrawals, newest first.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
pagePage number (default 1).
limitItems per page (default 10).
Request
curl -G "https://api.aywapay.com/api/v1/operations" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "operations": [ … ], "_meta": { "totalCount": 3, "pageCount": 1, "currentPage": 1, "perPage": 10 } }

Get one operation

GET/api/v1/operations/:id

One invoice, deposit or withdrawal by id.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/operations/:id" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "id": "…", "type": "invoice", "status": "completed", … }

Coins and rates

GET/api/v1/currencies/:fiat

Every coin you can accept, with its rate in a fiat currency (default USD) and minimum invoice.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/currencies/:fiat" -d api_key=$AYWAPAY_SECRET_KEY
Response data
[ { "cid": "BTC", "name": "Bitcoin", "rate_usd": "0.0000125", "min_sum_in": "0.0001", "min_withdraw": "0.0002", … } ]

Your store

GET/api/v1/shops

The store the key belongs to.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
Request
curl -G "https://api.aywapay.com/api/v1/shops" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "id": "…", "name": "My Shop", "plan": "api", … }

Deposit addresses (White Label)

Permanent address for one of your users

GET/api/v1/shops/deposit/new

A fixed address per user and coin. Every payment to it is credited to you and reported with a pay_in callback. White Label plan.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
psys_cid*Coin, or a comma list for several.
uid*Your id of the user.
Request
curl -G "https://api.aywapay.com/api/v1/shops/deposit/new" -d api_key=$AYWAPAY_SECRET_KEY
Response data
{ "psys_cid": "USDT_TRX", "uid": "user-17", "hash": "T…" }

List deposit addresses

GET/api/v1/shops/deposit

Addresses already given out.

ParameterDescription
api_key*Your store's secret key (Stores & API → API). Keep it on your server.
uidOnly this user.
psys_cidOnly this coin.
Request
curl -G "https://api.aywapay.com/api/v1/shops/deposit" -d api_key=$AYWAPAY_SECRET_KEY
Response data
[ { "psys_cid": "BTC", "uid": "user-17", "hash": "bc1q…" } ]

Callback (webhook)

On every invoice status change we POST the invoice to its callback_url (or the store's Status URL). Withdrawals made with your API key are reported to the Status URL too, when they are sent, completed, fail or are cancelled. Add ?json=true to the URL to get JSON instead of a form post.

  • Answer with HTTP 200. Anything else is retried 8 more times over about two days, then shown as Failed in your dashboard.
  • Always check verify_hash before trusting a callback.
  • Stores & API → Webhooks shows every attempt, lets you resend one, and sends a signed test.
Invoice callback
{
  "txn_id": "65f1c0ffee00000000000001",
  "ipn_type": "invoice",
  "merchant": "My Shop",
  "merchant_id": "3f2a9c1e-…",
  "status": "completed",
  "amount": "0.5512",
  "currency": "LTC",
  "order_number": "1042",
  "order_name": "Pro plan",
  "confirmations": "6",
  "source_currency": "USD",
  "source_amount": "49.99",
  "invoice_total_sum": "0.5512",
  "verify_hash": "…"
}
Withdrawal callback
{
  "txn_id": "65f1c0ffee00000000000002",
  "ipn_type": "cash_out",
  "merchant": "My Shop",
  "merchant_id": "3f2a9c1e-…",
  "status": "completed",          // pending | completed | error | cancelled
  "psys_cid": "USDT_TRX",
  "currency": "USDT",
  "amount": "25.00",
  "fee": "1.25",
  "to": "T…",
  "tx_id": "a1b2…",
  "comment": "",
  "verify_hash": "…"
}

Verifica della firma

verify_hash is an HMAC-SHA1 with your store's secret key: of PHP's serialize() of the key-sorted fields for form posts, or of JSON.stringify of the body without verify_hash for JSON.

PHP (form post)
<?php
// Your store's secret key (Stores & API → API)
$secretKey = getenv('AYWAPAY_SECRET_KEY');

$post = $_POST;                       // form-encoded callback
$received = $post['verify_hash'] ?? '';
unset($post['verify_hash']);
ksort($post);
$expected = hash_hmac('sha1', serialize($post), $secretKey);

if (!hash_equals($expected, $received)) {
    http_response_code(400);
    exit('bad signature');
}
if ($post['status'] === 'completed' || $post['status'] === 'mismatch') {
    // mark order $post['order_number'] as paid
}
http_response_code(200);
Node.js (JSON)
import crypto from "node:crypto";

// callback_url ends with ?json=true, so the body is JSON
app.post("/callback", express.json(), (req, res) => {
  const { verify_hash, ...body } = req.body;
  const expected = crypto
    .createHmac("sha1", process.env.AYWAPAY_SECRET_KEY)
    .update(JSON.stringify(body))
    .digest("hex");
  const given = Buffer.from(String(verify_hash ?? ""));
  const wanted = Buffer.from(expected);
  if (given.length !== wanted.length || !crypto.timingSafeEqual(given, wanted)) {
    return res.status(400).send("bad signature");
  }

  if (body.status === "completed" || body.status === "mismatch") {
    // mark order body.order_number as paid
  }
  res.sendStatus(200);
});

Modalità test (sandbox)

Every store can have a test key next to its live key (Stores & API → API → Test key). It works with the same endpoints, with no real money:

  • Invoices made with the test key are test invoices: no deposit address, nothing on a blockchain.
  • Their payment page has Simulate buttons: paid, overpaid, underpaid, expire. Each fires your normal callback, with test=true and signed with the test key.
  • Test invoices never touch your balance. Withdrawals and deposit addresses need the live key (error 229); balances read 0.
  • Order numbers are separate: a test order never blocks a live one with the same number.
Create a test invoice
curl -G "https://api.aywapay.com/api/v1/invoices/new" \
  -d source_currency=USD -d source_amount=10 \
  -d order_number=test-1 -d order_name=Test \
  -d api_key=$AYWAPAY_TEST_KEY

Il tuo dominio di pagamento (White Label)

Con il piano White Label, fatture, link di pagamento, pagine di donazione e pulsanti di pagamento possono aprirsi sul tuo indirizzo, come pay.yourshop.com, invece che sul nostro. I clienti vedono solo il tuo dominio e il tuo marchio. Basta un record DNS e una decina di minuti, senza bisogno di uno sviluppatore.

Come configurarlo

  1. Passa il negozio al piano White Label (negozio → Generale).
  2. Apri la scheda Pagina di pagamento del negozio. In “Dove si aprono i link di pagamento”, scegli Il mio dominio.
  3. Inserisci un sottodominio di tua proprietà, come pay.yourshop.com (non yourshop.com da solo). Leggi le commissioni, se vengono mostrate, poi salva.
  4. Copia il record mostrato a schermo e aggiungilo dove gestisci il DNS del tuo dominio (Cloudflare, GoDaddy, Namecheap, Hostinger e così via). Nella dashboard trovi una breve guida per ciascuno.
  5. Attendi. Verifichiamo ogni minuto: DNS → Certificato HTTPS → Attivo. Di solito servono da 5 a 30 minuti; i nuovi record DNS possono richiedere qualche ora. Ti mandiamo un'email quando è attivo.

Il record DNS

TipoNomeValore
CNAMEpay<tuo-codice>.domains.aywapay.com

Copia la destinazione esatta dalla tua dashboard: è unica per il tuo negozio. La maggior parte dei provider vuole come nome solo la prima parte (pay).

Usi Cloudflare?

Imposta il record su “DNS only” (nuvola grigia). Con la nuvola arancione attiva il certificato non può essere emesso e la verifica segnala che il record passa dal proxy.

Se la verifica non va a buon fine

  • Record non trovato: il CNAME non c'è ancora oppure il DNS non si è ancora propagato. Controlla il nome e attendi qualche minuto.
  • Punta altrove: un altro record (A, AAAA o un vecchio CNAME) usa lo stesso nome. Eliminalo e tieni solo il CNAME.
  • Dietro il proxy: la nuvola arancione di Cloudflare è attiva. Imposta il record su “DNS only”.
  • Certificato in attesa: il DNS è corretto e il certificato HTTPS di solito arriva entro pochi minuti.

Quando è attivo

  • I link nuovi e quelli esistenti si aprono sul tuo dominio. I link già inviati con il nostro indirizzo continuano a funzionare.
  • Puoi tornare al link AywaPay in qualsiasi momento con un clic; il tuo dominio resta salvato.
  • Se il tuo DNS smette di puntare a noi per 24 ore, i link tornano da soli al nostro indirizzo e ti avvisiamo via email, così nessun pagamento va perso.
  • Se il tuo account prevede commissioni per il dominio proprio, le vedi prima di salvare e vengono addebitate sul tuo saldo.

Non vedi l'opzione? Serve il piano White Label. Se il tuo negozio ce l'ha già, scrivi a [email protected].

Stati delle fatture

newCreated, nothing received yet.
pendingPayment seen on the blockchain, waiting for confirmations.
completedPaid in full and confirmed. Ship the order.
mismatchOverpaid and confirmed: paid, the extra is in your balance too.
expiredTime ran out. With some money received it stays open for the rest of the payment.
cancelledCancelled before payment.
cancelled duplicateThe customer switched to another coin; the new copy carries on.
errorSomething went wrong; contact support.

Errori

CodeHTTPMeaning
101401Wrong or missing api_key.
103400A parameter is missing or invalid (the message names it).
105422Coin not available for this store.
111404No such invoice or operation.
116422Balance too low for amount plus fee.
202429Too many requests; slow down.
210422Below the coin's minimum.
211422order_number already used.
213422Invalid address for this coin's network.
218422Saved addresses only is on and the address is not saved.
224422The address is blocked for compliance reasons (sanctions list).
225422Over a withdrawal limit. Check your own limits in Settings → Security, or contact support.
229422Not possible with the test key (withdrawals, deposit addresses): use the live key.
303403Request from an IP not in the store's allowed IPs.

Domande? Scrivi a [email protected].