Customer and merchant
Your website creates the order. Coinductor receives the payment details as a prefilled, regular wallet-to-wallet transfer for the customer to review and sign.
For Business · Connected Checkout
Keep your customer moving. All the way to checkout.
Let customers connect Coinductor, choose on your website and review the payment in their wallet. The amount and recipient arrive already filled in. Once the customer approves, USDT goes directly to your designated wallet.
The purchase stays with your business.
OTO Pass stays with
Coinductor.
User and Coinductor
If the sender lacks sufficient TRX, OTO Pass is an optional SaaS feature that can enable an eligible transfer. It is separate from the merchant purchase.
Direct funds path
The customer-approved USDT transfer goes directly to the merchant-designated wallet. Coinductor does not hold or settle the purchase funds.
Customer experience
A zero-TRX option.
OTO Pass can support an eligible transaction when the sender has no TRX, subject to eligibility and a separate purchase of the Coinductor SaaS feature.
Wallet control
The customer approves.
Connection and payment are separate decisions. Every transfer is reviewed and signed in the customer’s wallet.
Funds path
Direct to your wallet.
The customer-approved transfer goes to the merchant-designated address. Coinductor does not take custody of purchase funds.
Two customer situations
One familiar checkout.
One familiar checkout.
Two available paths.
The available option is shown before the customer signs. Neither path removes the customer’s final review and approval.
Wallet has TRXSmart Send
Lower-cost sending.
Smart Send requires TRX and can help reduce network costs. The customer reviews the estimated fee and transaction details before signing.
Wallet has zero TRXOTO Pass
No TRX top-up first.
For an eligible transfer, the customer can choose OTO Pass as a separate Coinductor interaction and approve the wallet transfer without first obtaining TRX elsewhere.
The customer still decides.Every transaction is presented in Coinductor and signed only after
the customer approves the specific request.
Smart Send requires TRX. Smart Send savings vary by transaction, route availability and network conditions. OTO Pass is a separately purchased, single-use software feature; eligibility, sponsored-route availability, wallet activation requirements and local purchase price may vary.
Customer journey
Choose. Review. Pay. Return.
Customers choose on your website, open the payment request in Coinductor and approve the transfer. Your website checks the payment result and updates the order.
Connected Checkout.
The website manages the purchase. Coinductor presents the wallet request. Your website updates the order only after it verifies the transaction result.
1ScanThe customer scans your connection code.
2ConnectThey review the requesting domain and access.
3ChooseThey select your product, service or account action.
4CheckoutYour website creates the payment request.
5ReviewCoinductor shows the amount, recipient, network and applicable
fee.
6ApproveThe customer confirms and signs locally.
7UpdateYour platform verifies the result before fulfilment.
Request and status
Your websiteCoinductorYour website
Your platform sends supported transaction details for review and receives the status needed to manage its order flow.
USDT transfer
Customer walletTRONYour wallet
USDT moves directly from the customer wallet to the merchant-designated address. Coinductor does not provide merchant settlement.
Clear responsibilities
Your checkout. Their approval.
Coinductor provides
- Supported wallet connection and request presentation
- Pre-flight transaction review in the app
- Customer-controlled local approval and signing
- Transaction-status information for the supported flow
- Smart Send and eligible OTO Pass options
Your business manages
- Customer accounts, products and pricing
- Required identity, sanctions and compliance checks
- Order attribution and transaction-confirmation policy
- Taxes, purchase terms, refunds and customer support
- Delivery, account crediting and fulfilment
Self-custodial by design
Approved by the customer. Sent directly to you.
Private keys and recovery phrases must never be entered into your website or shared with Coinductor. The customer reviews and approves the transaction in their wallet. This reduces the need to build key-handling or customer-funds custody into the integration.
Customer keys handled by your pageNone
Purchase funds held by CoinductorNone
Transaction approvalCustomer, every time
Current supported scopeTRX and USDT on TRON
Integration
Bring the request
Bring the request
to the wallet.
Connect your checkout to Coinductor so supported transaction details arrive in the customer’s wallet for review and approval.
Separate sign-in from payment.
A wallet connection allows supported communication with the customer’s wallet. It does not authorize a payment. Create a new, specific transaction request for every checkout.
Design for every status.
Plan for approval, rejection, expiry, cancellation, duplicate requests, submission, network failure and confirmation before updating the order.
Identify the requesting domain.
Domain validation helps the customer understand where a supported request came from. It does not certify your company, products or regulatory status.
Confirm before fulfilment.
Your platform remains responsible for matching the transfer to the correct order and deciding how many network confirmations are required.
Public API documentation is being prepared, and integration availability is confirmed individually. Technical compatibility, security requirements and applicable merchant obligations must be reviewed before launch.
Bring Coinductor to your checkout.
Tell us about your customer journey, supported market and transaction flow. We’ll confirm whether the current integration can support your use case.