Account access, catalogue, pricing, checkout rules, customer obligations and order state remain with your service.
Developers · Integration hub
Bring your website closer to the wallet.
Connect wallet-based sign-in and payment requests to your website. Customers use your service, then review and approve supported transfers in Coinductor.
Partner accessTRON · USDT and TRXAuthentication guide available
The model
Your experience.
Your experience.
Their wallet.
Your platform keeps control of the account, product, order and fulfilment. Coinductor gives the customer a familiar place to review and approve supported wallet actions.
Short-lived requests carry supported authentication or transaction details between the service and the wallet.
The customer sees the requesting service and relevant details, then separately approves or rejects the requested action.
Connection is not payment authorization. Authentication can establish wallet control for your service, but it does not approve a later transaction. Each transaction requires its own clear request and customer confirmation.
Coinductor Auth
A scan to connect. A choice to approve.
Let customers scan a QR code with Coinductor and review your website’s identity before approving sign-in. Your service remains responsible for its account rules and access decisions.
1Create challengeYour backend creates a short-lived, single-use authentication
challenge.
2Show QRYour frontend displays a connection code bound to the browser
session and requesting origin.
3Scan in walletCoinductor shows the requesting domain and asks the customer to
continue.
4Verify responseYour backend validates the origin, challenge, signature and
permitted request context.
5Create sessionYour service creates or accesses the account under its own
policies.
Wallet authentication proves control of the signing key used for that request. It does not, by itself, prove a person’s legal identity, age, location, authority or regulatory eligibility.
Start building
Your authentication toolkit.
Explore the Coinductor Auth reference flow, run a local example and prepare your own backend. Reference code is available through partner access and requires production review.
Run the example
Requirements, configuration and a browser-to-wallet walkthrough.
Quick start →Understand the protocol
QR fields, relay events, encrypted responses and backend verification.
Protocol guide →Scan or simulate
Use a supported Coinductor app build or the included test-wallet simulator.
Testing guide →Prepare for production
Review signing compatibility, challenge handling, origins and real sessions.
Launch requirements →
Connected Checkout
From selection
From selection
to wallet approval.
Keep the shopping experience on your website. When the order is ready, deliver the supported transaction details to Coinductor for customer review and approval.
One journey. Separate decisions.
Authentication, checkout and transaction approval are independent stages. Bind every request to the correct order and session, then verify the network result before fulfilment.
1ConnectCreate a short-lived request for your registered domain.
2AuthenticateThe customer reviews and approves wallet-based access.
3Build orderYour website manages the catalogue, price and eligibility.
4RequestProvide the supported recipient, amount, asset and network.
5ApproveCoinductor presents Pre-flight details for local
confirmation.
6VerifyHandle rejection, expiry, submission, failure and
confirmation.
7FulfilUpdate the order under your own confirmation policy.
A successful wallet response is not automatically proof of a confirmed blockchain transfer. The merchant must validate the transaction result, recipient, asset, amount, network and required confirmation status before fulfilment.
Clear responsibilities
Your request. Their signature.
Coinductor presents supported requests and enables local wallet approval. It does not operate the merchant’s checkout or receive and settle the customer’s purchase funds.
Coinductor provides
- Supported wallet connection and request delivery
- Customer-facing review and approval inside the wallet
- Local signing without exposing the private key or recovery phrase
- Supported transaction submission and wallet-facing status
Your service manages
- Accounts, orders, prices, products and fulfilment
- Customer eligibility, required checks and legal obligations
- Recipient-wallet ownership and transaction reconciliation
- Refunds, disputes, taxes, support and confirmation policy
Never request a private key or recovery phrase. Integrations must also avoid presenting wallet control as legal identity verification or presenting a connection as transaction approval.
API availability
Let’s plan your integration.
Tell us how customers sign in, what they need to pay for and how your website confirms an order. We can discuss the supported flow with your team. Start with the authentication guide and request access to its reference example. The Connected Checkout technical specification remains in preparation.
Authentication protocol
The reference guide covers QR sign-in, relay messages, backend verification and testing. Production compatibility still requires confirmation.
REST specification
The Auth guide documents the demo routes on your own backend. A broader versioned public REST specification is not yet published.
Checkout events
Request states, expiry, cancellation, idempotency, callbacks and blockchain confirmation rules require a canonical specification.
Integration review
Supported markets, transaction flow, security requirements and merchant responsibilities are assessed before launch.
The Auth guide describes a reference implementation, not a production certification. Request the approved version and mobile compatibility details before launch. Authentication documentation does not specify checkout APIs or payment callbacks.
Bring the request closer to the wallet.
Tell us how customers use your service, what they need to approve and how you confirm the final transaction. We’ll assess the appropriate integration route.