Guest Checkout Tokenization

As per Reserve Bank of India (RBI) compliance requirements, storing card on file data has been limited. As an alternative solution, a guest checkout transaction token provided by schemes have been introduced as Alternate IDs (Alt ID). In order to request Scheme Alt ID and cryptogram, you need to send an action request to the Gateway. The call to retrieve scheme ALT ID and cryptogram is made by our system automatically.

Please note that this feature is applicable for Mastercard, Visa and Amex only.

The following XML document represents an example of a request with minimal set of elements, as well as an example of a response in the second tab:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ipg="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:a1="http://ipg-online.com/ipgapi/schemas/a1" xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
    <soapenv:Header/>
    <soapenv:Body>
        <ns4:IPGApiActionRequest
xmlns:ns4="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:ns2="http://ipg-online.com/ipgapi/schemas/a1" xmlns:ns3="http://ipg-online.com/ipgapi/schemas/v1">
            <ns2:Action>
                <ns2:GetGuestCheckoutTokenCryptogram>
                    <ns2:StoreId>331164004</ns2:StoreId>
                    <ns2:CreditCardData>
                        <ns3:CardNumber>4895********2363</ns3:CardNumber>
                        <ns3:ExpMonth>12</ns3:ExpMonth>
                        <ns3:ExpYear>28</ns3:ExpYear>
                        <ns3:CardCodeValue>123</ns3:CardCodeValue>
                        <ns3:Brand>VISA</ns3:Brand>
                    </ns2:CreditCardData>
                    <ns3:Payment>
                        <ns3:ChargeTotal>16.98</ns3:ChargeTotal>
                        <ns3:Currency>INR</ns3:Currency>
                    </ns3:Payment>
                </ns2:GetGuestCheckoutTokenCryptogram>
            </ns2:Action>
        </ns4:IPGApiActionRequest>
    </soapenv:Body>
</soapenv:Envelope>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header/>
    <SOAP-ENV:Body>
        <ipgapi:IPGApiActionResponse xmlns:a1="http://ipg-online.com/ipgapi/schemas/a1" xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
           <ipgapi:successfully>true</ipgapi:successfully>
           <ipgapi:GuestCheckoutTokenData>
           <v1:GuestCheckoutTokenNumber>4769*****7926</v1:GuestCheckoutTokenNumber>
           <v1:ExpMonth>12</v1:ExpMonth>
           <v1:ExpYear>2027</v1:ExpYear>
           <v1:CardLast4>2363</v1:CardLast4>
           <v1:Brand>VISA</v1:Brand>
           <v1:GuestCheckoutTokenCryptogram>AgAAAAD1R+1oMTv2HNIIQRAAAAA=</v1:GuestCheckoutTokenCryptogram>
            </ipgapi:GuestCheckoutTokenData>
        </ipgapi:IPGApiActionResponse>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The table below represents the full list of parameters related to this functionality:

Path/NameXML Schema typeDescription
v1:NetworkToken/
v1:GuestCheckoutTokenData/
v1: GuestCheckoutTokenNumber/
xs:string
[0-9]{13,19}
Guest checkout token number
v1:NetworkToken/
v1:GuestCheckoutTokenData/
v1:ExpMonth
xs:stringGuest checkout token expiry month
v1:NetworkToken/
v1:GuestCheckoutTokenData/
v1:ExpYear
xs:string
[0-9]{2}
Guest checkout token expiry year
v1:NetworkToken/
v1:GuestCheckoutTokenData/
v1:CardLast4
xs:string
\d{4}
Last four digits of the original Card Number represented by the guest checkout token
v1:NetworkToken/
v1:GuestCheckoutTokenData/
v1:Brand
xs:stringAvailable values:
"AMEX"
"MASTERCARD"
"VISA"
v1:NetworkToken/
v1: GuestCheckoutTokenData/
v1: GuestCheckoutTokenCryptogram
xs:string
minLength value="20
maxLength value="255"
Guest checkout token cryptogram as assigned by a scheme.

Want a quick overview?