Documentation
  • Welcome!
  • Card (server to server)
    • Overview
      • Authentication
      • Process Flow
      • API Endpoints
      • Testing
    • API Commands
      • 700 – Start Credit Card charge (3DS Enabled)
      • 701 – Request Capture Authorization
      • 702 – Request Cancel Authorization
      • 708 – Check transaction details
      • 709 – Check transaction status
      • 720 – Credit Request
      • 756 – Manual Rebill Request
      • 760 – Request Refund
    • Notifications
      • Notifications
      • 850 – Transaction state Notification
      • 860 – Refund Notification
      • 880 – Dispute Notification
    • Transaction Status Codes
    • 3D Secure Integration
  • APM Checkout (Blik)
    • Overview
      • Process Flow
      • Testing
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Create a checkout session
    • Retrieve a Checkout Session
    • Webhoook Event Notification
    • Pay a Checkout Session
  • Refund a Checkout Session
  • Retrieve checkout session refund
  • Wallet API
    • Introduction
      • Authentication
      • Metadata
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Payout
      • Create a payout
      • Retrieve a payout
  • Wallet payment page
    • Payment Page
Powered by GitBook
On this page
  1. Card (server to server)
  2. Notifications

Notifications

Notifications are sent using the HTTP protocol to the URL provided by the merchant. Notifications are sent with HTTP protocol to URL provided by merchant. Data is transmitted as POST parameter strdata, which contain XML structure.

NODE
REQUIRED
DATA TYPE
DESCRIPTION

result

YES

Character

Result indicates the result of the transaction. OK: means transaction notification was received and accepted. ERROR: means error detected in the notification from the gateway.

gatetransid

NO

Character 36

Unique gateway transaction id.

merchanttransid

NO

Character max 50.

Unique merchant transaction id received in the request.

errorcode

NO

Character

Optional Error Code from the Merchant

errormessage

NO

Character

Optional description of the error.

Notifications Responses

Response from the merchant must be a non-encoded plain XML. Responses to each notification have the same structure. If no response, an invalid response or an error is received from the merchant, the system will attempt to deliver notification for the following 7 days. No further notifications will be sent and the merchant account may be suspended pending resolution of the problem. The Response will take the form of the following example:

  <?xmlversion="1.0" encoding="utf-8" ?>
<response>
		<result> </result>
		<gatetransid> </gatetransid>
		<merchanttransid>760</merchanttransid>
		<errorcode> </errorcode>
		<errormessage> </errormessage>		
</response> 
PreviousNotificationsNext850 – Transaction state Notification

Last updated 9 days ago