transmitTerminal

Overview

The transmitTerminal command manually initiates the transmission of transaction or terminal data to Shva, Israel's central clearing network. This command allows merchants to control their own transmission timing instead of relying on automatic daily transmissions.

Use cases

  • Manual settlement initiation: Trigger immediate transmission to Shva instead of waiting for the automatic daily cycle

  • Same-day reconciliation: Ensure transactions are transmitted for immediate settlement and reporting

  • End-of-day processing: Manually close the day's transactions before the automatic transmission

  • Urgent settlement requirements: Handle time-sensitive transactions that need immediate processing

  • Business workflow integration: Integrate manual transmission into specific business processes or schedules

  • Pre-weekend/holiday processing: Ensure transactions are transmitted before extended periods when automatic processing might be delayed

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 transmitTerminal command in the int_in parameter.

XML payload structure

Note: The responseType field should be set to immediate within the transmitTerminal block. This ensures the merchant receives the response immediately after sending the request without waiting for the transmission to finish.

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 transactions to transmit

  • Available in your merchant dashboard

transmitType - Type of transmission to perform

Type: String (Enum) Required: Yes Description: Specifies the type of transmission to execute

Valid Values:

  • settlements - Transmits all transactions that are ready for transmission on the specific terminal

Example: settlements

Usage Notes:

  • settlements is the only available value for transmitType

  • Will transmit all transactions that are ready for transmission on the specific terminal

responseType - Response format specification

Type: String (Enum) Required: Yes Description: Must be set to immediate to receive the response immediately

Valid Values:

  • immediate - Merchant receives the response immediately after sending the request and won't wait for the transmission to finish

Example: immediate

Usage Notes:

  • Must be included in the transmitTerminal element

  • Always set to immediate to receive response without waiting for transmission completion

  • This is a required field for proper transmission handling

Optional parameters

Note: There are currently no optional parameters for the transmitTerminal command. All fields shown above are required.

Response structure

Successful response

A successful transmitTerminal response contains transmission confirmation and details:

Key Response Fields:

  • result: 000 indicates successful transmission initiation

  • tranId: Transaction ID for this operation

  • transmitId: Unique identifier for this transmission batch

  • terminalNumber: The terminal that initiated the transmission

  • transmitType: The type of transmission performed (e.g., settlements)

  • countTransmitted: Number of transactions transmitted (may be empty for immediate response)

Error response

Error responses include specific error codes and messages:

Code examples

Error codes

Error Code
Description
Resolution

000

Permitted transaction (Success)

Transmission initiated successfully

308

An error occurred while executing a query in the database

Contact support if the issue persists

444

Application Error

Contact support for assistance

500

TransmitId was not found

Verify the transmit ID and retry

501

Terminal cannot be retransmitted. Please call support

Contact support for manual intervention

502

Terminal is currently in transmit. Cannot make another transmit

Wait for current transmission to complete before retrying

503

Terminal cannot be retransmitted. There was no transmit failure

No retransmission needed - previous transmission was successful

504

Cannot transmit. There was a transmit failure. Please try to retransmit

Retry the transmission

534

Transmit exceeds allowed batches per transmit

Reduce the number of transactions or contact support to increase limit

550

Transmit service, error parsing GW request

Check request format and retry

552

Transmit service, transmit_log not in status 0

Contact support - internal status issue

553

Transmit service, error getting transactions from DB

Database issue - contact support if persists

554

Transmit service, error creating transactionData

Internal processing error - contact support

555

Transmit service, error creating 1402 messages

Message formatting error - contact support

556

Transmit service, error sending or creating request to BP

Communication error with processor - retry or contact support

557

Transmit service, error updating transmit log

Internal logging error - contact support

558

Acquirer error - terminal does not exist

Contact System Administration - terminal configuration issue

  • transmitInquire - Query transmission status and batch information after using transmitTerminal

  • doDeal - Process transactions that will later be transmitted

  • Request Structure - General API request format

Transmission Timing: Manual transmission typically processes all pending transactions for the specified terminal. Use transmitInquire to verify the results and get detailed information about what was transmitted.

Last updated

Was this helpful?