Void and refund

Void (reversal)

You can cancel the following transaction types before end of day:

  • Sale (purchase)
  • Return (linked refund)
  • Credit (naked refund)
  • Initial preauthorisation
  • All transactions realted to a preauthorisation (excluding the preauthorisation completion)
  • Preauthorisation completion (post authorisation)

There are 3 options to cancel a transaction via nexo using:

  • AcceptorCompletionAdviceV06 - caaa.003.001.06, description limited to cancellation and reversal scenarios
  • AcceptorCancellationRequestV06 - caaa.005.001.06
  • AcceptorCancellationAdviceV06 - caaa.007.001.06

Independent of the chosen message type, you would also need to consider the common elements of a nexo message,.

Use these tables together with the nexo Acquirer v6 Message Definition Report and the corresponding XSD.

Presence: m = mandatory, c = conditional, o = optional, - = not used by the Gateway for that message.

Message overview

MessagePurposeHow cancellation behavior is selected
AcceptorCompletionAdviceV06 (caaa.003.001.06)Reports that completion failed and that the preceding financial operation must be reversed.The Gateway evaluates TxCaptr, TxTp, TxSucss, and Rvsl. This document does not cover normal completion or post-authorisation.
AcceptorCancellationRequestV06 (caaa.005.001.06)Requests cancellation or asks whether a referenced transaction can still be cancelled.Tx/TxCaptr=true executes the cancellation. Tx/TxCaptr=false performs only an eligibility check.
AcceptorCancellationAdviceV06 (caaa.007.001.06)Advises that a completed transaction was cancelled or was not financially transferred or cleared.The message type itself selects cancellation-advice processing. TxSucss, Rvsl, and FailrRsn describe why the cancellation occurred.

Common elements

The following fields are common to the three messages. Message-specific transaction fields are documented in the later sections.

TagDescriptionCompletion AdviceCancellation RequestCancellation Advice
Hdr/PrtcolVrsnProtocol version. Use 6.0.mmm
Hdr/XchgIdExchange ID assigned by the terminal for this message.mmm
Hdr/ReTrnsmssnCntrRetransmission counter.o-o
Hdr/CreDtTmDate and time when the message was created. Include a timezone.mmm
Hdr/InitgPty/IdIdentifies the sending terminal host or application.mmm
Hdr/RcptPty/IdIdentifies the configured Gateway recipient.ooo
Hdr/Tracblt/...Optional traceability information.ooo
Envt/Acqrr/Id/IdAcquirer ID. The Gateway requires the value even where the XSD marks its parent block optional.mmm
Envt/Acqrr/ParamsVrsnVersion or load timestamp of the parameters used by the terminal.mmm
Envt/Mrchnt/Id/IdMerchant ID. The Gateway requires the value even where the XSD marks its parent block optional.mmm
Envt/Mrchnt/CmonNmMerchant name supplied by the terminal.ooo
Envt/Mrchnt/LctnAndCtct/PstlAdr/...Merchant address. If PstlAdr is present, TwnNm and Ctry are required by the XSD.ooo
Envt/Mrchnt/LctnAndCtct/AddtlCtctInfAdditional merchant contact, station, or tenant information.ooo
Envt/POI/Id/IdTerminal ID.mmm
Envt/POI/Id/ShrtNmGateway terminal ID when it differs from the acquirer terminal ID, for example in a Girocard setup.ooo
Envt/POI/GrpIdGateway store or POI group ID.ooo
Envt/POI/CpbltiesPOI capabilities block. The Gateway requires this block.mmm
Envt/POI/Cpblties/CardRdngCpbltiesCard-reading capabilities supported by the POI.ooo
Envt/POI/Cpblties/CrdhldrVrfctnCpbltiesCardholder-verification capabilities supported by the POI.ooo
Envt/POI/Cpblties/OnLineCpbltiesPOI online capability. ONLN means online, OFLN means offline, and an absent or different value permits both.ooo
Envt/POI/Cpblties/MsgCpblties/DstnMessage destination. CRDO requests the electronic-receipt indicator. The other destination values do not change cancellation routing.ooo
Envt/POI/Cpblties/MsgCpblties/AvlblFrmtAccepted by the XSD but not evaluated for cancellation processing.---
Envt/POI/Cpblties/MsgCpblties/NbOfLinesAccepted by the XSD but not evaluated for cancellation processing.---
Envt/POI/Cpblties/MsgCpblties/LineWidthAccepted by the XSD but not evaluated for cancellation processing.---
Envt/POI/Cpblties/MsgCpblties/AvlblLangAccepted by the XSD but not evaluated for cancellation processing.---
Envt/POI/Cmpnt/...Optional terminal, device, response-capability, or operating-system information.
See: link
ooo
Envt/CardCard environment block. It is optional for Completion Advice and mandatory in the Cancellation Request and Cancellation Advice XSDs. Copying the original card brand and applicable card data is recommended.omm
Envt/Card/PrtctdCardData/...Protected card data. Use this form when card data must be supplied in production.ccc
Envt/Card/PlainCardData/...Plain PAN, expiry date, sequence number, or track data. Use only in non-production testing; do not send clear card data in production.ccc
Envt/Card/IssrBINIssuer BIN.ooo
Envt/Card/CardCtryCdCard country code.ooo
Envt/Card/CardCcyCdCard currency code.ooo
Envt/Card/CardPdctPrflCard product profile used for grouping and reconciliation.ooo
Envt/Card/CardBrndCard brand. Copy the value from the original transaction when available.ooo
Cntxt/PmtCntxtPayment context block. The Gateway requires this block.mmm
Cntxt/PmtCntxt/CardPresIndicates whether the card was present.ooo
Cntxt/PmtCntxt/CrdhldrPresIndicates whether the cardholder was present.ooo
Cntxt/PmtCntxt/OnLineCntxtIndicates whether the original processing context was online.o-o
Cntxt/PmtCntxt/AttndncCntxtAttendance context. When absent, the Gateway treats the transaction as attended.ooo
Cntxt/PmtCntxt/TxChanlTransaction channel. It is considered for Completion Advice but not for the two cancellation messages.o--
Cntxt/PmtCntxt/CardDataNtryMdCard-data entry mode. The Gateway requires this field.mmm
Cntxt/PmtCntxt/FllbckIndFallback indicator: FFLB, SFLB, or NFLB.ooo
Cntxt/SaleCntxt/SaleIdSale system or workstation ID.ooo
Cntxt/SaleCntxt/CshrIdOperator or cashier ID.ooo
Cntxt/SaleCntxt/InvcNbInvoice number used for reporting.ooo
Tx/MrchntCtgyCdMerchant category code.mmm
Tx/CardPrgrmmPropsdCard programme proposed by the terminal.ooo
Tx/TxId/TxDtTmDate and time of the current message. Include a timezone.mmm
Tx/TxId/TxRefReference ID of the current message.mmm
Tx/InitrTxIdInitiator transaction ID used for correlation.ooo
Tx/RcncltnIdReconciliation ID associated with the message.ooo
Tx/TxDtls/CcyTransaction currency. It is mandatory in Completion Advice and optional in the cancellation message XSDs. Copy the original currency when known.moo
Tx/TxDtls/TtlAmtTotal amount. If the amount is unknown for a cancellation, send 0; the Gateway then uses the referenced transaction amount.mmm
Tx/TxDtls/ICCRltdDataEMV data, when applicable.ooo
SctyTrlr/AuthntcdDataMessage Authentication Value. Send it when message security or MAC validation is enabled for the connection.mmm

Acceptor Cancellation Advice

AcceptorCancellationAdviceV06 - caaa.007.001.06

Root path: Document/AccptrCxlAdvc/CxlAdvc

The message type itself selects cancellation-advice processing. The transaction-result fields describe whether the advice represents an explicit cancellation or a failure-driven automatic void.

Cancellation conventions

ScenarioTxSucssRvslFailrRsn
Explicit cancellationtruetrueOmit
Terminal failure or automatic voidfalsetrueSupply at least one recognized reason

Message-specific elements

TagDescriptionPresence
Hdr/MsgFctnIdentifies an Acceptor Cancellation Advice. Use CCAV.m
Tx/SaleRefIdOrder ID of the original transaction. Use it when the complete Tx/OrgnlTx key is not supplied. The order must already exist in the Gateway.c
Tx/OrgnlTxIdentifies the transaction to cancel. Supply this block unless Tx/SaleRefId identifies the existing Gateway order. The complete original key is the least ambiguous option.c
Tx/OrgnlTx/TxId/TxDtTmDate and time of the original transaction. Mandatory within OrgnlTx.c
Tx/OrgnlTx/TxId/TxRefReference ID of the original transaction. Mandatory within OrgnlTx.c
Tx/OrgnlTx/POIId/IdTerminal ID of the original transaction. Required when the original terminal differs from the current terminal and recommended for an unambiguous lookup.c
Tx/OrgnlTx/POIId/ShrtNmOriginal Gateway terminal ID when it differs from the acquirer terminal ID.o
Tx/OrgnlTx/RcptTxIdOriginal recipient transaction ID. A complete OrgnlTx/TxId key takes lookup precedence.o
Tx/OrgnlTx/TxTpTransaction type of the original transaction. Mandatory within OrgnlTx; normally use CRDP for a card payment or RESA for a reservation or pre-authorisation.c
Tx/TxSucssUse true for an explicit cancellation and false for a terminal-failure or automatic-void scenario.m
Tx/RvslReversal indicator. Use true.m
Tx/FailrRsnRequired when TxSucss=false; omit for an explicit cancellation. See Failure reasons.c
Tx/RcptTxIdThis current-message field is not used by the Gateway for Cancellation Advice. Use Tx/OrgnlTx or Tx/SaleRefId to identify the original transaction.-

Cancellation Advice response

AcceptorCancellationAdviceResponseV06 (caaa.008.001.06) does not contain Tx/TxDtls. It therefore cannot return the amount actually voided or reversed. A terminal that needs the final cancellation amount must use Acceptor Cancellation Request and process the corresponding caaa.006.001.06 response.

Acceptor Cancellation Request

AcceptorCancellationRequestV06 - caaa.005.001.06

Root path: Document/AccptrCxlReq/CxlReq

Cancellation behavior

Tx/TxCaptrResult
trueThe Gateway creates and submits the cancellation or void for the referenced transaction.
falseThe Gateway only checks whether the referenced transaction can still be cancelled. No cancellation is submitted.

Message-specific elements

TagDescriptionPresence
Hdr/MsgFctnIdentifies an Acceptor Cancellation Request. Use CCAQ.m
Tx/TxCaptrSelects execution or eligibility check. Although optional in the XSD, the Gateway requires the value.m
Tx/SaleRefIdOrder ID associated with the referenced transaction.o
Tx/OrgnlTxIdentifies the transaction to check or cancel. This block is mandatory in caaa.005.001.06.m
Tx/OrgnlTx/TxId/TxDtTmDate and time of the original transaction.

If Tx/OrgnlTx/TxId/TxDtTm is unknow, use the same value as Tx/TxId/TxDtTm

If those values are identical, then the Gateway will use one of the following XML tags (depending on presence):
Tx/OrgnlTx/RcptTxId
Tx/RcptTxId
Tx/SaleRefId
m
Tx/OrgnlTx/TxId/TxRefReference ID of the original transaction.

If Tx/OrgnlTx/TxId/TxRef is unknow, use the same value as Tx/TxId/TxRef

If those values are identical, then the Gateway will use one of the following XML tags (depending on presence):
Tx/OrgnlTx/RcptTxId
Tx/RcptTxId
Tx/SaleRefId
m
Tx/OrgnlTx/POIId/IdTerminal ID of the original transaction. Required when it differs from the current terminal and recommended for an unambiguous lookup.c
Tx/OrgnlTx/POIId/ShrtNmOriginal Gateway terminal ID when it differs from the acquirer terminal ID.o
Tx/OrgnlTx/RcptTxIdOriginal recipient transaction ID.o
Tx/OrgnlTx/TxTpTransaction type of the original transaction. This value is mandatory within OrgnlTx.m
Tx/RcptTxIdRecipient transaction ID associated with the current request. It can carry a Gateway transaction or order identifier, but the complete original key takes precedence.o
Tx/TxTpNot part of the current transaction structure for caaa.005.001.06. The original transaction type belongs in Tx/OrgnlTx/TxTp.-
Tx/TxSucssNot part of the Cancellation Request transaction structure.-
Tx/RvslNot part of the Cancellation Request transaction structure.-
Tx/FailrRsnNot part of the Cancellation Request transaction structure.-

Cancellation Response and actual amount

AcceptorCancellationResponseV06 - caaa.006.001.06

Root path: Document/AccptrCxlRspn/CxlRspn

The following response rule is planned for release 26.04. It is not yet confirmed as deployed.

After an approved Tx/TxCaptr=true cancellation, the Gateway returns the amount that was actually voided, reversed, or returned in Tx/TxDtls/TtlAmt. The response reports the final approved amount rather than simply echoing the amount submitted in the request.

Request or processing resultcaaa.006 response behavior
The request contains the correct non-zero amountTx/TxDtls/TtlAmt contains the final approved cancellation amount, which will normally equal the submitted amount.
The request contains Tx/TxDtls/TtlAmt=0 because the amount is unknownThe Gateway resolves the applicable amount from the referenced transaction and replaces zero with the amount actually cancelled.
A full or partial pre-authorisation void changes the effective amountThe response contains the final amount approved by the Gateway after the void amount has been determined.
The cancellation is processed as a returnThe response contains the amount actually returned.
Tx/TxCaptr=false requests only an eligibility checkNo cancellation is executed; the actual-cancellation-amount rule does not apply.
Response tagDescriptionPresence
Tx/TxDtls/CcyCurrency of the final approved cancellation amount.m
Tx/TxDtls/TtlAmtAmount actually voided, reversed, or returned after successful cancellation processing.m

Acceptor Completion Advice used for cancellation or reversal

AcceptorCompletionAdviceV06 - caaa.003.001.06

Root path: Document/AccptrCmpltnAdvc/CmpltnAdvc

This section covers only cancellation and reversal. It intentionally excludes successful completion, post-authorisation, and pre-authorisation completion.

Cancellation behavior

ScenarioTxCaptrTxTpTxSucssRvslFailrRsnResult
Failed financial completion requiring automatic reversaltrueCRDP or CAFTfalsetrueSupply a recognized reasonThe Gateway reverses the referenced operation.
Failed non-capture completion reported as cancellation advicefalseCRDP or CAFTfalseDoes not select this pathOptionalThe Gateway processes the message as cancellation advice.

For an automatic reversal, a recognized FailrRsn preserves the actual failure cause. If it is omitted, the Gateway can use a generic customer-cancellation reason.

Message-specific elements

TagDescriptionPresence
Hdr/MsgFctnUse RVRA for reversal advice without financial capture or FRVA for financial reversal advice. The transaction fields, rather than this value alone, determine cancellation behavior.m
Tx/TxCaptrUse true for the failed financial completion that must be reversed. Use false with TxSucss=false for cancellation-advice behavior. Although optional in the XSD, the Gateway requires the value.m
Tx/TxTpTransaction type. For the cancellation scenarios covered here, use CRDP or CAFT as applicable.m
Tx/SaleRefIdExisting Gateway order ID that can identify the original transaction.c
Tx/OrgnlTxExplicit original-transaction reference. Supply it unless another supported identifier or the current transaction key intentionally identifies the original transaction.c
Tx/OrgnlTx/TxId/TxDtTmDate and time of the original transaction. Mandatory when OrgnlTx is present.c
Tx/OrgnlTx/TxId/TxRefReference ID of the original transaction. Mandatory when OrgnlTx is present.c
Tx/OrgnlTx/POIId/IdTerminal ID of the original transaction. Required when it differs from the current terminal and recommended for an unambiguous lookup.c
Tx/OrgnlTx/POIId/ShrtNmOriginal Gateway terminal ID when it differs from the acquirer terminal ID.o
Tx/OrgnlTx/RcptTxIdOriginal recipient transaction ID.o
Tx/OrgnlTx/TxTpTransaction type of the original transaction. Mandatory when OrgnlTx is present.c
Tx/TxSucssUse false for the cancellation and reversal scenarios covered here.m
Tx/RvslUse true for automatic reversal. It does not select the failed non-capture cancellation-advice path.c
Tx/FailrRsnSupply at least one recognized reason for automatic reversal so the Gateway retains the actual cause. See Failure reasons.c
Tx/RcptTxIdGateway transaction or order identifier for the current message. It can be used when no complete original key is supplied.o

Original-transaction lookup

All executing cancellation and reversal paths must resolve the original transaction.

PriorityInformationUsage
1Minimum:
Tx/OrgnlTx/TxId/TxRef& Tx/OrgnlTx/TxId/TxDtTm,
and
Tx/OrgnlTx/POIId/Id (&Tx/OrgnlTx/POIId/ShrtNm if used in original transaction)
and
Tx/OrgnlTx/TxTp
This is the preferred and least ambiguous original key.
2Tx/OrgnlTx/RcptTxId along with Tx/OrgnlTx/TxId/...
or
Tx/RcptTxId
or
Tx/SaleRefId
These values can identify an existing Gateway transaction or order when no complete original key is supplied.
3Current Tx/TxId/TxRef, current Tx/TxId/TxDtTm, and the terminal IDCompletion Advice automatic reversal can use this fallback when the current transaction key intentionally matches the original.

When both an original key and another identifier are present, the complete original key takes precedence.

Amount and processing behavior

SituationExpected behavior
Original amount is knownSend the original amount and currency. A non-zero amount should match the referenced transaction.
Original amount is unknownSend Tx/TxDtls/TtlAmt=0. The Gateway treats the amount as unspecified and uses the referenced transaction amount for cancellation. For Acceptor Cancellation Request, the planned caaa.006 response behavior returns the amount actually cancelled.
Transaction has already settledWhere the applicable configuration permits it, the Gateway can process the requested cancellation as a return.

Failure reasons

Failure reasons apply to Completion Advice and Cancellation Advice. Cancellation Request does not contain Tx/FailrRsn.

CodeMeaningGateway treatment
CDCLCard declinedPreserved as a dedicated cancellation reason
CUCLCustomer cancelledPreserved as a dedicated cancellation reason
MALFMalfunctionPreserved as a dedicated cancellation reason
PARTPartially completedPreserved as a dedicated cancellation reason
TIMOTimeoutPreserved as a dedicated cancellation reason
FDCLOffline declineTreated as a technical-error cancellation reason
NDCLOnline declineTreated as a technical-error cancellation reason
SFRDSuspected fraudTreated as a technical-error cancellation reason
LATEResponse too lateTreated as a technical-error cancellation reason
UCMPUnable to completeTreated as a technical-error cancellation reason
USNDUnable to sendTreated as a technical-error cancellation reason
SECUSecurity errorTreated as a technical-error cancellation reason

Refund

This document describes the business-relevant elements used by the Gateway for linked and naked refunds with these nexo Acquirer v6 messages:

  • AcceptorAuthorisationRequestV06 - caaa.001.001.06, used for an online refund
  • AcceptorAuthorisationResponseV06 - caaa.002.001.06, containing the authorisation result
  • AcceptorCompletionAdviceV06 - caaa.003.001.06, used for a successful offline refund advice
  • AcceptorCompletionAdviceResponseV06 - caaa.004.001.06, acknowledging the advice

In Gateway terminology, a return is a linked refund against an existing Sale and a credit is a naked refund without an original transaction reference.

Use these tables together with the nexo Acquirer v6 Message Definition Report and the corresponding XSD.

Presence: m = mandatory, c = conditional, o = optional, - = not used by the Gateway for that message.

Refund scenario selection

ScenarioOriginal referenceGateway processing
Linked refund (return)Supply Tx/OrgnlTx or Tx/SaleRefId so the Gateway can resolve an existing Sale.Creates a full or partial refund linked to the original Sale.
Naked refund (credit)Omit Tx/OrgnlTx and Tx/SaleRefId.Creates an independent credit without locating an original Sale.

Both scenarios use Tx/TxCaptr=true and Tx/TxTp=RFND. The presence of a supported original-transaction or order reference selects a linked refund; the absence of all such references selects a naked refund.

If any original or order reference is supplied, the Gateway treats the message as linked. If the referenced transaction cannot be found, the Gateway rejects the message instead of silently processing it as a naked refund.

Message overview

MessagePurposeRefund selection
AcceptorAuthorisationRequestV06 (caaa.001.001.06)Requests online authorisation and immediate capture of a refund.Use Hdr/MsgFctn=FAUQ, Tx/TxCaptr=true, and Tx/TxTp=RFND. A reference selects a linked refund.
AcceptorAuthorisationResponseV06 (caaa.002.001.06)Returns the approved, partially approved, or declined refund result.The response to FAUQ uses Hdr/MsgFctn=FAUP.
AcceptorCompletionAdviceV06 (caaa.003.001.06)Reports a successful offline refund.Use Hdr/MsgFctn=FCMV, Tx/TxCaptr=true, Tx/TxTp=RFND, and Tx/TxSucss=true. A reference selects a linked refund advice.
AcceptorCompletionAdviceResponseV06 (caaa.004.001.06)Acknowledges that the refund advice was accepted and processed.The response to FCMV uses Hdr/MsgFctn=FCMK.

Common request and advice elements

The following fields are common to the online refund request and the successful refund completion advice. Message-specific fields are documented later.

TagDescriptionAuthorisation RequestCompletion Advice
Hdr/PrtcolVrsnProtocol version. Use 6.0.mm
Hdr/XchgIdExchange ID assigned by the terminal for this message.mm
Hdr/ReTrnsmssnCntrRetransmission counter. It is not part of caaa.001; use it in an advice retry when applicable.-o
Hdr/CreDtTmDate and time when the message was created. Include a timezone.mm
Hdr/InitgPty/IdIdentifies the sending terminal host or application.mm
Hdr/RcptPty/IdIdentifies the configured Gateway recipient.oo
Hdr/RcptPty/RmotAccs/AccsCdRemote-access or one-time access code when required by the configured payment flow.oo
Hdr/Tracblt/...Optional traceability information.oo
Envt/Acqrr/Id/IdAcquirer ID. The Gateway requires the value even though the XSD marks the acquirer block optional.mm
Envt/Acqrr/ParamsVrsnVersion or load timestamp of the parameters used by the terminal.mm
Envt/Mrchnt/Id/IdMerchant ID. The Gateway requires the value even though the XSD marks the merchant block optional.mm
Envt/Mrchnt/CmonNmMerchant name supplied by the terminal.oo
Envt/Mrchnt/LctnCtgyMerchant-location category. NMDC identifies a nomadic merchant and makes the supplied address the service location.oo
Envt/Mrchnt/LctnAndCtct/PstlAdr/...Merchant or service-location address. If the postal-address block is present, supply its required XSD fields.oo
Envt/Mrchnt/LctnAndCtct/AddtlCtctInfAdditional merchant contact, station, or tenant information.oo
Envt/POI/Id/IdTerminal ID.mm
Envt/POI/Id/ShrtNmGateway terminal ID when it differs from the acquirer terminal ID.oo
Envt/POI/GrpIdGateway store or POI group ID.oo
Envt/POI/CpbltiesPOI capabilities block. The Gateway requires this block.mm
Envt/POI/Cpblties/CardRdngCpbltiesCard-reading capabilities supported by the POI.oo
Envt/POI/Cpblties/CrdhldrVrfctnCpbltiesCardholder-verification capabilities supported by the POI.oo
Envt/POI/Cpblties/OnLineCpbltiesPOI online capability. ONLN means online, OFLN means offline, and an absent or different value permits both.oo
Envt/POI/Cpblties/MsgCpblties/DstnMessage destination. CRDO requests the electronic-receipt indicator.oo
Envt/POI/Cmpnt/...Optional terminal serial number, type, provider, device, response-capability, or operating-system information.oo
Envt/CardCard environment block. It is mandatory in caaa.001 and optional in caaa.003. A naked refund must contain sufficient card or token data for processing.mc
Envt/Card/PrtctdCardData/...Protected card data. Use this form when card data must be supplied in production.cc
Envt/Card/PlainCardData/...PAN, expiry date, sequence number, or track data. Use clear card data only in an appropriately secured non-production test.cc
Envt/Card/PmtAcctRefPayment account reference or supported hosted-data identifier.oo
Envt/Card/IssrBINIssuer BIN.oo
Envt/Card/CardCtryCdCard country code.oo
Envt/Card/CardCcyCdCard currency code.oo
Envt/Card/CardPdctPrflCard product profile used for grouping and reconciliation.oo
Envt/Card/CardBrndCard brand. For a linked refund, copy the original brand when available.oo
Envt/Crdhldr/NmCardholder name.oo
Envt/Crdhldr/BllgAdr/...Billing address used when address-verification data is applicable.oo
Cntxt/PmtCntxtPayment context block. The Gateway requires this block.mm
Cntxt/PmtCntxt/CardPresIndicates whether the card was present for the refund.oo
Cntxt/PmtCntxt/CrdhldrPresIndicates whether the cardholder was present.oo
Cntxt/PmtCntxt/OnLineCntxtIndicates whether the processing context was online. It is available only in the Completion Advice structure.-o
Cntxt/PmtCntxt/AttndncCntxtAttendance context. When absent, the Gateway treats the transaction as attended.oo
Cntxt/PmtCntxt/TxChanlTransaction channel.oo
Cntxt/PmtCntxt/CardDataNtryMdCard-data entry mode. The Gateway requires this field.mm
Cntxt/PmtCntxt/FllbckIndFallback indicator: FFLB, SFLB, or NFLB.oo
Cntxt/PmtCntxt/SpprtdOptnSupported payment options understood by the terminal. The Gateway consumes this field from the Authorisation Request but not from Completion Advice.o-
Cntxt/SaleCntxt/SaleIdSale system or workstation ID used for transaction reporting and downstream feeds.oo
Cntxt/SaleCntxt/CshrIdOperator or cashier ID.oo
Cntxt/SaleCntxt/InvcNbInvoice number used for reporting.oo
Cntxt/SaleCntxt/SpnsrdMrchnt/...Sponsored merchant information.oo
Tx/MrchntCtgyCdMerchant category code.mm
Tx/CardPrgrmmPropsdCard programme proposed by the terminal.oo
Tx/TxId/TxDtTmDate and time of this refund transaction. Include a timezone.mm
Tx/TxId/TxRefTerminal-assigned reference of this refund. It must be unique within the applicable terminal and time scope.mm
Tx/InitrTxIdInitiator transaction ID used for correlation.oo
Tx/RcncltnIdReconciliation ID associated with the refund.oo
Tx/TxDtls/CcyRefund currency. For a linked refund, it must match the original transaction currency.mm
Tx/TxDtls/TtlAmtAmount to refund. Use the requested partial amount or the full remaining refundable amount.mm
Tx/TxDtls/AmtQlfrAmount qualifier for a supported specialised scenario. Omit for an ordinary refund.oo
Tx/TxDtls/DtldAmt/AmtGoodsAndSvcsGoods-and-services portion of the refund amount.oo
Tx/TxDtls/AcctTpCard account type, when selected.oo
Tx/TxDtls/UattnddLvlCtgyUnattended-level category.oo
Tx/TxDtls/SaleItmReturned product or basket items. See Refund item details.oo
Tx/TxDtls/ICCRltdDataEMV data, when applicable.oo
Tx/AddtlTxDataAdditional transaction data supported for the applicable payment scenario.oo
SctyTrlr/AuthntcdDataMessage Authentication Value. Send it when message security or MAC validation is enabled for the connection.oo

Acceptor Authorisation Request for an online refund

AcceptorAuthorisationRequestV06 - caaa.001.001.06

Root path: Document/AccptrAuthstnReq/AuthstnReq

Required refund values

TagValueDescriptionPresence
Hdr/MsgFctnFAUQFinancial authorisation request.m
Tx/TxCaptrtrueRequests immediate capture of the refund.m
Tx/TxTpRFNDRefund. The reference fields determine whether it is linked or naked.m

Linked refund reference fields

A linked refund must resolve an existing Gateway transaction. The complete original transaction key is the least ambiguous reference.

TagDescriptionPresence
Tx/OrgnlTxOriginal Sale reference. Supply the block for the preferred original-key or recipient-transaction-ID lookup.c
Tx/OrgnlTx/TxId/TxDtTmDate and time of the original Sale. Mandatory when OrgnlTx is present.c
Tx/OrgnlTx/TxId/TxRefTerminal reference of the original Sale. Mandatory when OrgnlTx is present.c
Tx/OrgnlTx/POIId/IdTerminal ID of the original Sale. Required when it differs from the current terminal and recommended for an unambiguous lookup.c
Tx/OrgnlTx/POIId/ShrtNmOriginal Gateway terminal ID when it differs from the acquirer terminal ID.o
Tx/OrgnlTx/RcptTxIdRecipient transaction ID returned for the original Sale. Depending on the configured response convention, this identifies either the Gateway transaction or its order.o
Tx/OrgnlTx/TxTpOriginal transaction type. It is mandatory within OrgnlTx; use CRDP when the original transaction was a Sale.c
Tx/SaleRefIdExisting Gateway order ID. Use this as an alternative when the complete original key is not supplied.c

At least one supported reference route must be usable. Merely supplying a partial or unknown reference does not convert the request into a naked refund.

Original-transaction lookup priority

PrioritySupplied informationGateway usage
1Tx/OrgnlTx/TxId/TxRef, Tx/OrgnlTx/TxId/TxDtTm, and the original POIId/ShrtNm or POIId/IdPreferred original-key lookup. If the original terminal is omitted, the current Gateway terminal is used.
2Tx/OrgnlTx/RcptTxIdUses the recipient identifier returned for the original Sale. Its interpretation follows the terminal's configured recipient-ID convention.
3Tx/SaleRefIdUses the existing Gateway order ID.

When a complete original key and another identifier are both present, the complete original key takes precedence.

Naked refund fields

RequirementExpected value or behavior
Original transactionOmit Tx/OrgnlTx.
Existing order referenceOmit Tx/SaleRefId.
Card dataSupply sufficient protected card, hosted-data, token, or other supported payment data to identify the refund destination. There is no original Sale from which it can be resolved.
Refund amount and currencySupply the independent credit amount and its currency in Tx/TxDtls.
Current transaction keyUse a new, unique Tx/TxId/TxRef and the current Tx/TxId/TxDtTm. Do not reuse a Sale key.

Naked refunds are subject to the store, brand, processor, and payment-method configuration that permits independent credits.

Acceptor Completion Advice for a successful refund

AcceptorCompletionAdviceV06 - caaa.003.001.06

Root path: Document/AccptrCmpltnAdvc/CmpltnAdvc

Required successful-refund values

TagValueDescriptionPresence
Hdr/MsgFctnFCMVFinancial completion advice.m
Tx/TxCaptrtrueIndicates financial capture. Although optional in the XSD, the Gateway requires it.m
Tx/TxTpRFNDRefund.m
Tx/TxSucsstrueIndicates that the terminal-side refund succeeded.m
Tx/Rvslfalse or omitIndicates that this is a successful refund, not a reversal of a refund.o

The same reference rule applies as for the Authorisation Request:

  • Tx/OrgnlTx or Tx/SaleRefId selects a linked refund advice.
  • Omitting all original and order references selects a naked refund advice.
  • A supplied reference that cannot be resolved causes rejection; it does not fall back to a naked refund.

Failed or reversed refund advice is a cancellation or reversal scenario and is outside the scope of this document.

Authorisation Response

AcceptorAuthorisationResponseV06 - caaa.002.001.06

Root path: Document/AccptrAuthstnRspn/AuthstnRspn

The response to a financial refund request uses Hdr/MsgFctn=FAUP.

Response tagDescriptionPresence
Tx/TxId/TxDtTmDate and time of the refund request.m
Tx/TxId/TxRefTransaction reference copied from the request.m
Tx/RcptTxIdRecipient transaction ID assigned by the Gateway when available. Retain it for later correlation or cancellation.o
Tx/SaleRefIdSale or order reference associated with the refund.o
Tx/TxDtls/CcyCurrency associated with the processed refund.m
Tx/TxDtls/TtlAmtAmount associated with the processed refund. For a partial approval, use the returned amount rather than assuming the full requested amount was approved.m
Tx/TxDtls/DtldAmt/...Returned detailed amount information when available.o
Tx/TxDtls/ICCRltdDataEMV response data that the terminal must pass to the card when applicable.o
Tx/IntrchngDataScheme transaction identifier when returned by the processor.o
TxRspn/AuthstnRslt/AuthstnNtty/TpIdentifies whether the authorisation entity was the card issuer or an intermediary.o
TxRspn/AuthstnRslt/RspnToAuthstn/RspnAPPR = approved, PART = partially approved, DECL = declined.m
TxRspn/AuthstnRslt/RspnToAuthstn/RspnRsnResponse reason, limited to the nexo field length.o
TxRspn/AuthstnRslt/RspnToAuthstn/AddtlRspnInfAdditional processor or Gateway response information.o
TxRspn/AuthstnRslt/AuthstnCdAuthorisation code, padded to the required response length when necessary.o
TxRspn/AuthstnRslt/CmpltnReqrdIndicates whether a later completion message is required. Honor the returned value.m
TxRspn/TxVrfctnRsltAVS, card-security-code, manual-verification, or supported payment-specific verification results.o
TxRspn/ActnTerminal action such as display, print, PIN retry, or fall-forward when required.o
Envt/Card/MskdPANMasked PAN when available.o
Envt/Card/CardBrndResolved card brand when available.o
Envt/Card/PmtAcctRefPayment account reference or supported token identifier when requested and available.o

DECL is a business authorisation result. A malformed, unsupported, or invalid nexo message can instead produce an Acceptor Rejection and should not be treated as an issuer decline.

Completion Advice Response

AcceptorCompletionAdviceResponseV06 - caaa.004.001.06

Root path: Document/AccptrCmpltnAdvcRspn/CmpltnAdvcRspn

The response to a financial refund advice uses Hdr/MsgFctn=FCMK.

Response tagDescriptionPresence
Tx/TxId/TxDtTmDate and time of the advised refund.m
Tx/TxId/TxRefTransaction reference copied from the advice.m
Tx/RcptTxIdRecipient transaction ID assigned by the Gateway when available.o
Tx/SaleRefIdSale or order reference associated with the refund advice.o
Tx/RspnAPPR when the advice was accepted and processed normally. This acknowledges the advice; it is not a new issuer authorisation decision.m
Envt/Card/MskdPANMasked PAN when available.o
Envt/Card/CardBrndResolved card brand when available.o
Envt/Card/PmtAcctRefPayment account reference when explicitly requested and available.o
TMSTrggrTerminal-management trigger when the Gateway requires the terminal to contact the TMS.o

Operational rules

RuleExpected behavior
Linked versus nakedAny supplied original or order reference selects linked-refund processing. Omit all such references only when an independent naked refund is intended.
Original referencePrefer the complete original transaction key. When the original terminal differs from the current terminal, include its terminal identifier.
Reference failureAn unknown or incomplete linked-refund reference is rejected; the Gateway does not downgrade it to a naked refund.
AmountA linked refund can be full or partial and is checked against the original transaction and its remaining refundable amount. A naked refund uses the independently requested credit amount.
CurrencyA linked refund must use the original transaction currency.
Unique transaction keyUse a new Tx/TxId/TxRef with the current timestamp. Reusing a transaction key can invoke duplicate-message handling.
Advice retryRetransmit the same Completion Advice with an incremented Hdr/ReTrnsmssnCntr; do not create a different business transaction for a transport retry.
Response handlingTreat APPR, PART, and DECL as distinct outcomes. For PART, use the returned amount and follow the terminal's partial-approval rules.
EMV completionWhen Tx/TxDtls/ICCRltdData is returned in caaa.002, pass the required issuer response data to the card.
SecurityProtect card and authentication data and send SctyTrlr when the connection is configured for message authentication.

Did this page help you?
Want a quick overview?