Available settlement dates: an advance indication of arrival date
For a payout currency, returns settlement dates within the next week recognized by the upstream, with their valid flags. The first question after ordering is when funds will arrive; this is the answer available before ordering.
⚠ These are upstream business days, not today calculated in UTC. Upstream documentation requires the settlement date to be “today” without specifying its timezone. The dates differ for some hours each day, and weekends or public holidays can differ by whole days. We therefore forward the upstream answer unchanged and calculate no dates ourselves. Do not derive your own working-day schedule either.
⚠ After ordering, the exact date is payout_date in GET /v1/remittances. This endpoint is a forecast; that field is the fact.
⚠ With same_currency: true, where payout currency equals our settlement currency for stablecoin direct payouts, dates may be empty. The upstream may not maintain this table for that case, and it does not mean payout is impossible: for corridors requiring no conversion, we fall back to the current day. Do not render an empty list as “this corridor cannot send today”.
Query Parameters
| Field | Type | Required | Description |
|---|---|---|---|
currency |
string | Required | Payout currency, three uppercase letters. |
line |
"express" | "pobo" | Optional | Product line, determining which settlement currency is used for the query. Unrecognized values are treated as express. |
Response
{
"settlement_currency": "USD",
"payout_currency": "GBP",
"same_currency": false,
"dates": [
{
"date": "2026-08-13",
"valid": true
},
{
"date": "2026-08-14",
"valid": true
},
{
"date": "2026-08-15",
"valid": false
}
],
"earliest_valid": "2026-08-13"
}invalid_request: currency missing or not three uppercase letters. · product_not_available: line disabled. · service_unavailable: no settlement currency configured for this line.upstream_error: we could not query the upstream.
⚠ This deliberately does not fall back to an empty list. Empty means this currency pair has no settlement dates;
the actual situation is that we could not obtain an answer. Telling users the corridor cannot send today would misrepresent our outage as a business rule.
Retry the request.curl -X GET 'https://api.zinfra.vip/v1/remit/conversion-dates' \
-H 'x-auth-token: Bearer $TOKEN'const res = await fetch("https://api.zinfra.vip/v1/remit/conversion-dates", {
method: "GET",
headers: {
"x-auth-token": "Bearer $TOKEN",
},
});
// Keep monetary amounts as strings, never numbers.
const data = await res.json();import requests
res = requests.get(
"https://api.zinfra.vip/v1/remit/conversion-dates",
headers={
"x-auth-token": "Bearer $TOKEN",
},
)
# Use Decimal(str(...)) for amounts, not float.
data = res.json()req, _ := http.NewRequest("GET", "https://api.zinfra.vip/v1/remit/conversion-dates",
nil)
req.Header.Set("x-auth-token", "Bearer $TOKEN")
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/remit/conversion-dates"))
.header("x-auth-token", "Bearer $TOKEN")
.method("GET", HttpRequest.BodyPublishers.noBody())
.build();
// Use String / BigDecimal for amounts, not double.$ch = curl_init('https://api.zinfra.vip/v1/remit/conversion-dates');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'GET',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'x-auth-token: Bearer $TOKEN',
],
]);
$res = curl_exec($ch);
// Use bcmath / strings for amounts, not floatval.{
"settlement_currency": "USD",
"payout_currency": "GBP",
"same_currency": false,
"dates": [
{
"date": "2026-08-13",
"valid": true
},
{
"date": "2026-08-14",
"valid": true
},
{
"date": "2026-08-15",
"valid": false
}
],
"earliest_valid": "2026-08-13"
}