WQN Gateway 작동 방식

From integration to reconciliation

A clear path from the first API request to settlement.

Choose an integration path, validate it in Sandbox, complete provider and compliance readiness, then operate payments with signed events and traceable reports.

01

Hosted checkout

Redirect customers to a managed payment experience while keeping sensitive payment details outside the merchant application.

02

Server API

Create payment intents, attach merchant references, select routes, and consume normalized status updates from your backend.

03

Payment links

Prepare a lightweight path for teams that need a shareable checkout without building a complete custom front end.

Connection path

Step by step

1. 1
   Create merchant accountMerchant logs in, reviews business profile, and prepares KYC/KYB details.
2. 2
   Generate sandbox keysUse publishable and secret keys from the member API page.
3. 3
   Create payment intentSend amount, currency, metadata, and Idempotency-Key from the merchant server.
4. 4
   Redirect to checkoutCustomer chooses card, QR, wallet, bank, BNPL, or counter payment.
5. 5
   Verify webhookValidate HMAC signature, timestamp, request ID, and event status.
6. 6
   Reconcile settlementExport transactions, fees, holds, and payout batches from reports.

Provider routing

2C2P ready

• WQN creates an internal payment intent first.
• Provider adapter requests a payment token when 2C2P route is selected.
• Payment options are filtered by market, currency, device, method, and risk rules.
• Provider notification is normalized to WQN events for merchant webhooks.
• Status inquiry, refund, cancel/void, and reconciliation are handled from protected operations workflows.

Normalized payment flow

One merchant integration, controlled provider handoffs.

1MerchantCreate payment intent

→

2WQN GatewayValidate, route, normalize

→

3ProviderAuthorize payment method

→

4WebhookDeliver signed status

Developer checklist

Before live

• Use server-side secret keys onlyRequired
• Send Idempotency-Key on mutating requestsRequired
• Verify webhook HMAC signatureRequired
• Test approved, review, declined, refund, and cancel scenariosRequired

Go-live gates

Approval

• Provider contract and credentialsPending
• Compliance and PCI scope reviewPending
• Settlement bank verificationPending
• Risk rules and approvalsPending