1. Non-Secure Payment
SA
  • Overview
    • Getting Started
  • Authentication
    • Token Generation
      POST
  • Commission
    • Commission
      POST
  • HASH
    • Hash Creation
    • Hash Validation
  • Non-Secure Payment
    • Non-Secure Payment Flow
    • Non-Secure Card Payment
      POST
    • Non-Secure Pre-Authorization Payment
      POST
    • Confirm Payment
      POST
  • 3D Secure Payment
    • 3D Secure Payment Flow
    • 3D Secure Card Payment
      POST
    • 3D Secure Pre-Authorization Payment
      POST
    • Complete Payment
      POST
    • Confirm Payment
      POST
  • Non-Secure and 3D Payment with Sipay
    • Non-Secure and 3D Secure Payment with Sipay
      POST
  • Check Status
    • Check Status
      POST
  • Refund
    • Refund
      POST
  • Webhook
    • Webhook
  • Status Codes
    • Status Codes
  1. Non-Secure Payment

Confirm Payment

Testing
POST
/ccpayment/api/confirmPayment
confirm_payment endpoint is used to confirm the payment.
The confirm endpoint must be triggered when the payment_completed_by parameter is sent to the merchant.
If this endpoint is not sent, it will be automatically canceled by the bank in approximately 20 business days.

The hash key must be sent in the request.
Sample hash keys can be found in the request form panel on the side, corresponding to the selected programming language.

Hash Parameters#

The parameters and their order to be used for the hash algorithm are as follows.
merchant_key
invoice_id
status
app_secret

Request

Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Body Params application/jsonRequired

Examples

Responses

🟢200Success
application/json
Body

⚪68Failed
Request Request Example
Shell
JavaScript
Java
Swift
#!/usr/bin/env bash

 

generate_hash_key() {
  local merchant_key="$1"
  local invoice_id="$2"
  local status="$3"
  local app_secret="$4"

 

  local data="${merchant_key}|${invoice_id}|${status}"

 

  local iv
  iv=$(openssl rand -hex 16 | openssl sha1 | awk '{print $2}' | cut -c1-16)

 

  local password
  password=$(printf "%s" "$app_secret" | openssl sha1 | awk '{print $2}')

 

  local salt
  salt=$(openssl rand -hex 16 | openssl sha1 | awk '{print $2}' | cut -c1-4)

 

  local salt_with_password
  salt_with_password=$(printf "%s" "${password}${salt}" | openssl sha256 | awk '{print $2}' | cut -c1-32)

 

  local key_hex
  key_hex=$(printf "%s" "$salt_with_password" | xxd -p -c 256)

 

  local iv_hex
  iv_hex=$(printf "%s" "$iv" | xxd -p -c 256)

 

  local encrypted_base64
  encrypted_base64=$(printf "%s" "$data" | openssl enc -aes-256-cbc -K "$key_hex" -iv "$iv_hex" -base64)

 

  local msg="${iv}:${salt}:${encrypted_base64}"
  msg="${msg//\//__}"

 

  echo "$msg"
}

 

merchant_key="test_merchant_123"
invoice_id="INV-2026-0001"
status="1"
app_secret="my_secret_key_456"

 

result=$(generate_hash_key "$merchant_key" "$invoice_id" "$status" "$app_secret")
echo "Hash Key: $result"
Response Response Example
200 - Success
{
    "status_code": 100,
    "status_description": "The transaction has been Approved",
    "transaction_status": "Completed",
    "order_id": "VP17697652077026116",
    "invoice_id": "VUONVW35PWK2TDY-1769765203"
}
Modified at 2026-04-29 07:20:15
Previous
Non-Secure Pre-Authorization Payment
Next
3D Secure Payment
Built with