Skip to content

EMV Device Integration via API (Pay Bridge Solution)

v1.0
API Base URL
Pay Bridge Server:https://secure5.tranzila.com/cgi-bin
Download OpenAPI

The Pay Bridge Solution lets you run card-present transactions on cloud-connected EMV devices directly through an API. The following devices are supported because they operate in a cloud configuration: Nova, A30, A80, and Urovo.

Each request targets a specific physical device through its cloud identifier (pos_id), which is mapped to the device in 5Admin.

Supported services

Servicetranmodecred_typeDocumented below
Charge - RegularA1Yes
Charge - InstallmentsA8Yes
Charge - Credit installmentsA6Yes
Refund (Credit)C1Yes
Verification - J5--Not yet provided
Forced transaction--Not yet provided

J5 verification and forced-transaction requests are available services, but request/response samples were not included in the source material and are therefore not documented here.

Endpoint and content type

  • URL: https://secure5.tranzila.com/cgi-bin/tranzila71mdl.cgi
  • Method: POST
  • Header: Content-Type: application/json

The terminal is identified by supplier (terminal name) together with pos_id (the device cloud ID).

Currency

Transactions are processed in ILS only. The currency field uses the ISO 4217 numeric code 376 (Israeli New Shekel).

Error handling

Responses are returned with HTTP 200 even when the transaction fails. The transaction outcome is carried at the application level inside transaction_result:

  • statusCode = 0 indicates an approved transaction.
  • A negative statusCode (for example -26, "invalid currency code") indicates a declined or rejected transaction. The human-readable reason is returned in statusMessage.

Amounts

Monetary fields inside transaction_result (amount, firstPaymentAmount, otherPaymentAmount) are returned in agorot (minor units). For example, amount: 200 is 2.00 ILS and amount: 30000 is 300.00 ILS. The sum field in the request is expressed in ILS (major units).

Was this page helpful?