Z Zise Developers
/
简体中文
Global Acquiring › API Reference › QR Payments

Read-only QR payment configuration: payment assets / balances / fees / limits

GET /v1/qrpay/config scope: qrpay:read
On behalf of a member · x-on-behalf-of required

Retrieve this when opening the checkout screen. With available: false, reason explains why and assets is empty.

── assets is filtered server-side ── Using the raw product-configuration list would let users reach the final step before discovering an asset was delisted. Order follows this member’s payment preferences; the first row is the default debit asset.

⚠ You do not determine the debit asset. preferred_asset in POST /v1/qrpay/payments only means try this asset first. Valid values come from assets[].asset here.

── Only two public fee components ── fee_bps and fee_fixed. Exchange-rate premiums and cost discounts are margin parameters and are never exposed.

── Limits ── Amounts are formatted human-readable strings, with precision supplied by limits.ledger_scale. "" means no such limit, or unlimited. kyc_trigger_amount is the threshold above which L1 is required; "" means no trigger, not mandatory KYC for everyone.

⚠ require_step_up is always true: every QR payment requires the end user to confirm on our hosted screen. This flag lets you design that step in advance instead of discovering it when POST /v1/qrpay/payments returns 400.

FieldTypeRequiredDescription
x-on-behalf-of string Required

Response

200OK
{
  "available": true,
  "assets": [
    {
      "asset": "USDT",
      "ledger_scale": 6,
      "display_scale": 2,
      "balance": "520.000000"
    }
  ],
  "pricing": {
    "fee_bps": 50,
    "fee_fixed": "0.000000"
  },
  "limits": {
    "ledger_scale": 6,
    "min_amount": "1.000000",
    "single_limit": "2000.000000",
    "daily_limit": "5000.000000",
    "kyc_trigger_amount": "500.000000"
  },
  "require_step_up": true
}
Request 
curl -X GET 'https://api.zinfra.vip/v1/qrpay/config' \
  -H 'x-auth-token: Bearer $TOKEN' \
  -H 'x-on-behalf-of: $MEMBER_ID'
const res = await fetch("https://api.zinfra.vip/v1/qrpay/config", {
  method: "GET",
  headers: {
    "x-auth-token": "Bearer $TOKEN",
    "x-on-behalf-of": "$MEMBER_ID",
  },
});
// Keep monetary amounts as strings, never numbers.
const data = await res.json();
import requests

res = requests.get(
    "https://api.zinfra.vip/v1/qrpay/config",
    headers={
        "x-auth-token": "Bearer $TOKEN",
        "x-on-behalf-of": "$MEMBER_ID",
    },
)
# Use Decimal(str(...)) for amounts, not float.
data = res.json()
req, _ := http.NewRequest("GET", "https://api.zinfra.vip/v1/qrpay/config",
    nil)
req.Header.Set("x-auth-token", "Bearer $TOKEN")
req.Header.Set("x-on-behalf-of", "$MEMBER_ID")
res, err := http.DefaultClient.Do(req)
// Decode amount fields as string, not float64.
HttpRequest req = HttpRequest.newBuilder()
    .uri(URI.create("https://api.zinfra.vip/v1/qrpay/config"))
    .header("x-auth-token", "Bearer $TOKEN")
    .header("x-on-behalf-of", "$MEMBER_ID")
    .method("GET", HttpRequest.BodyPublishers.noBody())
    .build();
// Use String / BigDecimal for amounts, not double.
$ch = curl_init('https://api.zinfra.vip/v1/qrpay/config');
curl_setopt_array($ch, [
  CURLOPT_CUSTOMREQUEST => 'GET',
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    'x-auth-token: Bearer $TOKEN',
    'x-on-behalf-of: $MEMBER_ID',
  ],
]);
$res = curl_exec($ch);
// Use bcmath / strings for amounts, not floatval.
200 
{
  "available": true,
  "assets": [
    {
      "asset": "USDT",
      "ledger_scale": 6,
      "display_scale": 2,
      "balance": "520.000000"
    }
  ],
  "pricing": {
    "fee_bps": 50,
    "fee_fixed": "0.000000"
  },
  "limits": {
    "ledger_scale": 6,
    "min_amount": "1.000000",
    "single_limit": "2000.000000",
    "daily_limit": "5000.000000",
    "kyc_trigger_amount": "500.000000"
  },
  "require_step_up": true
}