AurasPay
AURASPAY · PRE-SEED INVESTOR DECK · 2026

Stablecoin infrastructure
for merchants, wallets and AI agents.

AurasPay brings merchant payments, a self-custody wallet, wallet connectivity and permissioned AI-payment interfaces into one operating ecosystem, with white-label deployments activated separately for enterprises.

Pre-Seed · Target raise: $1M · Target pre-money valuation: $7M

Explore the platform↗Investor relations
Actual evidence
→
Management forecast
01 · Ecosystem problem

Stablecoin transactions need connected payment workflows.

A wallet address alone does not connect the payment to an order, invoice or reconciliation workflow. AurasPay focuses on those operational needs across merchants, developers and enterprises.

What breaks todayWallet address ≠ merchant payments operation
01

Merchants need orders, invoices, status and reconciliation—not only a wallet address.

02

Developers and AI agents need wallet connections, payment requests, bounded permissions and verified outcomes.

03

Enterprises need a branded deployment without rebuilding each payment component.

02 · Solution + commercial wedge

A connected operating layer around the payment.

AurasPay combines non-custodial merchant acceptance, wallet experience, wallet connectivity and permissioned AI interfaces. Merchant payments remain the first commercial wedge; enterprise white label is activated separately.

01CheckoutLink · QR · Plugin · POS · API
→
02Direct settlementBlockchain → merchant wallet
→
03AurasPay custodyNone
01

The merchant controls the receiving destination.

02

The user or external wallet keeps final approval authority.

03

AurasPay coordinates the request, permissions, status verification and integration surfaces.

03 · Products by audience

What AurasPay offers. Four audiences, one infrastructure.

A complete catalogue of wallet experiences, merchant solutions, enterprise offers and developer tools. Each entry shows its purpose and current availability.

Individuals2wallet experiencesBusiness8products & solutionsEnterprise4enterprise offeringsDevelopers5tools & integrations

Counts describe offers for each audience. Shared APIs, plugins and Agent Checkout appear in both relevant categories; the category counts are not added together as unique products.

Individuals

One self-custody wallet, on mobile and web.

2 wallet experiences

  1. Android self-custody wallet to hold, send, receive and approve supported assets. iOS is coming soon.

    Revenue stream
    Wallet services, not a wallet subscriptionSwaps, buy-crypto and eSIM can generate service commissions. Mobile and web share the same revenue pool.

  2. Review balances and prepare sends or swaps in the browser; final signing stays in the mobile wallet.

    Revenue stream
    Wallet services, not a wallet subscriptionSwaps, buy-crypto and eSIM can generate service commissions. Mobile and web share the same revenue pool.

Business

Accept, track and integrate merchant payments.

8 products & solutions

  1. Share a hosted checkout by message, email or invoice and track its payment status.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  2. Present a scannable payment request at a counter, event or on an invoice.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  3. Enter an amount and run in-person stablecoin checkout from a merchant screen.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  4. Issue payment requests with invoice context and follow payment confirmation.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  5. Connect existing stores and business platforms to hosted checkout, with server-side payment verification.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  6. Manage payment requests, transaction states, receiving destinations and integrations.

    Revenue stream
    Merchant payment feesIncluded merchant operations and analytics. No standalone subscription is forecast.

  7. Create and retrieve payment requests, verify status and integrate signed webhooks.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  8. AI agents resolve, prepare and verify existing Base USDC payment links using x402 v2 and external-wallet signing.

    Revenue stream
    Merchant payment feesEligible Agent Checkout payments use the merchant fee. Count their TPV once, within Payments.

Available integrations: WooCommerce, WordPress, Magento, Shopware, OpenCart, PrestaShop, CS-Cart, Odoo and WHMCS. Shopify is coming soon.

Enterprise

Three review-led offers and one sandbox-first proposition.

4 enterprise offerings

  1. White Label · Full Platform

    Available · activation required

    Branded hosted website, merchant workspace and checkout, with API access after activation.

    Revenue stream
    Setup + monthly software OR revenue share$13,999 setup + $999/month, or $14,999 setup + 0.29% share with no monthly fee. These are alternative plans.

  2. White Label API

    Available · activation required

    Payment infrastructure for the customer's own interface; hosted website and merchant dashboard are not included.

    Revenue stream
    API setup + monthly maintenance OR revenue share$7,999 setup + $799/month, or $8,999 setup + 0.29% share with no monthly fee. Separate from the included merchant API.

  3. Pay by Bank White Label

    Sandbox-first · not live

    Separate bank-payment proposition in development; sandbox first, with regulated access required for production.

    Revenue stream
    Potential contracted technical-service feesProposed setup, platform and usage terms require agreement and regulated access. Sandbox only; excluded from quantified revenue.

  4. Split Payment Contracts

    Available · activation required

    Standalone managed contracts route principal and an approved fee to two destinations, subject to project review.

    Revenue stream
    Project delivery + contracted ongoing serviceQuote setup, maintenance and any AurasPay fee separately. A client’s configured fee is not automatically AurasPay revenue; not quantified.

Developers

Build payment, wallet and AI workflows.

5 tools & integrations

  1. Connect existing stores and business platforms to hosted checkout, with server-side payment verification.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  2. Create and retrieve payment requests, verify status and integrate signed webhooks.

    Revenue stream
    Merchant payment fees1% of eligible completed payments. Included tools are not charged again.

  3. AI agents resolve, prepare and verify existing Base USDC payment links using x402 v2 and external-wallet signing.

    Revenue stream
    Merchant payment feesEligible Agent Checkout payments use the merchant fee. Count their TPV once, within Payments.

  4. Merchant MCP

    Live · scoped access

    Connect AI clients to merchant operations with OAuth permissions; enabled tools follow merchant-approved scopes.

    Revenue stream
    Merchant usage and separately scoped enterprise accessSupports payment adoption. No public standalone tariff is established; no extra MCP fee is added to the forecast.

  5. Auras Connect

    Live · scoped access

    Wallet connection infrastructure and developer projects; final approval remains with the user's wallet.

    Revenue stream
    Potential enterprise connectivity / usage plansConnectivity and distribution today. No published standalone price or volume driver; excluded until commercial terms are set.
Supporting resource: Contracts & Networks registry

Official product pages · reviewed 2 October 2026

04 · Shared architecture

Payment requests, wallet connections and verified status.

Documented connections link merchant workflows, wallet sessions, scoped permissions and payment-status verification.

Shared workflow elements
Payment requestsWallet connectivityPermissionsPayment-status verificationIntegrations

Verified product relationships

Payments↔Agentic

Existing payment request + authoritative status

S11
Payments↔Merchant MCP

Permission-scoped merchant operations

S12
Auras Wallet↔Auras Connect

Compatible wallet session; approval stays in wallet

S17 · S19
Payments↔White Label

Contracted branded checkout, APIs and webhooks

S13
01

Payments ↔ Agentic: existing payment requests and authoritative payment status.

02

Payments ↔ Merchant MCP: merchant payment operations through scoped tools.

03

Wallet ↔ Connect and Payments ↔ White Label: compatible wallet sessions and contracted branded payment workflows.

05 · AI + MCP

AI agents can participate on both sides of commerce.

Merchant MCP supports permission-scoped merchant operations. Agentic Payments supports an eligible buyer-side path while actual authorisation remains with a human or bounded external-wallet approval.

Merchant side · Merchant MCP
Allowed toolsMerchant-approved permissionsOrders and payments

Documented example

“Prepare a payment link, then let me review it before creation.”
S12 · Live remote MCP · supported writes require separate review
Buyer side · Agentic Payments
Payment requestsPayment request, proof and verificationPayment-status verification

Documented example

Request → external-wallet signature → submit proof → verified status
S11 · Eligible Base USDC route · external-wallet signing
Human / external-wallet approval boundaryFinal approval remains with a human or bounded external wallet
01

A payment request states the merchant, amount, network and asset.

02

The external wallet signs; AurasPay never receives private keys.

03

Submitted proof is not completion until the authoritative payment record verifies it.

06 · Wallet + Connect

Wallet experience and connectivity.

Auras Wallet is the user-facing self-custody wallet. Auras Connect is the developer layer for short-lived, origin-bound wallet sessions.

Auras Wallet official product preview
User product

Auras Wallet

Wallet: live mobile, web and multi-chain user experience.

S19 ↗
Auras Connect official product preview
Developer layer

Auras Connect

Connect: production and sandbox setup across supported network families.

S17 · S18 ↗
Human / external-wallet approval boundaryThe wallet retains final authority; payment completion comes from the canonical payment API or verified webhook.
07 · Enterprise white label

Enterprise deployment under the customer’s brand.

Branded merchant workspace, checkout, APIs and webhooks, with scope and commercial terms agreed before implementation and production activation.

Contracted output
  • Branded merchant workspace
  • Branded checkout
  • Payments API + webhooks
  • Contracted modules only
Activation path
  1. Scope + proposal
  2. Contract + security review
  3. Implementation + readiness
  4. Production activation
Commercial termsFull Platform or White Label API

Published setup and monthly fees follow the selected plan. Scope, invoice and activation requirements are confirmed before launch.

01

Target buyer: enterprises that need branded stablecoin merchant acceptance.

02

Scope, modules, implementation, security and production readiness are agreed before activation.

03

Setup, subscription/licence and add-ons are priced by commercial proposal.

08 · Product adoption

Early platform adoption. Commercial activation is the next milestone.

AurasPay is pre-revenue. The figures below are management-reported Payments platform counts, not paying-merchant counts or completed payment volume.

ACTUAL · AS SUPPLIED
2,821Registered users
1,639Payment links created
192Product-active users
Evidence supplied192Product-active users
Next investable proofRecurring TPVPaying · retained merchants
01

2,821 registered users, 1,639 payment links created and 192 product-active users.

02

These are different platform measures, not a conversion funnel; reporting period and test exclusion are unverified.

03

Next commercial milestone: paying merchants with repeat completed payments. Agentic payment volume is included within Payments volume.

09 · Why now + market

Two buyers; one documented bottom-up method.

Merchants buy payment acceptance. Enterprises buy infrastructure and deployment. Developers and wallet users can extend reach, but their market sizes are not added to accessible revenue.

MARKET CONTEXT · NOT TAM
01

Merchant acceptance buyer

Merchant SAM: target merchants × eligible payment volume × adoption × actual fee.

02

Infrastructure buyer

Enterprise SAM: qualified institutions × expected contracted software value.

$5.7T2024 adjusted stablecoin volumeS1 ↗
$274BStablecoin supply · Dec 2025S3 ↗

Bottom-up method

01

Merchant SAM: target merchants × eligible payment volume × adoption × actual fee.

02

Enterprise SAM: qualified institutions × expected contracted software value.

03

Global stablecoin activity remains context, not TAM, and the two revenue pools stay separate.

10 · Revenue model

Each service has a revenue role. Each forecast has a driver.

Merchant payment fees, enterprise setup and software subscriptions, plus wallet service commissions. Prices, management-supplied rates and modelled volumes are identified separately; this is forecast revenue, not current income.

Commercial stage
Pre-revenue

Focus: activating paying merchants and repeat completed payments.

Revenue sources
Payment fees1%
Swap commission0.79%
Buy-crypto commission1%
eSIM commission3%
01

Payments: 1% of eligible completed volume. Links, QR, POS, invoices, plugins and the merchant API do not each create an extra fee.

02

White Label: one-time setup plus monthly subscription, or an alternative revenue-share plan; never both on the same contract.

03

Wallet services: swaps 0.79%, buy crypto 1% and eSIM 3% per management. Only eligible AurasPay commissions are included; other services need separate terms.

Published pricing

Merchant payments1%

Of eligible completed payments. No separate subscription, setup, API or plugin charge.

S24
White Label · Full Platform$13,999

Subscription plan: $999 / month

Revenue-share alternative

$14,999 + 0.29%

S13
White Label API$7,999

Subscription plan: $799 / month

Revenue-share alternative

$8,999 + 0.29%

S13

White Label’s 0.29% share is inside the client’s total commission, not added on top. Subscription clients do not also pay the share. Network and provider charges are not AurasPay income.

FORECAST · NOT ACTUAL RESULTS

Forecast by revenue stream

Modelled revenue, not actual results. Operating volumes come from the approved 2026–2030 planning workbook; White Label prices were refreshed on 6 October 2026. Provider rates below were supplied by management.

All forecast White Label deployments use the selected subscription plan. This is a scenario assumption, not a contracted mix. Revenue-share TPV is not forecast without a separate volume plan.

Revenue composition by year
$10.9k
2026 H2E
$203.6k
2027E
$949.1k
2028E
$3.54M
2029E
$10.82M
2030E
Payment feesWhite Label setupWhite Label subscriptionBuy-crypto + swaps · provider-dependent + eSIM
Revenue in USD thousands
Revenue stream2026 H2E2027E2028E2029E2030E
Payment fees · 1%9.0139.5630.02,232.06,417.0
White Label setup · White Label · Full Platform—14.042.084.0140.0
White Label subscription · White Label · Full Platform—6.030.083.9179.8
Payments + White Label9.0159.5702.02,399.96,736.8
Buy-crypto commission · 1%1.427.9157.5714.22,566.8
Swap commission · 0.79%0.613.289.6423.21,520.8
eSIM commission · 3%Sales × 3%3.0Sales × 3%Sales × 3%Sales × 3%
Quantified provider-service commissions1.944.1247.11,137.44,087.6
Quantified forecast total10.9203.6949.13,537.310,824.4

Management’s 2027 eSIM sales target is $100,000, generating $3,000 at 3%. Other years have no sales-volume estimate yet; they are not treated as zero. The total includes only quantified streams in each period.

Volume assumptions and calculation
Volume assumptions and calculation2026 H2E2027E2028E2029E2030E
Average active merchants301555001,2002,325
Monthly TPV per active merchant (USD)5,0007,50010,50015,50023,000
New White Label deployments013610
Average live White Label deployments0.00.52.57.015.0
Referred buy-crypto volume / payment TPV15%20%25%32%40%
Swap volume / payment TPV8%12%18%24%30%
eSIM · sales (USD)—100,000———

Payment revenue = average merchants × monthly TPV × period months × 1%. Setup = new deployments × plan setup price. Subscription = average live deployments × months × monthly price. Buy/swap = eligible service volume × 1% / 0.79%, respectively.

2026E covers H2 only (6 months), retained from the original plan; it is not October actuals or a rebased forecast. New deployments are assumed to start evenly through each period, with no White Label churn. Setup is recognised at delivery; recurring fees over the service period.

Buy-crypto retains the workbook’s referred-volume assumption as a planning proxy, not observed wallet sales. Swap volume is also linked to payment TPV as a proxy. No off-ramp commission is forecast separately. Provider commissions represent AurasPay’s share, not gross provider charges.

AurasPay Investor Business Model 2026–2030 · Assumptions B5:F34 · Operating Drivers B13:F35 · Revenue Model B8:F26. Service rates and eSIM target: management, 6 October 2026.

Other revenue opportunities · outside the total

Retained planning estimates from the earlier workbook. Card activation, separate enterprise scope, commercial terms and customer separation must be established before these amounts enter the quantified forecast. They are not contracted revenue, and are not summed with White Label.

Revenue in USD thousands
Revenue stream2026 H2E2027E2028E2029E2030E
Card spend commission · assumed 0.35%—8.753.6211.6690.9
Active-card commission · assumed $1/month—4.525.593.0282.0
Card activation · assumed $2/card—1.55.818.148.9
Separate enterprise software licences40.0132.0350.0728.01,440.0
Separately scoped enterprise API add-ons—10.242.0127.4324.0

Legacy licence assumptions: 2/6/14/26/45 clients at $20k/$22k/$25k/$28k/$32k per year. API adoption: 0/17/25/35/45% at $10k/$10k/$12k/$14k/$16k annually. These are not public prices for Connect, MCP or Split Contracts, nor an extra charge on the included merchant API.

Average active cards: 0/375/2,125/7,750/23,500; monthly spend: $0/$550/$600/$650/$700; new activations: 0/750/2,885/9,025/24,440. Planning assumptions, not activated cards.

This update forecasts revenue only. Prior gross-margin, EBITDA and financing assumptions have not been recalculated for this service mix and are not presented as outputs of this forecast.

11 · Go-to-market

One six-month priority, with two controlled expansion paths.

Priority: founder-led activation of WHMCS hosting and digital-service merchants that already see stablecoin demand. In parallel, pursue one qualified white-label pilot and one external developer or AI integration—not six independent campaigns.

01Qualified merchantICP fit · stablecoin demand
02DemoWorkflow and settlement review
03ActivationIntegration · wallet · verification
04First completed paymentOrder matched · status verified
05First fee collectedRecognised transaction revenue
06Repeat usageRetained merchant · repeat payments
01

Merchant wedge: direct outreach, plugins and hands-on activation through repeat completed payments.

02

White-label hypothesis: fintech or payment enterprise needing branded merchant acceptance; track stage from proposal to paying production.

03

Developer/AI acquisition: documentation, direct integration outreach and one measurable external implementation.

12 · Named competition

Compete by buyer and workflow—not product count.

Diligence covers four categories: payment acceptance, wallet connection and experience, agent payments, and enterprise white label. The named matrix below compares the merchant-payment category on verifiable criteria.

Competition categoriesPayment acceptanceWallet experience + connectionAgent paymentsEnterprise / white label
CompetitorSettlementMerchant workflowTotal priceNeeded services / dependencies
Direct wallet transferDirect to merchant walletManual address / manual matchingNetwork fee + internal operationsManual status, reconciliation and support
AurasPayDirect to merchant walletWoo, WHMCS, CS-Cart + more1% core merchant fee (management pricing)Networks; third parties for cards, ramps, swaps and regulated services
BitPayS5 · S6Bank or supported crypto wallet; generally dailyShopify, WooCommerce, Magento2% + $0.25 → 1% + $0.25 by monthly volumeKYC, compliance approval, supported settlement rails
CoinbaseS7 · S8USD / USDC; bank sweeps for eligible partnersAPI-first; Business checkout / links1% Commerce; enterprise terms may varyCoinbase onboarding, supported networks and payout rails
Triple-AS9 · S10Bank or crypto; next-day bank settlement statedWooCommerce, OpenCart, Shopify / PinwheelCustom / not publicly quotedLicensed-entity coverage, KYC/AML and banking partners
13 · Why AurasPay

Merchant payments with reusable wallet and AI interfaces.

Integration time and operating cost will be measured against existing alternatives as customers activate. These are planned measures, not current performance claims.

Proven today

Available today: non-custodial merchant acceptance, scoped merchant tools, wallet experience and origin-bound connectivity.

Enterprise option: branded merchant workspace, checkout, APIs and webhooks after contracted activation.

Prove next

Next: measure integration time, operating cost and repeat merchant usage.

Integration time and operating cost will be measured against existing alternatives as customers activate. These are planned measures, not current performance claims.

14 · Leadership

AurasPay’s leadership team.

Founder and executive leadership alongside technical leadership.

Mazen Z. H. Alshareef
Founder & CEO

Mazen Z. H. Alshareef

Fahd Siyam
Chief Technology Officer

Fahd Siyam

15 · 24-month execution plan

From product adoption to recurring commercial use.

The proposed post-round plan prioritises merchant activation, enterprise deployments and measurable product usage. Milestones are targets, subject to funding and execution.

Target
0–6 months

0–6 months: paying merchants with repeat completed payments and an instrumented funnel.

6–12 months

6–12 months: a paid, activated white-label client and one working external Agentic integration.

12–18 months

12–18 months: measured external use of Merchant MCP and Auras Connect.

18–24 months

18–24 months: documented security and operational validation plus evidence for the next financing decision.

16 · Pre-Seed round

Raising $1M to commercialise AurasPay’s stablecoin infrastructure.

Target pre-money valuation: $7M. Implied post-money valuation at full raise: $8M. New-investor ownership at full raise: 12.5%. This is priced-equity arithmetic before any prior instruments or employee option-pool adjustment.

PRE-SEED · 2026$1M
Pre-money$7M
Post-money$8M
Equity12.5%

Use of funds

Founder-led sales & merchant activation
Product · infrastructure · security
Priority hires
Legal · compliance · provider work
Operating reserve

Current operating runway · management reported

10 monthsPost-round runway depends on the agreed operating budget and timing of the raise.
17 · Risks + regulation

Commercial execution, provider dependencies and regulatory boundaries.

AurasPay provides non-custodial software and DLT infrastructure. Corporate registrations are not banking, payment, custody, exchange or VASP licences.

01

Commercial — pre-revenue; prioritise one customer segment, merchant activation and repeat payments.

02

Provider — cards, ramps and swaps depend on third parties and their availability and terms.

03

Regulatory — specialised services depend on provider approval, eligibility and jurisdiction.

04

Financial — manage hiring, infrastructure and operating reserves against the monthly cash budget.

APPENDIX

Appendix · product breadth without diluting the core pitch

Secondary detail is retained for diligence, but removed from the main decision path.

Products & APIs+
  • Self-custody wallet and Web Wallet
  • Payments API, links, QR, POS, invoices and signed webhooks
  • Live Merchant MCP: permission-scoped access; supported writes require review (S12)
  • Live Agentic Commerce API and eligible Base USDC x402 checkout; external-wallet signing (S11)
  • Auras Connect and white-label enterprise workspace; activation requires review (S13)
Commerce integrations+
  • WooCommerce / WordPress
  • Magento / Shopware
  • OpenCart / PrestaShop
  • WHMCS / CS-Cart / Odoo
  • Shopify — coming soon
Conditional & planned services+
  • Standalone split-contract service: project review before deployment (S15)
  • Pay by Bank: separate sandbox-first proposal, not live (S14)
  • Third-party swap, on/off-ramp and cards depend on providers
  • Gift cards, top-ups and eSIM depend on availability
Financial model · management assumptions+
  • 2026 H2–2030 revenue is broken down by stream in the Revenue Model section, with current White Label pricing and management-supplied wallet commissions.
  • Volumes are retained from the approved planning workbook, not actual cohorts. eSIM has a $100,000 sales target in 2027 only; other years remain unquantified.
  • Cards and separate enterprise/API opportunities are outside the total. Prior gross margin and EBITDA have not been recalculated for the revised revenue mix.
  • Current operating runway: 10 months, management reported; post-round runway depends on the agreed budget
Sources & methodology+
  1. S1
    Visa Economic Empowerment Institute — Update on key digital-asset technologies ↗2025 · 2024 adjusted stablecoin transaction volume after Visa / Allium filters remove likely bot and high-frequency distortions.
  2. S2
    Visa Onchain Analytics — transaction methodology ↗Accessed Aug 2026 · Adjusted-volume methodology and filter definitions; market context only, not AurasPay TAM.
  3. S3
    Visa Consulting & Analytics — Stablecoin strategy ↗2026 · Stablecoin supply reached approximately $274B in December 2025.
  4. S5
    BitPay — pricing ↗Accessed Aug 2026 · Public processing tiers: 2% + $0.25 below $500K monthly, 1.5% + $0.25 at $500K–$999,999, and 1% + $0.25 at $1M+.
  5. S6
    BitPay — terms and settlement ↗Accessed Aug 2026 · Merchant account ledger and daily settlement to bank account or supported wallet; restrictions and verification apply.
  6. S7
    Coinbase Developer Platform — Payment Acceptance ↗Accessed Aug 2026 · Enterprise stablecoin checkout; buyers may use self-custody wallets, while fiat settlement uses Coinbase account and payout rails.
  7. S8
    Coinbase Developer Platform — pricing ↗Accessed Aug 2026 · Commerce public price is 1% per transaction; custom enterprise pricing may apply.
  8. S9
    Triple-A — ecommerce and coverage ↗Accessed Aug 2026 · API, payment links, next-day settlement and stated customer coverage across 140+ countries; onboarding and jurisdiction rules apply.
  9. S10
    Triple-A — ecommerce plugins ↗Accessed Aug 2026 · Public support documentation lists WooCommerce, OpenCart and Shopify with Pinwheel.
  10. S11
    AurasPay — Agentic Commerce and Agent Checkout ↗Accessed Sep 2026 · Official product page describes a live v0.3 commerce API and an eligible Base USDC x402 route with external-wallet signing. Product availability is not evidence of completed TPV or revenue.
  11. S12
    AurasPay — Merchant MCP ↗Accessed Sep 2026 · Official product page describes live, OAuth-scoped merchant access with up to 41 tools depending on enabled features and permissions; supported writes require separate approval.
  12. S13
    AurasPay — White-label crypto payments and pricing ↗Reviewed 6 Oct 2026 · Full Platform subscription: $13,999 setup plus $999/month; API subscription: $7,999 plus $799/month. Alternative revenue-share plans: setup $14,999/$8,999 and default AurasPay share 0.29%, with no monthly subscription. Production activation is gated; subscription and share are alternatives.
  13. S14
    AurasPay — Pay by Bank ↗Accessed Sep 2026 · Official page labels Pay by Bank sandbox-first and not live. Production requires approved regulated-party access and bank connectivity.
  14. S15
    AurasPay — Split payment contracts ↗Accessed Sep 2026 · Standalone managed split-contract requests are subject to project, governance, asset and security review; an enquiry is not a deployed contract.
  15. S16
    AurasPay — Business payments ↗Accessed Sep 2026 · Official product page describes live payment links, QR, POS, invoices, plugins, API and a 1% platform fee; merchant funds settle to the merchant wallet.
  16. S17
    Auras Connect — product overview ↗Accessed Sep 2026 · Official product page describes an available non-custodial wallet-connectivity layer with short-lived, origin-bound sessions across supported network families.
  17. S18
    Auras Connect — developer documentation ↗Accessed Sep 2026 · Official documentation defines production and sandbox setup, server-only keys, origin isolation and canonical payment verification requirements.
  18. S19
    AurasPay — Self-custody wallet ↗Accessed Sep 2026 · Official product page describes live mobile, web and multi-chain self-custody wallet surfaces; final authorisation remains with the user.
  19. S20
    AurasPay — platform overview ↗Reviewed 2 Oct 2026 · Official top-level product map for individuals, businesses, developers and enterprise customers. Audience counts include shared offers, with availability stated per offer.
  20. S21
    AurasPay — Commerce plugins ↗Reviewed 2 Oct 2026 · Nine integrations listed as available; Shopify is coming soon. Platform version and merchant configuration requirements apply.
  21. S22
    Auras Wallet — product and services ↗Reviewed 2 Oct 2026 · Mobile and web wallet experiences, wallet capabilities and third-party services. Crypto card and IBAN/bank transfers are marked coming soon.
  22. S23
    AurasPay — Developer products ↗Reviewed 2 Oct 2026 · Payment API, Agentic Payments, Merchant MCP and Auras Connect; plugins are also linked. Contracts and networks are a supporting registry, not a separately counted product.
  23. S24
    AurasPay — Merchant pricing ↗Reviewed 6 Oct 2026 · 1% of eligible received payments; included merchant tools have no separate subscription, setup, API or plugin licence charge. White Label and separately scoped services follow their own written terms.