1 of 1

Fund Escrow

Allows users to deposit funds into an existing escrow contract, securing them until the agreed conditions are met.

Allows flexible USDC amounts to be transferred to the escrow contract.

URL: /escrow/fund-escrow

Body params:

contractId: ID (address) that identifies the escrow contract

signer: Address of the user signing the contract transaction

amount: Amount to transfer to the escrow contract

Example:

{
	contractId: "GC3DJY4LLQYJHEONXFDLQVVRCFZQCPFX7VD33KP4P7QSVZY3SJHQBZGV",
	signer: "GBY3PAJY5R3ZIXTYBGFW4URB4RINEXQBC3T4RWDDKJ5TZXQYZUN6A4TP", 
	amount: "500.00"
};

Previous Version:

POST escrow/fund-escrow

Headers

Name

Value

Content-Type

application/json

Body

Name

Type

Description

engagementId

string

The unique identifier linking this escrow to a specific project or transaction.

contractId

string

The unique identifier of the contract.

signer

string | Address

The address authorized to approve the release of funds.

Example of Request Body:

{
  "engagementId": "test",
  "contractId": "GD2SVFOJ...",
  "signer": "SCMXDC..."
}

Possible Responses

{
    "status": "SUCCESS",
    "unsignedTransaction": "AAAAAgAAAABfQAm/gS..."  // XDR Hash Transaction
}

Only Signer

{
  "error": "Only the signer can fund the escrow"
}

Already Funded

{
  "error": "Escrow already funded"
}

Fully Funded

{
  "error": "This escrow is already fully funded"
}

Insufficient Founds

{
  "error": "The signer does not have sufficient funds"
}

Not Found

{
  "error": "Escrow not found"
}

Not Enough Allowance

{
  "error": "Not enough allowance to fund this escrow"
}

{
    "message": "Message",
    "error": "Bad Request",
    "statusCode": 400
}

{
    "statusCode": 429,
    "message": "ThrottlerException: Too Many Requests"
}

What this Endpoint returns?

This endpoint returns the transaction unsigned so that the transaction can be signed by means of a customer wallet.

Fund Escrow

Allows users to deposit funds into an existing escrow contract, securing them until the agreed conditions are met.

Allows flexible USDC amounts to be transferred to the escrow contract.

URL: /escrow/fund-escrow

Body params:

contractId: ID (address) that identifies the escrow contract

signer: Address of the user signing the contract transaction

amount: Amount to transfer to the escrow contract

Example:

{
	contractId: "GC3DJY4LLQYJHEONXFDLQVVRCFZQCPFX7VD33KP4P7QSVZY3SJHQBZGV",
	signer: "GBY3PAJY5R3ZIXTYBGFW4URB4RINEXQBC3T4RWDDKJ5TZXQYZUN6A4TP", 
	amount: "500.00"
};

Previous Version:

POST escrow/fund-escrow

Headers

Name

Value

Content-Type

application/json

Body

Name

Type

Description

engagementId

string

The unique identifier linking this escrow to a specific project or transaction.

contractId

string

The unique identifier of the contract.

signer

string | Address

The address authorized to approve the release of funds.

Example of Request Body:

{
  "engagementId": "test",
  "contractId": "GD2SVFOJ...",
  "signer": "SCMXDC..."
}

Possible Responses

{
    "status": "SUCCESS",
    "unsignedTransaction": "AAAAAgAAAABfQAm/gS..."  // XDR Hash Transaction
}

Only Signer

{
  "error": "Only the signer can fund the escrow"
}

Already Funded

{
  "error": "Escrow already funded"
}

Fully Funded

{
  "error": "This escrow is already fully funded"
}

Insufficient Founds

{
  "error": "The signer does not have sufficient funds"
}

Not Found

{
  "error": "Escrow not found"
}

Not Enough Allowance

{
  "error": "Not enough allowance to fund this escrow"
}

{
    "message": "Message",
    "error": "Bad Request",
    "statusCode": 400
}

{
    "statusCode": 429,
    "message": "ThrottlerException: Too Many Requests"
}

What this Endpoint returns?

This endpoint returns the transaction unsigned so that the transaction can be signed by means of a customer wallet.