Application and workflow
- Proposed inclusion
- Scheduled basket, offer, merchant-acceptance and payment-handoff application components.
- Excluded or conditional
- Customer funds, wallets, merchant contracts and payment-provider accounts.
SatCart
Give Bitcoin buyers a clear way to put an offer in front of a merchant.
Connect a buyer’s shopping basket with a merchant-ready Bitcoin offer and payment handoff. A focused commerce opportunity for businesses with an existing merchant network or relevant buyer audience.
At a glance
- Best-fit buyer
- Bitcoin payment providers, merchant networks and commerce operators with an existing customer or merchant audience.
- Customer value
- Connect buyer intent with a merchant's own payment route through an organised offer and acceptance journey.
- Transaction options
- Software asset acquisition or a defined licence.
- Included in discussion
- Scheduled basket, offer, merchant-acceptance and payment-handoff application components.
The opportunity
Connect buyer intent with a merchant's own payment route through an organised offer and acceptance journey.
Explore the workflow
See the journey from start to finish.
Follow the key steps from the first input to the final outcome. Request a private demonstration focused on your requirements.
Prepare the offer
Bring the basket details and currency quote into a proposed Bitcoin purchase.
Example journey
A sample basket is used to prepare a currency quote and proposed Bitcoin offer.
Continue with the next step below.
Put the buyer in control
Let the buyer review the offer before sharing it with the merchant.
Example journey
The sample buyer approves the offer before the merchant receives an acceptance link.
Continue with the next step below.
Hand over for payment
Connect an accepted offer to the merchant's chosen payment instructions or checkout route.
Example journey
The accepted sample offer leads to merchant-controlled payment instructions; settlement is a separate step.
Your acquisition or licence
A clear scope from the outset.
Agree the assets, rights and delivery milestones before commitment, with the detail set out in the signed schedule.
View included assets, exclusions and conditions
Interface and supporting materials
- Proposed inclusion
- Specified request data schema, interface and operating documentation.
- Excluded or conditional
- Third-party product content, customer records and rights outside the scheduled software.
Rights and delivery
- Proposed inclusion
- Defined software rights and an agreed setup for the buyer's merchant model.
- Excluded or conditional
- SatCart's scope is non-custodial. The merchant retains payment, fulfilment and refund responsibilities; a payment handoff is distinct from confirmed settlement.
Agreed acceptance
- Proposed inclusion
- Agree a controlled basket-to-merchant-acceptance journey and the payment handoff. Any payment-status integration is separately specified and validated.
- Excluded or conditional
- Buyer-specific delivery requirements and any continuing services are agreed separately in writing.
A straightforward acquisition or licence.
A defined application and service-configuration walkthrough, with fixed transition support and clear ongoing provider responsibilities.
Explore the transaction structure that fits your business. Speak directly with the founder about the commercial fit and next steps.
Request confidential details →Explore your commercial scenario
What could this mean for your business?
Explore merchant software subscriptions, separately from Bitcoin prices or customer payment volumes.
Editable sample assumptions. Use your own figures. These examples are not forecasts, observed results or sale asking prices.
Illustrative annual gross software revenue
Formula: Merchant customers × monthly software fee × paid months.
Gross revenue before delivery, software, other costs and taxes; not net profit. This scenario does not model Bitcoin returns or funds handled.
Discuss this scenarioDefine the deal
SatCart
Connect buyer intent with a merchant's own payment route through an organised offer and acceptance journey.
Included in the discussion
- Scheduled basket, offer, merchant-acceptance and payment-handoff application components.
- Specified request data schema, interface and operating documentation.
- Defined software rights and an agreed setup for the buyer's merchant model.
A clear handover
A defined application and service-configuration walkthrough, with fixed transition support and clear ongoing provider responsibilities.
Scope and acceptance
Agree a controlled basket-to-merchant-acceptance journey and the payment handoff. Any payment-status integration is separately specified and validated.
SatCart's scope is non-custodial. The merchant retains payment, fulfilment and refund responsibilities; a payment handoff is distinct from confirmed settlement.
Agree before commitment
- Application and permitted use
- Brand and domain scope
- Delivery and acceptance milestones
- Payment schedule and fixed support period
A proposed starting package
- Rights
- Acquire the scheduled seller-owned software assets, or license the defined workflow for your operation. Brand and domain rights are itemised separately.
- Exclusivity
- Acquisition and licence alternatives are priced separately. Any exclusivity is defined by the rights, market, territory and term in the agreement.
- Handover allowance
- A defined application and service-configuration walkthrough, with fixed transition support and clear ongoing provider responsibilities.
- Payment structure
- A staged payment schedule tied to signed scope, agreed workflow acceptance and completed handover. Amounts and timing are agreed in the written offer.
Discussion terms, subject to the exact rights schedule, costed delivery scope and written agreement. These handover allowances begin after acceptance; implementation obligations and defect remedies are specified separately.
Proposed commercial scope. Final rights, price and delivery obligations are agreed in writing.
Discuss this package →Make an informed acquisition
Practical guides for buyers.
Compare acquisition with a new build, understand licence scope and assess a website portfolio.