Strict Send Payment Paths  [Go SDK]

The DigitalBits Network allows payments to be made across assets through path payments. A path payment specifies a series of assets to route a payment through, from source asset (the asset debited from the payer) to destination asset (the asset credited to the payee).

A Path Payment Strict Send allows a user to specify the amount of the asset to send. The amount received will vary based on offers in the order books.

A path payment strict send search is specified using:

  • The destination account id or destination assets.
  • The source asset.
  • The source amount.

As part of the search, frontier will load a list of assets available to the source account id or use the assets passed in the request and will find any payment paths from those source assets to the desired destination asset. The source’s amount parameter will be used to determine if a given path can satisfy a payment of the desired amount.



name notes description example
?source_amount string The amount, denominated in the source asset, that any returned path should be able to satisfy 10.1
?source_asset_type string The type of the source asset credit_alphanum4
?source_asset_code string, required if source_asset_type is not native, string The source asset code, if source_asset_type is not “native” USD
?source_asset_issuer string, required if source_asset_type is not native, string The issuer for the source asset, if source_asset_type is not “native” GAEDTJ4PPEFVW5XV2S7LUXBEHNQMX5Q2GM562RJGOQG7GVCE5H3HIB4V
?destination_account string optional The destination account that any returned path should use GAEDTJ4PPEFVW5XV2S7LUXBEHNQMX5Q2GM562RJGOQG7GVCE5H3HIB4V
?destination_assets string optional A comma separated list of assets. Any returned path must use an asset included in this list USD:GAEDTJ4PPEFVW5XV2S7LUXBEHNQMX5Q2GM562RJGOQG7GVCE5H3HIB4V,native

The endpoint will not allow requests which provide both a destination_account and destination_assets parameter. All requests must provide one or the other. The assets in destination_assets are expected to be encoded using the following format:

XDB should be represented as "native". Issued assets should be represented as "Code:IssuerAccountID". "Code" must consist of alphanumeric ASCII characters.

curl Example Request

curl ""

JavaScript Example Request

var DigitalBitsSdk = require('xdb-digitalbits-sdk');
var server = new DigitalBitsSdk.Server('');

var source_asset = new DigitalBitsSdk.Asset('USD', 'GB4RZUSF3HZGCAKB3VBM2S7QOHHC5KTV3LLZXGBYR5ZO4B26CKHFZTSZ');
var destination_asset = new DigitalBitsSdk.Asset('EUR', 'GDCIQQY2UKVNLLWGIX74DMTEAFCMQKAKYUWPBO7PLTHIHRKSFZN7V2FC');
var source_amount = "2";

server.strictSendPaths(source_asset, source_amount, [destination_asset])
  .then(function (pathResult) {
  .catch(function (err) {


This endpoint responds with a page of path resources. See path resource for reference.

Example Response

    "source_asset_type": "credit_alphanum4",
    "source_asset_code": "USD",
    "source_amount": "2.0000000",
    "destination_asset_type": "credit_alphanum4",
    "destination_asset_code": "EUR",
    "destination_amount": "2.0000000",
    "path": [
        "asset_type": "credit_alphanum4",
        "asset_code": "UAH",

Possible Errors

  • The standard errors.
  • not_found: A not_found error will be returned if no paths could be found to fulfill this payment request

Edit this doc in GitHub


Stay up to date on the latest happenings at DigitalBits. Get the latest news.