Additional Fields

Given the needs of each fintech vary, we have added a feature that allows a fintech to add any number of fields (from the list of allowed fields) to their payload. The additional fields will be sent in an extra field (additional fields) as key values pair for any configured field provided the field is present in the request ISO message.

IsoFieldJson Field Name
3processingCode
5amountSettle
7transmissionDateAndTime
9conversionRate
12timeLocal
13dateLocal
15dateSettle
16dateConverted
17draftCapture
18merchantType
19acquiringCountryCode
20panExtendedCountryCode
21forwardingInstitutionCode
22posEntryMode
24networkId
25posConditionCode
26pinCaptureCode
27authIdRespLength
29settlementFee
32acquiringInstitutionIdCode
33forwardingInstitutionIdCode
34panExtended
40serviceRestrictionCode
46additionalDataIso
47additionalDataNational
48additionalData
50currencyCodeSettlement
54additionalAmounts
57authLifeCycle
66settlementCode
67extendedPaymentCode
68receivingInstCountryCode
69settlementInstCountryCode
86amountCredit
87amountCreditReversal
88amountDebit
89amountDebitReversal
90originalDataElements
91fileUpdateCode
92fileSecurityCode
93responseIndicator
94serviceIndicator
95replacementAmounts
97amountNetSettle
98payee
99settleInstIdCode
100receivingInstIdCode
102fromAccount
103toAccount
104transactionDescription
118paymentNumber
119paymentNumberReversal
123posDataCode
127.3routingInfo
127.4posData
127.5serviceStationData
127.7checkData
127.8retentionData
127.9additionalNodeData
127.12terminalOwner
127.13posGeographicData
127.14sponsorBank
127.15addressVerificationData
127.16addressVerificationResult
127.17cardholderInfo
127.19bankDetails
127.20authorizerSettlementDate
127.21recordId
127.23payeeNameAndAddress
127.24payeeReference
127.26originalNode
127.27cardVerificationResult
127.29secure3DData
127.30secure3DResult
127.31issuerNetworkId
127.32ucafData
127.33extendedTranType