KLiCKPAY

Merchant Integration Guide · v1.1.1


Overview

Call KLiCKPAY from your server only. Base URL https://pay.klicksev.net

Before integration, send KLiCKPAY:

  1. Your server outgoing IP, for the whitelist
  2. Your RSA public key only

Integration requires you to provide an RSA Public Key (1024 bit). It can be generated from the following web page (https://travistidwell.com/jsencrypt/demo/).

Send only RSA Public Key. Keep the private key to generate signature in codes.

KLiCKPAY then gives you:

Production site: klicksev.net. Reply the text success when KLiCKPAY calls your Notify URL or payout verification URL.

Callback IP

KLiCKPAY sends callbacks (NotifyUrl) and payout verification (ReturnUrl) from IP 34.87.162.255. Add it to your firewall allowlist, and still verify the Signature.

KeyWho creates itWho keeps itUse
AES keyKLiCKPAYYou and KLiCKPAYEncrypt and decrypt Data
Merchant RSA private keyYouYour server onlySign each request
Merchant RSA public keyYouSend to KLiCKPAYKLiCKPAY verifies your signature
KLiCKPAY RSA public keyKLiCKPAYYouVerify KLiCKPAY’s signature
KLiCKPAY RSA private keyKLiCKPAYKLiCKPAY onlyKLiCKPAY signs the callback

Call format

Every POST uses Content-Type: application/json. Version is 0.

Submit Deposit uses this JSON. The other calls use the same fields with a capital first letter: MerchantCode, Data, Signature, Version.

{
  "merchantCode": "VND00001",
  "data": "<base64>",
  "signature": "<base64>",
  "version": 0
}
Sign the exact JSON string inside Data, then encrypt that same string. AES is AES-256-CBC. The signature is RSA-SHA1. The Encryption tab has the steps.