Wait or redirect after Mark as Paid

What this setting does

In Manual Mode, money moves outside a PSP API. When the customer taps Mark as Paid, they first see a confirmation dialog (SweetAlert) whose copy depends on this setting. After they confirm and mark paid succeeds, SkyPay needs a rule: keep them on a verifying screen until you Complete, or auto-redirect to success_url immediately.

That rule is configured per Manual Mode provider in the dashboard under manual_configuration.after_mark_paid.

How it works

Both options start with a confirm dialog, then set status to waiting. The fork is what happens next: stay on verifying until you Complete (wait), or auto-redirect to success_url right away while you confirm later (continue).

Dashboard settings

Open Payment Providers, edit a Manual provider, and choose After mark paid:

Option: Wait for confirmation

Value: wait (default). Label in the dashboard: Wait for confirmation.

• Customer taps Mark as Paid → confirmation dialog (SweetAlert) first.
• After confirm succeeds, checkout stays on a verifying screen — no auto redirect.
• SkyPay polls until the merchant marks Complete.
• Then the customer is redirected to success_url.
• payment.completed fires when you confirm — fulfill from that (and verify), not from the redirect alone.

Option: Continue after mark paid

Value: continue. Label in the dashboard: Continue after mark paid.

• Customer taps Mark as Paid → confirmation dialog (SweetAlert) first.
• After confirm + mark paid succeeds → auto-redirect to success_url immediately.
• Payment status on return is still waiting — do not fulfill yet.
• SkyPay fires payment.waiting; later payment.completed when you mark Complete.
• Admin Complete later still fires the completed webhook for fulfillment.

Real scenarios

Pick wait or continue from how fast you actually confirm Nepal QR and bank transfers — not from what sounds nicer on a settings screen.

Webhooks for both options

Configure an HTTPS endpoint in the dashboard (Webhooks). Enable at least payment.waiting and payment.completed.

Continue mode makes webhooks especially important: the customer is already on success_url with status still waiting, so the return URL is not proof of funds. Fulfill when you mark Complete. See the Manual Mode webhooks section for signature details.

// Express example — POST /webhooks/skypay
app.post('/webhooks/skypay', express.raw({ type: 'application/json' }), (req, res) => {
  const body = req.body.toString('utf8');
  // Verify SkyPay-Signature: t=...,v1=hmac_sha256(secret, `${t}.${body}`)
  const event = JSON.parse(body);

  if (event.type === 'payment.waiting') {
    // Customer marked paid — alert ops. Do NOT fulfill.
  }

  if (event.type === 'payment.completed') {
    const payment = event.data.object; // { code, status, amount, ... }
    // Prefer: re-verify, then fulfill
    // GET https://app.skypay.dev/api/v1/checkout/payments-verify/${payment.code}
  }

  res.status(200).send('ok');
});

Fulfill only on completed

Fulfill only on payment.completed (plus server-side verify) — never on redirect alone when status is still waiting.

1. Receive payment.completed (or poll verify after ops marks Complete).
2. Call https://app.skypay.dev/api/v1/checkout/payments-verify/{code} with your API key.
3. Fulfill only when data.status === 'complete'.

const res = await fetch(
  'https://app.skypay.dev/api/v1/checkout/payments-verify/ORDER_8821',
  { headers: { Key: 'YOUR_API_KEY' } }
);
const { data } = await res.json();

if (data?.status === 'complete') {
  // Safe to fulfill — never fulfill while status is waiting
}

Production checklist

• Choose wait or continue per Manual provider to match how fast you confirm
• Webhook endpoint live for payment.waiting and payment.completed
• Signature verification on your server
• Fulfill only when verify returns complete
• Customer copy for continue (SweetAlert + success_url): “We’ll unlock access after we verify your transfer”
• Ops process to clear waiting payments promptly

FAQ