HiPay Marketplace - Cash-out server-to-server notifications

<?xml version="1.0" encoding="UTF-8"?>
<notification>
<md5content>42108f62f0d13337623e9ac8888e12dd</md5content>
	<result>
		<operation>other_transaction</operation>
		<status>ok</status>
		<date>2019-02-23</date>
		<time>11:04:07 UTC+0000</time>
		<transid>56cc3ca65706f195</transid>
		<account_id>123456</account_id>
		<amount>1000</amount>
		<currency>EUR</currency>
		<label>SALES transactions: Batch 210001 02-23-2019</label>
		<settlement_type>SALES</settlement_type>
		<settlement_id>210001</settlement_id>
		<settlement_date>02-23-2019</settlement_date>
	</result>
</notification>
    

 

2.1. “document_validation” notification for the validation or rejection of a document

An XML notification informing you of the validation status for each document of a seller account is sent.
Six fields are to be taken into consideration:
operation = document_validation
status = ok / nok 
message (reason of the rejection) 
document_type
document_type_label
account_id (value of the HiPay seller account)

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification> 
<md5content>d9e43bb0a9b92aba4fb22eed4164a1f0</md5content>
<result>
<operation>document_validation</operation>
<status>nok</status>
<message>Not a proof of address</message>
<date>2019-02-29</date>
<time>16:39:42 Europe/Paris+0200</time>
<document_type>2</document_type>
<document_type_label>Proof of address</document_type_label>
<account_id>1234567</account_id>
</result>
</notification>
    

 

2.2. “identification” notification for the validation of all documents

A final XML notification informing you that all the documents have been validated for a seller account is sent. Three fields are to be taken into consideration:
operation = identification
status =ok / nok 
account_id (value of the HiPay seller account)

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification>
	<md5content>f7bff5bce16868b3daefbc93bd52902a</md5content>
	<result>
		<operation>identification</operation>
		<status>ok</status>
		<date>2019-03-21</date>
		<time>13:56:40 UTC+0000</time>
		<account_id>1232592</account_id>
	</result>
</notification>
    

 

3.1. “document_validation” for the bank document

An XML notification informing you of the validation status of the bank account identification document (RIB/IBAN) of a seller account is sent.
Six fields are to be taken into consideration:
operation = document_validation
status = ok / nok
message (reason for validation or rejection)
document_type
document_type_label
account_id (value of the HiPay seller account)

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification> 
<md5content>d9e43bb0a9b92aba4fb22eed4164a1f0</md5content>
<result>
<operation>document_validation</operation>
<status>nok</status>
<message>Verified except holder\’s first name</message>
<date>2018-06-29</date>
<time>16:39:42 Europe/Paris+0200</time>
<document_type>6</document_type>
<document_type_label>Bank</document_type_label>
<account_id>1232592/account_id>
</result>
</notification>
    

 

3.2. “bank_info_validation” notification for encoded IBAN

This XML notification informs you of the status of the validation of a seller account’s banking information.
Three fields are to be taken into consideration:
operation = document_validation
status = ok / nok
account_id (value of the HiPay seller account)

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification>
<md5content>a4314ce63fc0be37959d2ee358393bf2</md5content>
<result>
<operation>bank_info_validation</operation>
<status>ok</status>
<date>2018-07-29</date>
<time>15:57:27 UTC+0000</time>
<account_id>1232592</account_id>
</result>
</notification>
    

 

4.1. Notification for electronic transfers

Two XML notifications inform you of the status of the electronic transfer validation. The following fields are to be taken into consideration:
operation = authorization or capture
status = ok / nok
account_id (value of the HiPay seller account)

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification>
<md5content>0abbf2ab3b21019d153f8664c4b27771</md5content>
<result>
<operation>authorization</operation>
<status>ok</status>
<date>2019-05-03</date>
<time>14:10:22 UTC+0000</time>
<transid>5909e4ccce294103</transid>
<account_id>1232592</account_id>
<amount>162.1</amount>
<currency>EUR</currency>
<label>2090 aecf 232550</label>
</result>
</notification>
    

 

<?xml version="1.0" encoding="UTF-8"?>
<notification>
<md5content>b6434b8f37c85878f667d6dccecb1327</md5content>
<result>
<operation>capture</operation>
<status>ok</status>
<date>2019-05-03</date>
<time>14:10:25 UTC+0000</time>
<transid>5909e4ccce294103</transid>
<account_id>1232592</account_id>
<amount>162.1</amount>
<currency>EUR</currency>
<label>2090 aecf 232550</label>
</result>
</notification>
    

 

4.2. “withdraw_validation” notification for withdrawals

This XML notification informs you of the status of the validation or rejection of a withdrawal request to the seller’s or operator’s bank.
Three fields are to be taken into consideration:
operation = withdraw_validation
status = ok / nok (value for chargeback)
account_id = seller account ID

 

Server-to-server POST notification example:

<?xml version="1.0" encoding="UTF-8"?>
<notification>
<md5content>a4314ce63fc0be37959d2ee358393bf2</md5content>
<result>
<operation>withdraw_validation</operation>
<status>ok</status>
<date>2019-05-03</date>
<time>15:57:27 UTC+0000</time>
<transid>5909e4ccce294103</transid>
<account_id>1232592</account_id>
</result>
</notification>