transmitInquire

Overview

The transmitInquire command retrieves metadata and status information about transmissions that have been sent to Shva, Israel's central clearing network. This command provides detailed information about transmission batches, including transmission time, number of transactions, success/failure status, and related identifiers.

This command is essential for merchants who need to track, audit, or troubleshoot their settlement transmissions, enabling comprehensive reconciliation and monitoring of the transmission process.

Use cases

  • Transmission status verification: Check if transmissions to Shva completed successfully or encountered errors

  • Reconciliation and auditing: Gather detailed transmission data for accounting and compliance purposes

  • Debugging transmission issues: Investigate failed or incomplete transmissions to identify problems

  • Settlement monitoring: Track when transactions were transmitted and processed by Shva

  • Batch analysis: Review transmission batches to understand settlement patterns and timing

  • Compliance reporting: Generate reports on transmission activities for regulatory requirements

  • Post-transmission validation: Verify transmission results after using transmitTerminal command

Request structure

For a comprehensive overview of the API request format and authentication, see API Request & Response General Structure.

Send a standard Hyp API request to your assigned server endpoint with the transmitInquire command in the int_in parameter.

XML payload structure

Required parameters

terminalNumber - Your merchant terminal identifier

Type: String (Numeric, 10 digits) Required: Yes Description: The unique terminal number assigned during merchant onboarding

Example: 0882819014

Usage Notes:

  • Must match your assigned terminal number

  • Used for identifying which terminal's transmissions to query

  • Available in your merchant dashboard

Optional parameters

transmitId - Specific transmission identifier

Type: String (Numeric, 1-20 digits) Required: No Description: Query a specific transmission batch by its unique identifier

Example: 987654321

Usage Notes:

  • Use to get details about a specific transmission batch

  • Transmission ID is returned in responses from transmitTerminal command

  • When specified, returns detailed information about that specific transmission

fromTransmitDateTime / toTransmitDateTime - Transmission date/time range

Type: String (DateTime format) Required: No Description: Date and time range filter for transmission queries

Format: YYYY-MM-DD HH:MM:SS or system-specific datetime format Example: 2025-07-24 08:00:00

Usage Notes:

  • Use both parameters together to define a datetime range

  • Filters transmissions by when they were sent to Shva

  • Useful for querying transmissions within specific time periods

shvaReferanceNo - Shva reference number

Type: String (Numeric, 7-8 digits) Required: No Description: Query transmissions by Shva reference number

Example: 5568985

Usage Notes:

  • Reference number assigned by Shva for transmission batches

  • Use to find specific transmissions when you have the Shva reference

  • Helpful for reconciling with Shva reports

transmitType - Type of transmission

Type: String (Enum) Required: No Description: Filter transmissions by type

Valid Values: Refer to Hyp integration documentation for available transmission types Example: STANDARD

Usage Notes:

  • Filter results to specific transmission types

  • Useful when different transmission types are used for different purposes

  • Must match the transmission type values used in your environment

Response structure

Successful response example

Key Response Fields:

  • result: 000 indicates successful inquiry

  • transmitId: Unique identifier for this transmission batch

  • transmitStatus: Status of transmission (completed, failed, pending, etc.)

  • startDateTime/endDateTime: When transmission started and ended

  • transmitStatistics: Detailed statistics including:

    • shvaReferanceNo: Shva reference number for the transmission

    • countTransmitted: Total number of transactions transmitted

    • currencyTotal: Overall amounts and counts by debit/credit

    • Card company breakdowns (isracard, visa, diners, amex, etc.)

Error response example

Key Error Fields:

  • result: Error code (500 in this example)

  • message/userMessage: Description of the error

  • transmitInquire: Empty element when no data is found

Code examples

Error codes

Error Code
Description
Resolution

000

Permitted transaction

Transmission inquiry completed successfully

308

An error occurred while executing a query in the database

Contact System Administration

444

Application Error

Contact System Administration

500

transmitId was not found

Verify the transmission ID exists and is valid

501

Terminal cannot be retransmitted

Call support for assistance

502

Terminal is currently in transmit

Wait for current transmission to complete before retrying

503

Terminal cannot be retransmitted

There was no transmit failure - retransmission not needed

504

Cannot transmit

There was a transmit failure - please try to retransmit

534

Transmit exceeds allowed batches per transmit

Contact System Administration

550

transmit service, error parsing GW request

Contact System Administration

552

transmit service, transmit_log not in status 0

Contact System Administration

553

transmit service, error getting transactions from DB

Contact System Administration

554

transmit service, error creating transactionData

Contact System Administration

555

transmit service, error creating 1402 messages

Contact System Administration

556

transmit service, error sending or creating request to BP

Contact System Administration

557

transmit service, error updating transmit log

Contact System Administration

558

Acquirer error - terminal does not exist

Contact System Administration

Reconciliation Tip: Use transmitInquire in combination with inquireTransactions to get a complete picture of your settlement process - transmission status from transmitInquire and individual transaction details from inquireTransactions.

Last updated

Was this helpful?