The Notification Process

The notification process has been developed to add a real time track and monitor of your transactions. When a transaction is complete, there are two main methods to retrieve its informations: “pull” and “push”. These two methods can also be combined. Push notifications are recommended as they can be applied in a more general way.

Crediting Customer

We suggest you to credit your customer when you received status as APPROVED, we will always inform you with message but if you want to group the responses by transaction result or show the transaction results in multi language back office, you can use code parameter which is useful for determine the result reason.

Please check possible response codes

Pull

Payment Status

The Merchant System pulls the payment result from our system Payment Status service by invoking the “status” method.

  • Live URL : https://api. /pw/v3/payment/status
  • Test URL : https://testapi. /pw/v3/payment/status

Parameters

Parameter Name Detail Example Type Always There
apiKey Your Api Key provided from us. 4d41d21a935f5bba9dee7 c7be4a7ca04 Char 32 ✔
referenceNo Your own transaction identifier. 1-1386413490-0089-14 Char 32 ✔

Payment Detail

  • Live URL : https://api. /pw/v3/payment/detail
  • Test URL : https://testapi. /pw/v3/payment/detail

Parameters

Parameter Name Detail Example Type Always There
apiKey Your Api Key provided from us. 4d41d21a935f5bba9dee7 c7be4a7ca04 Char 32 ✔
referenceNo Your own transaction identifier. 1-1386413490-0089-14 Char 32 ✔

Push

For each completed transaction process, a notification is sent asynchronously to the defined notification URL. The notification is sent with the POST HTTP method and contains the standard response parameters. During a transaction, you can receive several notifications with different status. This means that a transaction can, in very rare cases, change from status “failed” to “captured”. On the other side, if a transaction is set to “captured”, it cannot come back to “failed” or “pending”. Pay close attention to credit your customers once even if you receive a “captured” status multiple times. For various reasons, sometimes the push notification does not lead to your server. This is never 100% reliable. We recommend in this case to exceptionally use the pull method to fetch yourself the status of a transaction if you do not get a notification after several minutes.

For push feature, please provide us URL from your system.

Screenshot

  • If the IPN cannot be delivered to you URL, We will try to re-send the IPN in one hour. This is processing for ten times.Basically, we will try to send the IPN ten times in ten hours.

Security

  • We highly recommend that integrate IPN integration and accept only our IP requests to your end point 
Test environment

IP ADDRESS : 35.187.167.26
IP ADDRESS : 35.205.153.149
IP ADDRESS : 35.195.39.227
                            

Live environment

IP ADDRESS : 35.233.71.4
IP ADDRESS : 104.155.117.86
IP ADDRESS : 35.189.219.45

Checksum

We highly recommend to control checksum with IPN call. You will receive token with IPN request this token will be hashed

  • secretKey apiKey code status amount currency referenceNo timestamp
<?php
$request = $_REQUEST;
$secretKey = 'YOUR_SECRET';

function generateToken($request, $secretKey) {
    $rawHash = $secretKey . $params['apiKey'] . $params['code'] . $params['status'] . $params['amount'] . $params['currency'] . $params['referenceNo'] . $params['timestamp'];
    return md5( $rawHash );
}

Successful request from IPN

Parameter name Details Example Type Always there
code Meaningful response code for merchant system 02 - Response Code List String ✔
status The API request status. APPROVED - Status List Char 64 ✔
message Status message Auth3D is APPROVED Char 256 ✔
type Transaction type Please Check Types Char 256 ✔
operation Transaction operation Please Check Operations Char 256 ✔
referenceNo Your own transaction identifier. 1-1386413490-0089-14 Char 32 ✔
transactionId Our unique transaction identifier. 9-1438782271-1 Char 32 ✔
amount Amount in cents of the transaction 1234 (12.34 € for example) Int ✔
currency The currency of the transaction. EUR Char 3 ✔
paymentMethod Customer Payment Method VISA - Supported payment methods Char 32 ✔
timestamp Date and time 1533543919 ✔
token Code generated 98ca055ed2797f53c5144f4 Char 34 ✔
creditCard The credit card information. Please Check Creditcard
storedCardId Only sent if the card stored by merchant for supported payment methods 6-1474539891-0-1 Char 32

Creditcard

Parameter name Details Example Type Always there
number Masked Credit Card pan number 401288XXXXXX1881 Char 32 ✔
expiryMonth The card expiration month. 12 Int 2 ✔
expiryYear The card expiration year 2019 Int 4 ✔
email Customer email address. [email protected] Char 256 ✔
birthday The customer birth date. 1970-01-01 YYYY-MM-DD ✔
billingFirstName First name of the customer. John Char 64 ✔
billingLastName Last name of the customer. Doe Char 64 ✔
billingAddress1 The customer address 1. 26 green street Char 128 ✔
billingCity The customer city. Paris Char 64 ✔
billingPostcode The customer zip code. 75001 Char 16 ✔
billingCountry The customer state. FR Char 2 ✔
billingState The customer state. FR Char 2

Status Codes

  • APPROVED (Purchase successfully received)
  • DECLINED (Purchase declined because of acquirer reasons)
  • CANCELED (Transaction canceled by customer)
  • PENDING (Customer did not select any payment and try to purchase or canceled)
  • WAITING (Async payment methods, result will be inform by push method. Bank Transfer, Withdraw, Mobile Banking)
  • ERROR (System Throws Exception)

Transaction Operations

  • 3DAUTH (3D Purchase)
  • DIRECT (Direct Purchase)
  • STORED (Stored Purchase)
  • REFUND (Refund)

Transaction Types

  • AUTH (Auth Transaction)
  • PREAUTH (Preauth Transaction)