Skip to content

    Reversal Mobile POS

    Overview

    Request

    The URI is composed of two principal parameters.

    • scheme: neximpos
    • authority: reversal

    the following parameters are expected:

    NameDescriptionTypeMandatory
    amountAmount in centsintyes
    callerTrxIdIdentification string of the transaction within the third-party appStringyes
    sendTicketFlag that enables the display of the button send receiptboolean (true/false)no (default true)
    urlTicketFlag that enables the creation of the link to obtain the receipt imageboolean (true/false)no (default true)
    timestampData and time in the format "ddmmyyhhmm".Stringyes
    terminalIdTerminal id of the reversible transaction calculated.Stringyes
    callerNameString used to value the label of the “Torna A …” buttonStringyes
    uriURI on which to retrieve the transaction responseStringyes
    emailValue with which to pre-fill the email field on the send receipt screenStringno
    smsValue with which to pre-fill the sms field in the sending receipt screenStringno

    Example request

    neximpos://reversal?amount=1&timestamp=0912202317&callerName=Reversal&email=name.surn ame%40domain.it&sms=3344556951&callerTrxId=qwerty&terminalId=30350039&sendTicket=true &urlTicket=true&uri=demonexi%3A%2F%2Freversal

    Response

    The response call is composed of the following fields:

    • scheme: specified in the URI field shown above
    • authority: specified in the URI field shown above

    as for the query parameters, they are the following:

    NameDescriptionTypeMandatory
    callerTrxIdIdentification string of the transaction within the third-party appStringyes
    operationTypeThis field describe type of operationString (REVERSAL)yes
    resultThis field contains the result of the transactionintyes
    amountThe amount of the transactionintyes
    actionCodeCode assigned by the bank describing the reason of the refusal and inform the terminal of specific situations (see bit 39 in ISO8583); is “000” for approved transactionStringoptional *
    panPAN truncated with last 4 digit in clear. This field has a value only for approved transaction, null otherwise.Stringoptional *
    transactionTypeCard technology used:
    • “ICC” for EMV transaction;
    • “MAG” for magstripe transaction;
    • “CLI” for contactless transaction;
    This field has a value only for approved transaction, null otherwise.
    Stringoptional *
    authorizationNu mberThis field has a value only for approved transaction, null otherwiseStringoptional *
    timestampData and time in the format “ddmmyyhhmm”.
    This field has a value only for approved transaction, null otherwise.
    Stringoptional *
    * Valued only in the event of an approved or denied transaction

    ** Valued in relation to the urlTicket field of the request

    The result field can contain the following values:

    • 0: transaction approved
    • 9: pos not connected
    • 20: transaction canceled
    • 21: transaction denied
    • -1: invalid input parameters
    • -2: device not secure
    • -3: bluetooth off
    • -4: services not available
    • -5: deprecated app
    • -6: login required
    • -7: terminalId suspended
    • -8: terminalId absent
    • -9: terminalId not configured on POS
    • -10: POS connection timeout

    Example response

    demonexi://reversal?result=0&amount=1&callerTrxId=qwerty&operationType=REVERSAL&actionC ode=000&pan=533317******5938&transactionType=CLI&timestamp=0912202320&resultDescript ion=&cardTypeCVM=2&acquirerId=00000000003&stan=000003&operationNumber=000032&acqui rerName=NEXI%20%20%20%20%20%20%20%20%20%20%20%20&terminalId=30350039&mercha ntId=0000091%20%20%20%20%20%20%20%20&authorizationNumber=&urlTicket=https%3A%2F %2Fintapi.nexi.it%3A8443%2Fmpos%2Fmobile%2Fapi%2Fservices%2Forchestrator%2Freceipt%2Fvi ew%3Fid%3DDBFIEFJQIJKLPPOYBDEDGIIH

    Was this helpful?

    What was your feeling about it?