Joony CommerceDiscuss your project
Ecommerce payment integration

Connect online payment without hiding provider responsibility.

Start from hosted ABA/KHQR and wallet payment foundations, then confirm onboarding, callbacks, reconciliation, fees and recovery for the selected provider.

Hosted payment foundationsPayment-status contextProvider-specific onboardingExplicit reconciliation design
Online-first · early access

Joony has reusable hosted-payment and payment-status foundations, but a provider is never represented as automatically available for every business or market. Merchant approval, commercial terms, settlement and integration acceptance remain launch dependencies.

01

Treat payment as an external state machine.

A customer leaving checkout does not by itself prove payment. The implementation defines provider redirects or hosted flows, authenticated callbacks, retry behaviour, expiry and the order status allowed for each payment outcome.

  • Verify provider callback and signature behaviour
  • Design pending, failed, expired and successful outcomes
  • Keep retry and duplicate handling recoverable
02

Reconcile money as well as technical success.

A successful API response is not the same as settlement. Joony confirms provider reports, fees, payout timing, refunds and the operational owner responsible for investigating differences.

  • Document fees and settlement timing
  • Define payment-to-order reconciliation
  • Scope refund and support responsibilities