Transaction flow

When making API requests to our system, it is important to include the authorization token in the Authorization header to authenticate your requests. The correct format for including the token is:

Authorization: Bearer ${ACCESS_TOKEN}

For detailed information on obtaining and using access tokens, please refer to the Authentication section of our documentation.

Transactions Flow

In the Skyline Digital API, a single transaction entity encompasses the token amount to be sent and can also contain multiple payments. Each payment must specify a receiver or a bank account as the intended recipient for the transferred funds.

Take the following diagram which identifies the lifetime of a Transaction:

To initiate the Transaction process use the create transaction endpoint:

If a transaction is not flagged as a DRAFT a time-based quote will be issued and should be accepted under 2min time.

Inform the user of the exchange rate and track quote expiration by using the RFQ details under each payment

Upon successfully creating a transaction with the status WAITING_FOR_ACCEPTANCE, the user can proceed to accept the transaction. To do this, specify the transaction id in the following endpoint:

This will allow the user to accept and move forward with the transaction process.

To retrieve the transaction status and details, query the transaction using its ID with the following endpoint.

This will provide you with comprehensive information about the specific transaction, including its current status and associated details.

All user transactions can also be retrieved by calling this endpoint, you will receive an array of transaction objects. This provides a comprehensive overview of the user's transaction history, enabling easy tracking and management of transactions.

Please consult the Transaction API reference for more comprehensive information and explore additional related endpoints.

Last updated