Sample Calls
EAM Init sample call
EAM Payload Data Content
If you wish to process account statements and use the content of EAM fields for this purpose, the table below uses the Original Account Statement format of the Raiffeisen Electra system.
Character Usage Restrictions
In addition to all standard UTF-8 characters (in the range 32–126), only Hungarian accented characters found in the "extended" ASCII range above 128 may be used.
Error Codes
Legend:
EAM Status Messages and Their Meaning
| Status | Description |
Rejection Codes
The payer's payment service provider can communicate the reason for rejecting a given transaction to the Aggregator using the codes listed in the following table.
Other References
The beneficiary's (internal) transaction identifier (transactionReference) accompanies the message throughout its lifecycle. This data is generated by the beneficiary or the endpoint made available to the beneficiary. The purpose of the identifier is to allow the beneficiary to track the processing of their mandate in every message, as the data also appears on the account statement and in the status information message. The beneficiary's identifier does not go into the end-to-end ID field in the interbank space, because the GIRO standard application requires the payer's bank to fill it in a specified way. The beneficiary's internal transaction identifier shares a field (credTranId) in the EAM with the Aggregator's unique identifier, so the beneficiary's bank also receives the two identifiers concatenated in the interbank transfer message (or in the EAM code).
Callback URL
The use of a Callback URL is relevant in cases where the payment process is initiated from an application on the payer's device other than the mobile banking application. Using the Callback URL, the payer can return to the interface from which the purchase was initiated at the end of the payment. Such interfaces can include: the payment status page of an online store, the payment status page of an application in case of an in-app purchase, or the post-payment landing page of a loyalty application. The interface itself indicates the success or rejection of the payment.