API call: MPRSubscribe

Purpose

This command is used by the partner to subscribe a myPOS device to the service. All other commands could be initiated only for myPOS terminals which are already subscribed. Within the response of MPRSubscribe call, the partner will receive a security code generated for the particular Terminal ID (TID). The code must be entered on the myPOS device in order to complete the subscription. With a successful pair, the myPOS device will switch from ‘Standalone’ mode to ‘Cash register’ mode.

Method properties

PropertyTypical valueTypePresenceDescription
version3.0StringMThe version of the protocol used for transition.
loginname@website.comStringMIdentifier of the partner.
key_index1IntMIdentifier of the private key used for the signature.
tid90000015AN(8)MTerminal ID
ruid201203319999999StringMUnique identifier of the submitted request. Up to 255 characters.
currencyEURA(3)MISO 3-character currency code. It must match the currency of the terminal. Otherwise, the call will return an error.
action1N(1)M1 - Subscribe TID for the service; 2 - Cancellation of the subscription.
signatureByte[]BASE64MSHA-256 HASH for all properties in the command signed with the private key. The signature parameter is not used to calculate the hash.

Response properties

PropertyTypical valueTypePresenceDescription
version3.0StringMEEcho from MPRSubscribe.
loginname@website.comStringMEEcho from MPRSubscribe.
key_index1IntMEEcho from MPRSubscribe.
tid90000015AN(8)MEEcho from MPRSubscribe.
ruid201203319999999StringMEEcho from MPRSubscribe.
currencyEURA(3)MEEcho from MPRSubscribe.
action1N(1)MEEcho from MPRSubscribe.
code78025608N(8)MThis security code must be entered on the myPOS device in order to complete the subscription or to confirm the cancellation of the subscription.
status0N(2)MStatus of the request. For more information check Status Messages.
status_msgOKStringOAdditional details about the received status.
signatureByte[]BASE64MSHA-256 HASH for all properties in the command signed with the private key. The signature parameter is not used to calculate the hash.

Example of the request (The elements must follow this order):

<urn:MPRSubscribe xmlns:urn="urnIPayService">
  <urn:version>3.0</urn:version>
  <urn:login>name@website.com</urn:login>
  <urn:key_index>1</urn:key_index>
  <urn:tid>90000015</urn:tid>
  <urn:ruid>201203319999999</urn:ruid>
  <urn:currency>EUR</urn:currency>
  <urn:action>1</urn:action>      
  <urn:signature>bUViE5SzWy9iYpWzxlEVO/8Yb6bvtJVn1P6/rat5NBdgJaBU7OxeRm8rxi/fW1xuekqDM06F4MbzUPnTIA/sZ1ZwlMjSTExY5+7DqkdejN7mDgnB8zogrOfF6/P1snxuNgPRtHuJ0ZeTdTWNm9kKPGE7IadvIGtOpF+7yspfWd4=</urn:signature>
</urn:MPRSubscribe>

Example of the response:

<MPRSubscribeResponse xmlns:urn="urnIPayService"> 
  <MPRSubscribeResult xmlns:a="http://schemas.datacontract.org/2004/07/iPay.Core" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">  
    <a:version>3.0</a:version> 
    <a:login>name@website.com</a:login> 
    <a:key_index>1</a:key_index>
    <a:tid>90000015</a:tid> 
    <a:ruid>201203319999999</a:ruid> 
    <a:currency>EUR</a:currency> 
    <a:action>1</a:action> 
    <a:code>78025608</a:code> 
    <a:status>0</a:status> 
    <a:status_msg>OK</a:status_msg> 
    <a:signature> bUViE5SzWy9iYpWzxlEVO/8Yb6bvtJVn1P6/rat5NBdgJaBU7OxeRm8rxi/fW1xuekqDM06F4MbzUPnTIA/sZ1ZwlMjSTExY5+7DqkdejN7mDgnB8zogrOfF6/P1snxuNgPRtHuJ0ZeTdTWNm9kKPGE7IadvIGtOpF+7yspfWd4=</a:signature> 
  </MPRSubscribeResult> 
</MPRSubscribeResponse>