Crypto

Use these string values in tenderTypes at the merchant, location, or terminal level. Values are case sensitive. Copy them exactly as shown.

Current crypto tenders

Tender string	Asset	Network	Direction	Availability	Sandbox network notes
usdcBase	USDC	Base	Receive and auto liquidate to fiat	Available now	Uses a public Base test network in Sandbox
usdcSolana	USDC	Solana	Receive and auto liquidate to fiat	Available now	Uses a public Solana test network in Sandbox

Planned additions

Tender string	Asset	Network	Direction	Target window	Notes
ethereum	ETH	Ethereum	Receive and auto liquidate to fiat	Q4 2025	Production rollout follows certification
bitcoin	BTC	Bitcoin	Receive and auto liquidate to fiat	Q4 2025	Production rollout follows certification
bitcoin_Lightning	BTC over Lightning	Lightning Network	Receive and auto liquidate to fiat	Q4 2025	String uses an underscore by design

Where to set tender types

Level	Field	Behavior
Merchant	tenderTypes on the merchant object	Acts as the default for locations created under the merchant
Location	tenderTypes on the location object	Overrides the merchant defaults for that location when provided
Terminal	tenderTypes on the terminal object	Overrides the location settings for that terminal when provided

If a level omits tenderTypes, it inherits from its parent. Passing an empty array clears any override at that level and reverts to the parent defaults.

Example payloads

Create a location that inherits merchant defaults

{
  "name": "Downtown Flagship",
  "address": {
    "address1": "123 Main St",
    "city": "Springfield",
    "region": "MA",
    "country": "US",
    "postalCode": "01109"
  }
}

Create a location that explicitly sets crypto tenders

{
  "name": "Airport Kiosk",
  "address": {
    "address1": "987 Terminal Rd",
    "city": "Springfield",
    "region": "MA",
    "country": "US",
    "postalCode": "01109"
  },
  "tenderTypes": ["usdcBase", "usdcSolana"]
}

Create a terminal that narrows tenders under the same location

{
  "locationId": "loc_bfdc6a7f",
  "tenderTypes": ["usdcBase"]
}

Validation and behavior

Topic	Guidance
Case sensitivity	Values are case sensitive. Use exactly the strings shown in the tables
Combination rules	You can set one or many values in the array. The platform validates that each string is recognized
Settlement behavior	Crypto receipts auto liquidate to the sponsor bank FBO account in fiat according to your program rules
Sandbox behavior	Sandbox uses public test networks. Live network behavior and fees differ in Production
Backward compatibility	New tender strings can be added without a version change. Unknown strings are rejected with a validation error

Deprecations and naming hygiene

Old value	Status	Replacement
usdC_Ethereum	Do not use	Use ethereum when ETH becomes available or use usdcBase for USDC on Base
usdC_Polygon	Do not use	No current replacement in Production. Follow the roadmap and tender tables on this page

If your codebase contains legacy strings, migrate them to the current values shown above.

Related topics

Topic	Where
Environments and Base URLs	Reference Guide
Location Management	Entity Management section
Payment Webhooks and Event Reference	Reference Guide
Download OpenAPI and Postman	Reference Guide