X-Payments:Callback request with service payment information - Revision history

Dohtur at 12:14, 24 April 2018

2018-04-24T12:14:49Z

Dohtur at 13:44, 26 July 2016

2016-07-26T13:44:37Z

Dohtur: Created page with "This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment..."

2016-07-20T08:45:41Z

Created page with "This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment..."

New page

This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment gateway. The request is sent via HTTP POST to the callbackURL defined in the Payment initialisation request. Once this request has been sent, the customer is redirected back to the store.

===POSTed data===
{| cellspacing="0" cellpadding="2" border="1"
| colspan="1" | '''Field'''
| colspan="1" | '''Value'''
| colspan="1" | '''Type'''
| colspan="1" | '''Description'''
|-
| colspan="1" | action
| colspan="1" | callback
| colspan="1" | fixed string
| colspan="1" | Identifies the callback request
|-
| colspan="1" | txnId
| colspan="1" | (mixed)
| colspan="1" | string (MD5 hash)
| colspan="1" | A unique ID of the payment on the side of X-Payments
|-
| colspan="1" | updateData
| colspan="1" | (mixed)
| colspan="1" | string
| colspan="1" | Encrypted response from X-Payments
|}

X-Payments does not expect a response from the store for this request; however, if the HTTP status of the response is not 200 OK, the request is considered failed, and a special notification is sent to the X-Payments admin. The store needs to decrypt the encrypted part of the response and update the order on its side accordingly. Once the updateData value has been decrypted, it is an XML document with the same structure as the [[X-Payments:API#Response_specification_2|response for Payment information request]].
<br /><br />

← Older revision		Revision as of 13:44, 26 July 2016
Line 1:		Line 1:
		+	<noinclude>{{XP_API_TOC}}</noinclude>
	This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment gateway. The request is sent via HTTP POST to the callbackURL defined in the Payment initialisation request. Once this request has been sent, the customer is redirected back to the store.		This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment gateway. The request is sent via HTTP POST to the callbackURL defined in the Payment initialisation request. Once this request has been sent, the customer is redirected back to the store.

@@ Line 1: / Line 1: @@
 <noinclude>{{XP_API_TOC}}</noinclude>
 This is a background request that X-Payments sends to the store after a payment has been completed and its result (accepted, declined, etc) has been received from the payment gateway.  The request is sent via HTTP POST to the callbackURL defined in the Payment initialisation request. Once this request has been sent, the customer is redirected back to the store.
 ===POSTed data===