When the merchant system receives a payment, withdrawal, or event notification it must immediately perform a series of actions based on the type of transaction.

The specific actions depend on the merchant's risk policies and procedures, but typically include verifying one or more of the following conditions:

The transaction number (txn_num) assigned by Paramount in the notification is unique and correct. This is required to avoid processing the same transaction more than once.
The merchant account (merchant_id) in the notification is the correct merchant account ID assigned by Paramount.
The transaction type (txn_type) and status (txn_status) are valid.
The currency code (txn_currency) and amount (txn_amount) in the notification match those values in the transaction request initiated by the merchant.

In addition to these general verification actions, the merchant system should perform specific actions based on the type of notification (payment, withdrawal, or return).

Transaction Notification

When a merchant system receives a transaction notification, the system should:

Compare the transaction details received in the notification with the original data provided in the request. This check ensures that the data has not been altered.
Record the results of the transaction in the merchant system.

Verification Request

The content is sent to Paramount in an HTTP POST request to the following notification verification URL:

Notification verification URL
`https://staging.paydirectnow.com/service/servlet/ConfirmTrans`

🚧
Upon receiving a transaction notification from Paramount, the merchant application must echo back the original content to verify its authenticity.

After checking the transaction notification message and performing the necessary actions, the merchant system must echo back an exact copy of the original notification message to Paramount. This verification request confirms that the notification was successfully received and processed by the merchant.

If the merchant system doesn't send the verification request after it receives the notification, the system sends the notification again, to a maximum of three times. If Paramount still hasn't received the verification request after the notification is sent the third time, the notification is marked as unsuccessful in the Paramount system. The Paramount support team monitors systems for unsuccessful notifications and contacts merchants when necessary.

Verification Response

The verification response signals to the merchant system that Paramount marked the notification as successfully processed by the merchant.

Parameter

Type

Size

Required

Description

verification_code

String

4

Yes

The data verification code. Any response code other than 0 (zero) indicates that the data contains errors.

*0**: Verified
*C001**: Could not parse verification request - Invalid HTTP request
*C002**: Could not parse verification request - invalid content
*C003**: Could not parse verification request - invalid transaction ID
*C004**: Verification details don't match original payment - notification not found / exceeded 4 minute thread timeout
*C005**: Verification details don't match original payment - notification doesn't match
*C006**: Generic err

Example verification response

verification_code=0