Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product tour
  • Pricing

Solutions

  • Utility estimation
  • Context assembly
  • Market intelligence

Suppliers

  • Sell your data
  • Start onboarding
  • Programmatic Data License

Community

  • Public index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/Aurpay/Cross-border e-commerce crypto checkout exhaust
A

Cross-border e-commerce crypto checkout exhaust

AURPAYManage supplier listing

Cross-border e-commerce crypto checkout exhaust: per-order records of consumers in Latin America and Southeast Asia paying with stablecoins, Bitcoin and Lightning at merchant checkouts — payment completion versus abandonment, chain and asset used, order size in local currency, checkout country, and settlement timing. The byproduct is a merchant-level view of which emerging-market consumers actually hold spendable dollar-denominated crypto and what they buy with it.

Open buyer room →
Aurpay/Cross-border e-commerce crypto checkout exhaust
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Aurpay and files the sample in your catalog — private to you.

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Payment Services
Instruments
cryptoequitiesfx
Categories
Alternative
Sentiment
Regions
USLatin AmericaOther
Sample tickers
SHOPPYPLCOINNUMELI
Dataset card
Type
not stated
Format
Tabular / event-log (per-order payment records with chain, asset, country, amount and settlement-status fields; format inferred from the gateway and plugin model)
Volume
Est. 10^5-10^7 order and payment-event rows cumulatively, each carrying chain, asset, country, value and settlement-status fields — gigabytes (inferred from gateway order throughput since launch; no volume figure published).
Users
N/A as a platform user base; the proxy is paying consumers, est. 10^4-10^5 unique crypto payers across served merchant stores cumulatively (inferred from a 9-person gateway operation; no count published).
History
5 years
Update frequency
not stated
Growth
Active but early (recently created corporate profile, a 9-person team and a current-cycle 2026 playbook and regional guide series)
Launched
~2021-2023 (corporate profile created in that window and the product is a current-generation non-custodial gateway; no launch year stated on the page)
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

Aurpay has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling