Skip to main content

Transfer API Reference

Version: 2.0.0

The Paysera Transfer API allows you to manage fund transfers between various accounts and payment methods. This API provides functionalities for creating, reserving, revoking, and signing transfers, as well as checking their status and managing related options like single-window transfers.

Base URL​

  • Production: https://wallet.paysera.com/transfer/rest/v1

Authentication​

All Transfer API endpoints require OAuth 2.0 MAC (Message Authentication Code) authentication, or, as an alternative, SSL client certificate authentication.

Authorization Header Format:

Authorization: MAC id="CLIENT_ID", ts="TIMESTAMP", nonce="RANDOM_STRING", mac="MAC_HASH", ext="body_hash=BODY_HASH"

Example:

Authorization: MAC id="a9b8c7d6e5f4g3h2", ts="1234567890", nonce="xyz123abc456def", mac="dGhpcyBpcyBhIHJhbmRvbSBtYWMgaGFzaCB2YWx1ZQ==", ext="body_hash=cmFuZG9tQm9keUhhc2hWYWx1ZQ%3D%3D"

For more details, please refer to the Transfer API Authentication Documentation.

API Features​

Transfers Management​

Create, retrieve, revoke, reserve, and sign fund transfers. Manage currency conversions and password-protected transfers.

Single Window Transfers​

Access functionalities related to single-window transfers, including available countries, payment systems, delivery options, and mandatory fields.

Transfer Lifecycle​

A transfer moves through several states:

  • new - created but not yet visible or processed; automatically deleted if no further action is taken
  • registered - made visible via PUT /transfers/{id}/register
  • signed - authorized via PUT /transfers/{id}/sign
  • done - successfully processed
  • rejected - cancelled via DELETE /transfers/{id}
  • failed - failed during processing (see failure_status)

On creation, set auto_process_to_done: false to step through these states manually, or leave it at the default (true) to let the transfer process automatically when possible. Use PUT /transfers/{id}/reserve to reserve funds for the transfer.

Pagination​

List endpoints (such as GET /transfers) use offset- and cursor-based pagination:

  • limit - Maximum number of results (default: 20)
  • offset - Number of results to skip
  • after / before - Cursor values for paging through frequently-changing result sets

Each list response includes a _metadata object with total, limit, offset, has_next, and has_previous.

Example:

GET /transfers?debit_account_number=EVP1234567&limit=20&offset=20

Note: GET /transfers requires at least one account filter (debit_account_number or credit_account_number).

Rate Limits​

The API implements rate limiting to ensure service stability. If you exceed the rate limit, you will receive a 429 Too Many Requests response.

Contact​

Paysera Support: tech_support@paysera.com Website: https://www.paysera.com