Swadakta Sign in

Payments & Pricing

Quote first. Protect money. Release by proof.

Swadakta earns through a clear service margin built into each quote. Clients pay through provider rails where possible, receivers are paid after proof and milestone checks, and risky money decisions stay protected.

Launch rails

Provider payments before receiver payout.

credit_card
Card or PayPal first

Standard global work should use checkout, invoice, or order links before manual transfers.

phone_iphone
M-Pesa where supported

KES collections can use Safaricom Daraja once the business account and callback are live.

account_balance
Wise stays hidden as fallback

Wise is used only when simpler rails fail or do not fit because it adds manual reconciliation.

Step 1

Brief

Client creates a corridor brief with route, task, proof, item, value, and timing details.

Step 2

Quote

Swadakta prices time, travel, risk, platform margin, receiver payout, and provider fees.

Step 3

Protect

Payment is collected or confirmed through the safest available rail before paid work proceeds.

Step 4

Release

Receiver payout is released by milestone after proof, report, dispute, and scope checks.

Estimate a launch quote

A quick range before the real quote.

This estimator is deliberately conservative. The final quote still depends on the actual corridor, lawful-goods checks, receiver availability, travel, documents, urgency, and proof requirements.

Founder margin is built into each quote.

At launch, the clean model is total client quote minus receiver payout, field costs, and provider fees. The founder margin is what funds Swadakta, support, AI tooling, risk work, and growth.

Planning range

AUD 85-130

Recommended rail: card checkout or PayPal. Protected decisions still wait for the final brief.

Payment rails

Use the lowest-friction safe rail first.

Swadakta should not make the founder reconcile every payment manually. The normal order is card or PayPal for global clients, M-Pesa for suitable KES collections, bank transfer where a receipt trail is clean, and Wise only as an exception fallback.

credit_card

Stripe / card

Best for standard global checkout, deposits, and repeatable packages in supported currencies.

account_balance_wallet

PayPal

Useful when clients prefer PayPal approval, order, or invoice style payment.

phone_android

M-Pesa

Planned for Kenya-shilling work through business Daraja setup, callback confirmation, and recorded receipts.

sync_alt

Bank / Wise fallback

Manual rails require matching amount, sender, date, and Swadakta reference before funds count as protected.

What clients see

Transparent status, not internal costs.

  • check_circleQuote amount, payment status, funds status, safe payment link, and release condition.
  • check_circleProof requirements, milestone progress, receipts, media, and client-safe reports.
  • check_circleRefund or dispute pauses when scope, proof, or provider evidence needs review.

What founder/admin sees

Margin and protected decisions.

  • lockQuote revenue, receiver payout, field costs, payment processing fee, and margin risk.
  • lockProvider reference, callback state, reconciliation notes, and fallback payment evidence.
  • lockAI can draft and check. It cannot mark paid, release funds, refund, or assign paid work.

Escrow boundary

Swadakta is not currently a licensed escrow provider.

For high-value property, title, construction, supplier deposits, or legally sensitive jobs, use a regulated escrow/payment provider or staged provider-held funds before receiver release. Swadakta can track milestones and proof, but should not pretend to be a bank, escrow company, law firm, or tax advisor.