Accept agreement

curl --request POST \
  --url https://api.etherfuse.com/ramp/agreements/customer-agreement \
  --header 'Content-Type: application/json' \
  --data '
{
  "presignedUrl": "https://api.sand.etherfuse.com/ramp/agreements/customer-agreement?...&signature=..."
}
'

{
  "accepted_ip": "201.140.10.20",
  "accepted_timestamp": "2026-05-01T15:00:00Z",
  "agreement_version": "1.0",
  "document_reference": "https://docs.etherfuse.com/agreements/v1.0.pdf"
}

Agreements

Accept agreement

Records the user’s acceptance of the Customer Agreement, which governs the use of Etherfuse’s on/off ramp services.

Authentication: the presigned URL is the authentication mechanism for the end user; this endpoint must be called by or on behalf of the user who will be bound by this agreement.

Legal effect: by calling this endpoint with a valid presigned URL, the user agrees to the terms governing fiat-to-crypto and crypto-to-fiat transactions, including fees, settlement times, and liability provisions.

Optional customer info: when using programmatic KYC, you may omit the customerInfo field since identity data was already submitted via the KYC endpoints.

POST

ramp

agreements

customer-agreement

Accept agreement

curl --request POST \
  --url https://api.etherfuse.com/ramp/agreements/customer-agreement \
  --header 'Content-Type: application/json' \
  --data '
{
  "presignedUrl": "https://api.sand.etherfuse.com/ramp/agreements/customer-agreement?...&signature=..."
}
'

{
  "accepted_ip": "201.140.10.20",
  "accepted_timestamp": "2026-05-01T15:00:00Z",
  "agreement_version": "1.0",
  "document_reference": "https://docs.etherfuse.com/agreements/v1.0.pdf"
}

Body

application/json

presignedUrl

string

required

customerInfo

object

Show child attributes

Response

Agreement accepted

accepted_timestamp

string<date-time>

required

agreement_version

string

required

accepted_ip

string | null

document_reference

string | null

location

object

Show child attributes

Accept terms Create bank account (presigned)

⌘I