Per-provider limits (expirationTime)
Overview
The EYT API exposes a platform-wide floor and ceiling for the cash-in expirationTime (in seconds):
- Minimum:
30(30 seconds) - Maximum:
604800(7 days) - Default:
86400(24 hours)
Beyond those limits, the API rejects the request with a validation error. Additionally, each PIX provider behind your account may impose its own, stricter limits. When expirationTime is below the account provider's minimum, the API responds 400 Bad Request with errorCode set to PROVIDER_EXPIRATION_BELOW_MINIMUM and the accepted minimum in the details. When it is above the account provider's maximum, errorCode is PROVIDER_EXPIRATION_ABOVE_MAXIMUM and details.providerMaxSeconds carries the accepted ceiling.
Per-provider limits table
| Provider | Minimum | Maximum | Granularity | Note |
|---|---|---|---|---|
| Woovi | 300 (5 min) | 604800 (7 days) | seconds | Limit imposed by the Woovi API |
| BRZip | 30 (30 s) | 604800 (7 days) | seconds | — |
| Magen | 30 (30 s) | 604800 (7 days) | seconds | — |
| Hyperwallet | 30 (30 s) | 604800 (7 days) | seconds | — |
| GolPix | 86400 (1 day) | 604800 (7 days) | days | The GolPix API only accepts expiresInDays (1–30 integer). Sub-day values are rejected to avoid silent surprises. Non-multiples of 86400 are rounded up to the next whole day. |
| OnlyUp | 30 (30 s) | 604800 (7 days) | seconds | — |
| FyHub | 30 (30 s) | 604800 (7 days) | seconds | — |
| Treeal | 30 (30 s) | 604800 (7 days) | seconds | — |
| AvivPay | 60 (1 min) | 86400 (24 h) | seconds | The AvivPay API accepts between 60 s and 24 h. Above 86400 the API responds PROVIDER_EXPIRATION_ABOVE_MAXIMUM. |
| NixFin | 30 (30 s) | 604800 (7 days) | seconds | — |
| a55 | 30 (30 s) | 604800 (7 days) | seconds | The a55 API accepts up to 30 days, but the platform ceiling (7 days) applies. The value is sent in seconds (expiresInSeconds), so sub-day windows are honored exactly. |
| AvivPay IP | 30 (30 s) | 604800 (7 days) | seconds | Same API as a55: accepts up to 30 days, but the platform ceiling (7 days) applies. The value is sent in seconds (expiresInSeconds), so sub-day windows are honored exactly. |
Error shape
When the submitted expirationTime is below the account provider's minimum:
HTTP/1.1 400 Bad Request
Content-Type: application/json{
"statusCode": 400,
"code": "PIX_PROVIDER_EXPIRATION_BELOW_MINIMUM",
"errorCode": "PROVIDER_EXPIRATION_BELOW_MINIMUM",
"message": "Provider woovi requires expirationTime >= 300s (got 30s)",
"userMessage": "O provedor woovi exige tempo mínimo de 300 segundos para expiração.",
"details": {
"provider": "woovi",
"providerMinSeconds": 300,
"granularity": "seconds",
"userExpirationTime": 30
},
"errorId": "<correlation-id>",
"timestamp": "2026-05-05T12:34:56.789Z",
"path": "/api/pix/cash-in",
"method": "POST"
}Use details.providerMinSeconds to retry the request with the minimum accepted value.
How do I know which provider my account uses?
Provider configuration is per account and set at account creation. Contact your integration manager or check the admin panel if you are unsure which provider is active. For most integrations this is transparent, except when you need expiration windows shorter than 5 minutes on a Woovi account (shorter than 1 day on a GolPix account, or longer than 24 hours on an AvivPay account).