Versions Compared

Version Old Version 2 New Version Current
Changes made by

Roland Thijssen

Currence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


 

Function

Request from the Merchant to retrieve the status of a specific transaction from the Acquirer.

Root

AcquirerStatusReq

Data elements

createDateTimestamp 


Merchant

Transaction

Signature

Sub-elements

merchantID
subID

transactionID

SignedInfo
SignatureValue
KeyInfo

Response

AcquirerStatusRes (F').

Communication

HTTP POST request with an XML message to the AcquirerStatusURL

Security / authentication

  • Unilateral TLS connection (Acquirer holds SSL server certificate)
  • Authentication of Acquirer based on Acquirer's SSL server certificate
  • Authentication of Merchant based on Merchant.merchantID, Merchant.subID in the message
Comment

A Merchant may send an AcquirerStatusReq to an Acquirer for a transaction only in the following cases:

  • When by a an Redirect to Merchant (E) as part of the Payment protocol, or
  • When triggered by the elapsing of the Transaction.expirationPeriod, or
  • At a later time, after the Transaction.expirationPeriod has elapsed

The Merchant should submit a 'batch processing' of open transactions serially (one by one) to the Acquirer.


expandImage Removed
Section
bordertrue


Column
width675px


See 'Appendix: IDs'

(Sub-)element

Description

createDateTimestamp

Date and time at which this message was created

Expand
titleMore info
Note: Because the field is included in the digital signature, the value of this field must be determined prior to generating the signature.


Merchant

merchantID

See 'Appendix: IDs'

subIDSee 'Appendix: IDs'
Transaction

transactionID

Made up of Acquirer.acquirerID (first four positions) and a unique number of six positions (together ten positions)

subIDA number from 0 to and including 999999 in which each value is related to a separate instance registered with the Acquirer. The default value is '0'.
Transaction

transactionID

Unique 16-digit number within an iDx based product, assigned by an Acquirer. The number consists of a section from the Acquirer (Acquirer.acquirerID, first four positions) and a unique number generated by the Acquirer (12 positions).



Div
stylepadding-left: 1cm
idno-print
classno-print


Excerpt


Column
width100%

Example

Message RDark

message

Code Block
languagexml
theme
<?xml version="1.0" encoding="UTF-8"?>
<AcquirerStatusReq version="1.0.0" productID="NL:BVN:
eMandates
eMandatesCore:1.0"
	xmlns=" http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0"
	xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<createDateTimestamp>2001-12-17T09:30:475Z</createDateTimestamp>
	<Merchant>
		<merchantID>1234123456</merchantID>
		<subID>1</subID>
	</Merchant>
	<Transaction>
		<transactionID>1234123456789012</transactionID>
	</Transaction>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
        <!-- Signature is placed here. See Signature section for specification-->
    </Signature>
</AcquirerStatusReq>
titleClick for a schematic representation





Schematic representation
 of AcquirerStatusReq (F)