Assembling the JSON with Business Data Content
RTP data content for IBAN:
{
"paymentRequestData":{
"creditorAccount":{
"iban":"HU43120103740145832700100007"
},
"creditorIdentification":{
"identificationType":"ORG-OTHR",
"identification":" identification"
},
"paymentInformationId":
"GIROT01265350",
"categoryPurpose":{
"categoryPurposeCode":"EPAY"
},
"paymentRequests":[
{
"expiryDateTime":
"2025-10-05T12:38:20.876Z",
"instructionIdentification":
"GIROT6452487",
"instructionPriority":"HIGH",
"instructedAmount":{
"currency":"HUF",
"amount":"100"
},
"amountModificationAllowed":"false",
"chargeBearer":"SLEV",
"ultimateDebtorName":"Minta Péter",
"ultimateDebtorIdentification":{
"identificationType":"ORG-OTHR",
"identification":"abc123"
},
"debtorName":"Kovács Béla",
"debtorAddress":{
"country":"HU",
"address":"Táncsics utca 1"
},
"debtorIdentification":{
"identificationType":"ORG-OTHR",
"identification":"xyz"
},
"debtorAccount":{
"iban":
"HU77120836000041718100100009"
},
"ultimateCreditorName":"Tóth Tibor",
"ultimateCreditorIdentification":{
"identificationType":"ORG-OTHR",
"identification":"1234-abc"
},
"purposeCode":"EPAY",
"regulatoryReporting":{
"invoiceIdentification":"INV-0120120",
"customerIdentification":"custid-3981723",
"credTranIdentification":
"GIROT1300052 ",
"loyaltyIdentification":"1",
"navCheckIdentification":"2",
"latestDateTime":"2025-10-04T12:38:20.877Z "
},
"remittanceInformationUnstructured":"Felhasználói kézikönyv - közlemény mező"
}
]
}
}
For secondary identifier:
proxyType
TELE +36-301234567
EMAL user@host.com
TXNB 10198014 (company tax number)
TXID 8463016669 (individual tax identifier)
proxyId
the secondary identifier value must be provided in this field
IBAN and proxy (secondary identifier) cannot be provided simultaneously
Field Descriptions
| Field name | Content | Description |
|---|---|---|
paymentRequestData | Payment request data | |
creditorAccount | Creditor's account | The unique identifier of the creditor's account to be credited. |
iban | Creditor's account in IBAN format | The creditor's international bank account number. In Hungary it is a 28-character number string always starting with HU; the last 24 characters match the domestic account number if it is 3×8 characters; for a 2×8 character account number the last eight digits of the IBAN are zeros. If provided, the creditor name must be provided, and none of the secondary identifier fields may be filled. |
creditorIdentification | Creditor identifier | |
identificationType | Creditor identifier type | Creditor identifier type, possible values: ORG-BIC: Organization BIC identifier; ORG-OTHR: Organization other unique identifier; PRV-OTHR: Private individual other unique identifier. Only one can be provided. If provided, the creditor identifier value must also be provided. |
identification | Creditor identifier value | Creditor identifier value; if provided, the creditor identifier type must also be provided. For ORG-BIC the BIC format must be used: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} |
paymentInformationId | Payment information block identifier | A unique identifier provided by the sending party to unambiguously identify the Payment Information block within the message. Uniqueness must be ensured. |
categoryPurpose | Category purpose | The validity period of the payment request can be specified here with millisecond precision. |
categoryPurposeCode | Category purpose code | The high-level purpose of the order according to predefined categories. In this message element the initiating party can provide information about the processing of the payment that is expected to trigger a special processing flow at one of the banks in the payment chain. Values published by the standards body in the ExternalCategoryPurpose1Code list may be provided. Category purpose codes |
paymentRequests | Payment request information | A group of message elements containing data for each individual transaction in the message. |
expiryDateTime | Payment request validity period | The validity of the payment request, within which the payment request can be fulfilled. Can be specified with centisecond precision. Maximum 2 months. |
instructionIdentification | Instruction identifier | The instruction identifier is a point-to-point reference between the payment request sender and the instructed party for identifying the individual transaction. The instruction identifier may be included in multiple messages related to the instruction. Uniqueness must be ensured. |
instructionPriority | Instruction priority | Indicates the urgency or order of importance with which the payment request sender requests the sending of the payment request. HIGH: High priority; NORM: Normal priority. Only 'HIGH' or 'NORM' can be provided. |
instructedAmount | Request amount | The requested amount in the currency specified by the payment request sender. |
currency | Currency | Currency code per ISO 4217 standard. Only 'HUF' is allowed. |
amount | Amount | The amount to be moved between the debtor and the payment request sender, in the currency specified by the payment request sender. If the amount is marked as modifiable, it can be fulfilled with an amount different from the original in the request — lower or higher — up to the instant transfer limit. Only two decimal places are allowed; the value must be 00, or the amount may be provided without a decimal point and cents. |
amountModificationAllowed | Amount editability | The payment request sender can indicate in the message whether the amount of the request can be modified by the recipient. If the payment request amount is modifiable, it can be fulfilled with an amount different from the original in the request — lower or higher — up to the instant transfer limit. |
chargeBearer | Charge bearer | This determines the party or parties that will bear the costs associated with the execution of the transfer. Only 'SLEV' is allowed. |
ultimateDebtorName | Ultimate debtor name | The name of the end-party who ultimately owes the amount to the (ultimate) creditor. ISO guideline: data about the ultimate debtor may only appear in the message if it differs from the debtor. |
ultimateDebtorIdentification | Ultimate debtor identifier | |
identificationType | Ultimate debtor identifier type | Ultimate debtor identifier type, possible values: ORG-BIC: Organization BIC identifier; ORG-OTHR: Organization other unique identifier; PRV-OTHR: Private individual other unique identifier. Only one can be provided. |
identification | Ultimate creditor identifier value | Ultimate debtor identifier value. |
debtorName | Debtor name | |
debtorAddress | Debtor address | |
country | Debtor country code | Debtor's country code. |
address | Debtor unstructured address | Debtor's unstructured address; can include postal code, city, street, street type, house number, staircase, floor, door, etc. |
debtorIdentification | Debtor identifier | |
identificationType | Debtor identifier type | Debtor identifier type, possible values: ORG-BIC: Organization BIC identifier; ORG-OTHR: Organization other unique identifier; PRV-OTHR: Private individual other unique identifier. Only one can be provided. If provided, the debtor identifier value must also be provided. |
identification | Debtor identifier value | Debtor identifier value; if provided, the debtor identifier type must also be provided. For ORG-BIC the BIC format must be used: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} |
debtorAccount | Debtor's account | The clear identifier of the remitter's account. Only one of IBAN or secondary identifier can be provided. |
iban | Debtor's account in IBAN format | The debtor's international bank account number. In Hungary it is a 28-character number string always starting with HU; the last 24 characters match the domestic account number if it is 3×8 characters; for a 2×8 character account number the last eight digits of the IBAN are zeros. If provided, the debtor name must be provided, and none of the secondary identifier fields may be filled. |
proxy | Debtor's account with secondary identifier | If provided, the debtor name and IBAN account number cannot be provided. |
proxyType | Debtor account secondary identifier type | Debtor account secondary identifier type, possible values: TELE: Mobile phone number; EMAL: Email address; TXID: Hungarian tax ID or foreign tax ID/tax number; TXNB: Hungarian tax number. TELE, EMAL, TXID, TXNB codes can be provided. If provided, the debtor name and IBAN cannot be provided, and the debtor account secondary identifier value must be provided. |
proxyId | Debtor account secondary identifier value | Format depends on the debtor account secondary identifier type: TELE: format is Plus, Country code, hyphen, area code, phone number: +[0-9]3-[0-9]25 e.g.: +36-7012345678; EMAL: email address up to 70 characters; TXID: Hungarian tax ID with country code e.g.: TXID:HU8123456789 or TXID:CZ123456789; TXNB: Hungarian or foreign tax number with country code e.g.: TXNB:HU12345678. If provided, the debtor name and IBAN cannot be provided, and the debtor account secondary identifier type must be provided. |
ultimateCreditorName | Ultimate creditor name | The name of the end-party to whom the amount is ultimately due. ISO guideline: data about the ultimate creditor may only appear in the message if it differs from the creditor. |
ultimateCreditorIdentification | Ultimate creditor identifier | |
identificationType | Ultimate creditor identifier type | Ultimate creditor identifier type, possible values: ORG-BIC: Organization BIC identifier; ORG-OTHR: Organization other unique identifier; PRV-OTHR: Private individual other unique identifier. |
identification | Ultimate creditor identifier value | Ultimate creditor identifier value. |
purposeCode | Purpose/Payment situation identifier | The purpose allows end parties — the initiating party, debtor/(ultimate) payer, and (ultimate) creditor — to communicate information about the nature of the transfer. The purpose is a content element that none of the intermediary banks in the payment chain use for processing the order. Values published by the standards body in the ExternalPurpose1Code list may be provided. Purpose codes |
regulatoryReporting | ||
invoiceIdentification | Invoice or receipt identifier | It may be necessary to provide an invoice or receipt identifier — for example, in the case of utility bill payments — the identifier of the invoice to be paid, as this may facilitate later retrieval for both the payer and the beneficiary. Similarly, in the case of retail transactions, providing the receipt identifier may be useful. |
customerIdentification | Customer identifier | A customer identifier is primarily used in utility bill payments, where the service provider identifies its customers with a special identifier used only by that particular provider. In this case, it is also necessary to include this in the transfer message, as it helps to unambiguously track payments for both the payer and the beneficiary. |
credTranIdentification | Beneficiary's internal transaction identifier | Beneficiary's internal transaction identifier — it may happen that the beneficiary company assigns its own identifier to individual financial transactions; including these in the transfer message can help with quick and unambiguous processing of the transaction in the beneficiary's own internal systems. Uniqueness must be ensured. |
loyaltyIdentification | Loyalty or discount system identifier | Loyalty or discount system identifier — including identifiers related to individual discounts in retail purchase transactions may be in the interest of both the payer and the beneficiary merchant. This also allows the customer to identify themselves with their loyalty card number and apply their personal discounts before approving the transaction. |
navCheckIdentification | NAV check code | NAV check code — in retail purchases, the receipt must mandatorily contain the NAV check code, which can also be included in the transfer message for later transaction processing. |
latestDateTime | Payment deadline | In addition to the payment request validity period, the payment deadline can optionally be provided. If provided, it must be within the validity period. If not provided, it takes the value of the validity period. Can be specified with centisecond precision. The validity period of the payment request can be at most 2 months per current regulations. Cannot be greater than the validity period. |
remittanceInformationUnstructured | Unstructured remittance information | This field contains information agreed between the debtor and the creditor. Unstructured information enabling reconciliation/matching of an incoming transfer with the item it is intended to settle, e.g., a commercial invoice recorded on the customer's current account. Only one of unstructured or structured remittance information can be used. |
remittanceInformationStructured | Structured remittance information | Only one of unstructured or structured remittance information can be used. |
reference | Creditor reference | This reference must be provided by the initiating party in the structured remittance information to enable the creditor to reconcile the received amount when the payment request is fulfilled. Can only be provided if unstructured remittance information is not provided. |
referenceType | Creditor reference type code | The type of reference defined by the creditor, in code form. Only 'SCOR' is allowed. Can only be provided if unstructured remittance information is not provided and the creditor reference is provided. |
referenceIssuer | Creditor reference issuer | The organization that defines the type of creditor reference. Can only be provided if unstructured remittance information is not provided and the creditor reference is provided. |