PAYSTAR / DEVELOPER DOCUMENTATION

Downloads

Credential-free schemas, profile-specific Postman templates and separately downloadable reference dictionaries.

[01]

A consistent documentation package

All files below belong to documentation revision 2026-09-15.5, based on API baseline 2026-08-25.9. Only owner-approved schema changes are applied, including non-empty deposit history. Unresolved ECOM and notification contracts are not silently added.

OpenAPI 3.1 · JSONBaseline schemas plus approved deposit status history/currency, currency-key semantics and P2P form-URL, payment-detail and status-correction changes, with a dated documentation revision.OpenAPI 3.1 · YAMLThe same data as the JSON contract.Postman collection11 entries: preserved profile templates plus owner-provided ECOM H2H/H2C examples; separate credentials and placeholder card data.Postman environmentEmpty secrets; fill only in your private environment.Verification notesDated observations and pending decisions, separate from schema constraints.

Download package manifest · JSON ↓ — revision, file sizes and SHA-256 checksums.

14 files in total · No credentials · No payment execution

[02]

Download dictionaries

Choose only the reference you need. Each individual dictionary keeps the same version metadata and dictionaries.<name> path as the combined file, but contains no unrelated dictionary. Descriptions, scope and review caveats are retained.

Errors · JSONFormat v2: one record per error in items, ID-only groups, shared response fields and scoped handling; not an exhaustive mapping.Currencies · JSONCurrency reference identifiers; availability depends on the assigned profile.Additional fields · JSONField catalog, item structure, terminal-specific requiredness and privacy guidance.Order statuses · JSONFlow-specific finality: P2P Failed can be corrected to Success on the same order; payout classification is unchanged.Payment history · JSONHistory fields, partial code mappings, unknown-code policy and UTC guidance.Telecom operators · JSONOperator names, enum values and profile scope.Bank scope catalogIncomplete scope reference; not a closed bank enum.

Need the combined file?

Combined reference dictionariesAll six dictionaries at the existing URL. businessErrors uses formatVersion 2 with one items list; bank scopes remain separate.

The combined download remains available. The businessErrors dictionary now uses formatVersion 2: read each scenario from items; groups contain IDs, not duplicate payloads. Update consumers of the former createPayloadExamples and depositCurrencyClarification branches. Bank scopes were already separate and remain in banks.json.

Read the reference dictionaries →

[03]

Use the correct profile

Import the collection and environment into your own workspace.
Fill only the credentials for the explicitly assigned test profiles.
Choose the intended request; replace the merchant ID for each create.
Confirm the required fields and use approved payment fixtures.
After uncertainty, retain the original ID and resolve its status before retrying.

No automatically executable Postman test scripts or browser-side request controls are included.

Need the required fields, currencies or limits for your pipeline?

Confirm your profile with Yegor ↗