How Integration Works

Every API call is made as a verified Skyline Digital customer, using that customer's own API key. There are two ways to use this:

• You are the Skyline customer. Your organisation is verified once on the Skyline platform, and your systems use the API to do what you would otherwise do in the platform: manage receivers, bank accounts and wallets, and create, submit and track transactions.
• You are a platform whose users are Skyline customers. Each of your end customers onboards with Skyline directly and completes verification there. They then create an API key on the Skyline platform and enter it into your platform. Your platform calls the API with that key and acts as that customer. Skyline does not issue platform-level credentials that act for many customers, and there is no API-driven onboarding.

In both cases the people and businesses you pay are registered as receivers under the customer's account.

The Integration Lifecycle

1. Account setup -- The customer registers on the Skyline platform and completes KYC or KYB there. Verification is not part of the API. See Account Setup.
2. API credentials -- The customer creates an API key on the platform. Your integration exchanges it for tokens. See Authentication and API Keys.
3. Setup -- Register the receivers you will pay, and the bank accounts and wallets that funds move between. See Setup.
4. Transactions -- Create a transaction, submit it, accept the quote and track its status until it settles. See Transactions.
5. Payables -- Optionally, upload invoices and pay them in batches. See Payables.

Transaction Flow Overview

At a high level, every transaction follows the same shape:

1. Choose a receiver and the bank account or wallet the funds go to. Learn more in the Receivers guide.
2. Create the transaction with the amount, the asset you send and the asset the receiver gets.
3. Submit it to obtain a quote with the rate and fees. Quotes are valid for a short window.
4. Accept the quote to lock the rate and start execution.
5. Track the status by polling the transaction until it reaches a final state. The API does not send webhooks.

Each transaction type has its own guide:

• Crypto-to-Fiat -- Convert stablecoins to fiat and send to a bank account
• On-Ramp -- Convert fiat to crypto via bank transfer
• Crypto-to-Crypto -- Transfer between digital assets

What's Next

• Getting Started -- Base URL, environments, authentication and error handling