UpdateBearer

Update the specified card’s bearer details.

Request

Path parameters

terminalID

string,  10 characters,  required

The Paymentology issued terminal ID of the terminal requesting the transaction

reference

string,  1-255 characters,  required

The user defined reference to the card; for example a member id or wallet number

cardIdentifier

string,  1-20 characters,  required

The card number, sequence number or tracking number of the specified card

firstName

string,  0-50 characters,  required

The first name of the card bearer. Field is required but can accept empty string

lastName

string,  0-50 characters,  required

The last name of the card bearer. Field is required but can accept empty string

idOrPassport

string,  0-20 characters,  required

The ID or passport number of the card bearer. Field is required but can accept empty string

cellphoneNumber

string,  0-20 characters,  required

The cellphone number of the card bearer. Field is required but can accept empty string

streetAddress

string,  5 characters,  required

The street address of the card bearer. No special characters nor alphabetic, example “17014”

postalCode

string,  9 characters,  required

The postal code of the card bearer. This value is left-justified with right-space-fill, example”12345    “,”123456789”

cityAddress

string,  required

City or area of the card bearer.

countryAddress

string,  3 characters,  required

ISO Alpha code indicating the country. eg. GBR

emailAddress

string,  required

Email address of the card bearer.

transactionID

string,  1-255 characters,  required

Client generated Transaction ID to assist in identify transactions on the client side

transactionDate

date,  required

Client generated / local Transaction Date to assist in identifying transactions on the client side

checksum

string,  required

HMAC-SHA256 hashed signature of the concatenated method name with all argument values using the terminal password as private key

<methodCall>
  <methodName>UpdateBearer</methodName>
  <params>
    <param>
      <value>
        <string>terminal_equipo_id</string>
      </value>
    </param>
    <param>
      <value>
        <string>TTKTEST</string>
      </value>
    </param>
    <param>
      <value>
        <string>5555xxxxxxxx0858</string>
      </value>
    </param>
    <param>
      <value>
        <string>Foo</string>
      </value>
    </param>
    <param>
      <value>
        <string>of Woe</string>
      </value>
    </param>
    <param>
      <value>
        <string>123456</string>
      </value>
    </param>
    <param>
      <value>
        <string>14996970101</string>
      </value>
    </param>
    <param>
      <value>
        <string>Street President Lula, 13</string>
      </value>
    </param>
    <param>
      <value>
        <string>17400000</string>
      </value>
    </param>
    <param>
      <value>
        <string>Haron</string>
      </value>
    </param>
    <param>
      <value>
        <string>BRA</string>
      </value>
    </param>
    <param>
      <value>
        <string>foo.ofwoe@mail.com</string>
      </value>
    </param>
    <param>
      <value>
        <string>CUB_000001</string>
      </value>
    </param>
    <param>
      <value>
        <dateTime.iso8601>20221201T11:03:42</dateTime.iso8601>
      </value>
    </param>
    <param>
      <value>
        <string>5C2394F37EA077918525FA42D7E3D33CF69A410E</string>
      </value>
    </param>
  </params>
</methodCall>

 

Response

STATUS200 OK

Schema

resultCode

integer

Status code indicating transaction result

<?xml version=""1.0"" encoding=""UTF-8""?>
<methodResponse>
  <params>
    <param>
      <value>
        <struct>
          <member>
            <name>resultCode</name>
            <value>
              <int>1</int>
            </value>
          </member>
          <member>
            <name>resultText</name>
            <value>
              <string>Approved</string>
            </value>
          </member>
        </struct>
      </value>
    </param>
  </params>
</methodResponse>

 

Was this page helpful?

Are you ready to use our APIs

If you are not yet registered with us.

Still have questions? Contact us.