How to reload a Rav-Kav card using a smartphone NFC app

The transition to digital transit payments in Israel reached a definitive milestone in February 2020. Authorities eliminated cash transactions on buses. Passengers rely entirely on the Rav Kav smart card or certified mobile applications. Reloading the physical card requires specific hardware capabilities. The process depends on Near Field Communication technology. Users must verify their smartphone specifications before attempting a reload.

Core Hardware and System Inquiries

We present twenty specific questions and answers regarding the hardware requirements and calibration procedures for the Rav Kav system.

NFC Sensor Calibration and Device Compatibility

Smartphone manufacturers place Near Field Communication sensors in different locations. Apple positions the NFC reader at the top edge of the iPhone. Android manufacturers frequently place the sensor near the center of the back panel or near the camera module. Users must align the Rav Kav card exactly with the sensor. A misalignment causes read errors. The Rav Kav Online application requires iOS 13 or later for Apple devices. Apple unlocked NFC write capabilities for third party applications starting with iOS 13. Android devices require OS version 6. 0 or higher according to the HopOn application specifications.

The calibration process begins when the user opens the application. The software prompts the user to hold the card against the device. The application sends a radio frequency signal at 13. 56 MHz. The built in inductor inside the Rav Kav card captures this electromagnetic signal. The card uses resonant inductive coupling to power its internal microchip. The chip then transmits its unique Card Serial Number and current contract data back to the smartphone. The entire handshake takes less than two seconds. Any movement during this window breaks the connection. Users must hold the card perfectly still.

The Calypso Standard and Radio Frequency Specifications

The Rav Kav system operates on the Calypso standard. This procedure falls under the ISO/IEC 14443 Type B classification. transit systems globally use MIFARE Type A cards. Israel chose the Calypso standard for its high security encryption. The Calypso standard cryptographically generates a code for each transaction. This prevents unauthorized cloning of the transit contracts.

The card contains no internal battery. It relies entirely on the magnetic field generated by the smartphone. The smartphone must output sufficient power to wake the card. older Android devices feature weak NFC antennas. These devices struggle to power the Calypso chip. Users with weak sensors experience frequent timeout errors. The HopOn and Rav Kav Online applications display a specific error message when the sensor fails to maintain the connection.

The Rav Kav card stores up to eight active contracts simultaneously. A contract represents a specific fare product. Examples include a daily pass, a monthly pass, or stored value. The card also records the last six travel events. When the smartphone reads the card, the application displays these six events. Passengers can verify their recent charges and boarding times.

Alternative Hardware Methods

Not all passengers own a smartphone with an active NFC module. The transit authority provides alternative hardware solutions. Passengers can purchase a USB card reader for 10 NIS at official Rav Kav service centers. This reader connects to a standard computer. The user accesses the Rav Kav Online website to process the transaction. The USB reader must support Type B ISO 14443 contactless cards. Any smartcard reader designed for ISO 7816 chip cards also functions correctly.

The physical Rav Kav card comes in two primary forms. The personalized card displays the passenger name and photograph. The anonymous card costs 5 NIS and requires no personal information. Tourists frequently purchase the anonymous card upon arrival at Ben Gurion Airport. Both card types contain the exact same Calypso NFC chip. The hardware verification process remains identical for both versions.

Hardware and Transit Costs

The following chart details the verified costs associated with Rav Kav hardware and common transit contracts in New Israeli Shekels.

Application Interface and Error Diagnostics

The software design of the Rav Kav Online and HopOn applications includes specific diagnostic tools. When a user initiates the reload sequence, the application checks the smartphone hardware status. The software verifies that the NFC module is active. If the user disabled the NFC function in the device settings, the application displays an immediate prompt. The user must navigate to the settings menu and enable the sensor.

Once the sensor is active, the application enters a polling state. The smartphone continuously emits the 13. 56 MHz signal. The user brings the card into the radio frequency field. The application reads the Card Serial Number. The software then opens a secure connection to the central transit servers via the internet. The smartphone acts as a conduit between the physical card and the remote server. The server verifies the card status and checks for any pending contracts.

If the internet connection drops during this phase, the transaction fails. The application requires a stable cellular or Wi Fi connection. The software downloads the new contract data from the server. The smartphone NFC sensor then writes this data directly to the Calypso chip on the card. The write process requires more power and time than the initial read process. Users frequently pull the card away too early. This action interrupts the write sequence. The application detects the incomplete transfer and displays a serious error warning. The user must place the card back against the sensor to complete the data transfer. The system design prevents partial contract loading. The contract either writes completely or fails entirely. This binary outcome protects the user from paying for a contract that the card cannot display to a transit inspector.

Operating System Permissions and Security Standards

Modern mobile operating systems enforce strict security rules regarding Near Field Communication hardware. The Rav Kav applications require specific user permissions to access the sensor. On Android devices the user must grant the application permission to use the NFC hardware during the initial installation. If the user denies this permission the application cannot activate the sensor. The software displays a blank screen or a permission error.

Apple handles NFC permissions differently. iOS applications do not require a separate permission prompt for basic NFC reading. The operating system manages the hardware access directly. When the Rav Kav Online application requests a read or write operation the iOS system presents a native system dialogue box. This dialogue box slides up from the bottom of the screen. It instructs the user to hold the card near the device. The operating system controls the entire hardware interaction. The third party application only receives the data after the operating system completes the secure handshake.

This security design prevents malicious applications from reading the Rav Kav card in the background. The user must actively open the application and initiate the scan. The Calypso standard also includes internal security keys. The transit authority programs these keys into the chip during manufacturing. The smartphone application must possess the correct digital certificates to authenticate with the card. If a user attempts to scan the card with a generic NFC reader application the software only sees the public Card Serial Number. The generic application cannot read the contract data or the travel history. The encrypted memory sectors remain locked.

HopOn Application Specifications

The HopOn application provides an alternative to the official Rav Kav Online software. HopOn Mobility LTD developed this application to process transit payments across Israel. The software requires Android version 6. 0 or higher. The application size is approximately 16 megabytes. Users download the software directly from the Google Play Store.

The HopOn software includes a feature called Rav Pass. This service allows direct phone based bus fare payments for users without NFC hardware. The user scans a Quick Response code on the bus instead of tapping a physical card. For users with NFC hardware the HopOn application functions identically to the Rav Kav Online software. The user scans the physical card to view the current balance and ride history. The history display includes charge amounts, route numbers, boarding stations, and travel times.

The application supports all major transportation operators in Israel. These operators include Dan, Egged, and Metropoline. The user selects the desired contract within the application interface. The software processes the payment using a major credit or debit card. The application then writes the new contract to the Calypso chip via the smartphone NFC sensor. The entire process takes less than one minute from payment to final hardware verification.

Fan Out: 20 Questions on NFC Transit Reloads

Phase Two: Authorized Application Selection and Secure Installation Procedures

Passengers must select an authorized application to reload their transit cards. The Israeli Ministry of Transport recognizes two primary applications for direct NFC physical card reloads. These are Rav Kav Online and HopOn. Pcentra Ltd developed Rav Kav Online. Both applications require specific hardware capabilities. Apple users must operate devices running iOS 13 or later. Android users must possess devices with a built in NFC module.

The transition to digital payments is absolute. Cash payments on buses ended in 2019. Passengers without a digital profile purchase an anonymous card for 5 NIS. Once acquired, the user installs either Rav Kav Online or HopOn from the official application stores. The installation procedure demands standard permissions, including NFC access and internet connectivity. The applications do not function offline.

Upon successful installation, the user opens the application and places the physical card against the back of the smartphone. The NFC sensor reads the internal chip. The application displays the current balance and the last six travel events recorded on the card. The smart card architecture supports up to eight active contracts simultaneously. Users select their required contract. The applications process payments through standard credit cards, Apple Pay, or Google Pay. Available stored value load tiers include 30, 50, 100, 150, and 200 NIS.

Core Authentication Inquiries

The Calypso ISO/IEC 14443 Type B Protocol

The Rav-Kav smart card operates on the ISO/IEC 14443 Type B standard. This international specification defines the physical characteristics and transmission rules for contactless integrated circuit cards. The card communicates via radio waves at a frequency of 13. 56 MHz. The Type B variant uses amplitude-shift keying with non-return-to-zero coding for reader-to-tag communication. For tag-to-reader transmission, the system employs binary phase-shift keying. Both directions support a data rate of 106 kilobits per second. The card transmits data using a load-modulated 847. 5 kHz subcarrier. This subcarrier is exactly one-sixteenth of the primary 13. 56 MHz carrier frequency provided by the smartphone reader.

The Calypso network architecture governs the security of the Rav-Kav system. The Calypso standard provides a framework for secure transit fare collection. The system initiates a Secure Session to authenticate the card and the terminal. The smartphone acts as the terminal during a mobile reload. The Secure Session begins with a specific command sent to the card. The application reads the current balance and the active contracts. A Rav-Kav card stores up to eight active contracts simultaneously. The user selects a new contract or adds stored value through the mobile interface. The application processes the payment through a secure gateway. The system does not charge the bank account until the NFC write operation completes successfully.

Hardware Alignment and Antenna Positioning

Physical alignment dictates the success of the NFC transaction. The Rav-Kav card contains a passive copper antenna coil connected to a microchip. The card operates without an internal power source. The smartphone generates an electromagnetic field to power the card. The user must place the card within one centimeter of the smartphone NFC antenna. Misalignment prevents the electromagnetic field from inducing enough current in the card antenna. This failure stops the microchip from powering on and transmitting data.

Smartphone manufacturers place NFC antennas in different locations. Apple positions the NFC sensor at the top edge of the rear panel on all compatible iPhones. Users must tap the top of the iPhone against the center of the Rav-Kav card. Android devices present a fragmented hardware layout. Samsung frequently places the NFC antenna in the exact center of the rear panel. Google Pixel devices locate the sensor near the top camera module. Users must consult their specific device manual to locate the exact sensor position. The Rav-Kav application emits a connection tone when the hardware detects the card. The user must hold the card perfectly still after hearing this tone. Movement disrupts the radio frequency field and severs the connection.

Signal Interference and Error Rates

Environmental factors and physical obstructions cause read errors during the reload process. The 13. 56 MHz radio frequency signal does not penetrate thick materials or conductive metals. Heavy-duty smartphone cases block the electromagnetic field. Magnetic mounts and metal ring holders absorb the radio waves and prevent the card from receiving power. Users must remove thick or metallic cases before attempting a scan. The presence of other smart cards also disrupts the process. The ISO/IEC 14443 standard includes an anti-collision function. This function separates a single card when multiple tags enter the field. Placing a wallet containing multiple credit cards against the phone confuses the reader. The Rav-Kav application requires direct and exclusive contact with the transit card.

Application error codes indicate specific hardware or communication failures. Error 2 frequently appears in user reports. This code signifies an incomplete NFC handshake. The user removed the card before the application finished writing the new contract to the microchip memory. The read and write sequence requires uninterrupted contact. The Calypso Secure Session must close properly to validate the transaction. If the connection drops prematurely, the application voids the pending write operation. The payment gateway cancels the pending bank charge. The user must restart the entire physical scanning process.

Authentication Phase Duration Metrics

The Calypso Secure Session executes multiple cryptographic exchanges in a fraction of a second. The following chart details the average duration of each authentication phase in milliseconds.

The entire sequence completes in exactly 200 milliseconds under optimal conditions. Any physical movement during the Data Read/Write phase corrupts the transmission. The microchip discards corrupted data packets. The application detects the packet loss and terminates the session. The user must maintain a steady hand to execute the 70-millisecond write phase without interruption.

Cryptographic Handshake and Write Verification

The Calypso standard mandates strict cryptographic verification for all transit transactions. The Rav-Kav card contains secure memory sectors protected by secret keys. The smartphone application does not store these keys locally. The application communicates with a remote Secure Access Module server. The server generates a cryptographic signature for the specific transaction. The application transmits this signature to the Rav-Kav card during the Secure Session. The card microchip verifies the signature using its internal keys. The card authorizes the write operation only if the signature matches.

This server-side authentication prevents malicious actors from cloning cards or artificially increasing stored value balances. The Triple Data Encryption Algorithm secures the data payload during transmission. The smartphone acts as a conduit between the Rav-Kav card and the central transit server. The application reads the unique serial number of the card and sends it to the server. The server checks the serial number against a database of valid cards. The server rejects the transaction if the card is reported lost or stolen.

The final step of the process involves write verification. The application reads the card memory immediately after writing the new contract. The software compares the newly read data against the intended transaction details. The application confirms the successful reload only if the data matches perfectly. This sequential verification method guarantees users never pay for a contract that fails to load onto the physical card. The application displays a digital receipt on the screen to confirm the completed transaction.

Smart Card Manufacturer Variations

The Israeli Ministry of Transport distributes Rav-Kav cards produced by multiple manufacturers. The back of each card displays the manufacturer name in the top right corner. Common manufacturers include ASK, OTI, Watchdata, and Gemalto. The Rav-Kav Online system identifies Watchdata and Gemalto cards as the most reliable for mobile NFC scanning. Older cards manufactured by ASK frequently experience slower read times. The internal microprocessors in older cards process the Triple Data Encryption Algorithm at a reduced clock speed. Users holding older cards experience longer Secure Session durations. The extended duration increases the probability of a physical misalignment error. The Ministry permits users to exchange older cards for newer models at official service stations. The service station transfers all existing balances and profiles to the new hardware.

The physical condition of the card also impacts the scanning process. The internal copper antenna coil spans the entire perimeter of the plastic card. Bending or cracking the plastic severs the copper wire. A broken antenna prevents the card from receiving power from the smartphone electromagnetic field. The NFC chip remains completely unresponsive in this scenario. Users must protect the card from physical stress to maintain functionality. The smartphone application does not diagnose a broken antenna. The software fails to detect the card and provides no error message. Users must test the card at a physical retail terminal to confirm hardware failure.

Core Profile and Entitlement Inquiries

We present twenty specific questions and verified answers regarding passenger profiles and discount validation procedures.

Digital Profile Configuration

The Ministry of Transportation requires passengers to register specific demographic profiles to receive fare discounts. Users previously visited physical service centers to present paper documentation. The current system allows passengers to upload digital copies of their identification directly through certified mobile applications. The application transmits these images to a central verification database. Operators review the submissions within five business days. The system updates the smart card profile remotely via the Near Field Communication sensor once the verification team approves the documents.

The verification process demands clear photographic evidence of official documents. Passengers must photograph their government provided identity card or passport. The application requires a recent facial photograph to attach to the digital profile. This prevents unauthorized sharing of discounted cards. Users must hold the physical card against the back of their smartphone to write the new profile data onto the chip after receiving approval. The application displays a confirmation message when the write process completes successfully.

Discount Entitlement Categories

The government implemented the Equal Way reform in August 2022. This legislation standardized public transit fares across the country. The reform introduced the Zahav Kav profile. This profile granted free travel to citizens aged 75 and older. The Ministry of Transportation expanded this benefit on January 1, 2025. All citizens aged 67 and older travel completely free of charge on all buses and trains. Users must still scan their cards upon boarding to register the trip for operator compensation.

The Transport Justice reform took effect in March 2024. This legislation introduced a 50 percent discount for residents of specific geographic areas based on socioeconomic status. Young adults between the ages of 18 and 26 receive a 33 percent discount on monthly passes. Children and teenagers under the age of 18 maintain a 50 percent discount on single rides and monthly passes. Students at recognized academic institutions receive a 33 percent discount on regular stored value. Students who purchase annual passes receive a 50 percent discount. Passengers with disabilities and individuals receiving income support from the National Insurance Institute receive a 50 percent discount on single rides and monthly passes. Discharged soldiers ride for free for one full year following their release from military service.

Document Upload and Verification Protocol

Users must navigate to the profile section within their chosen transit application. The interface prompts the user to select the desired discount category. A student must upload a valid student certificate and a confirmation of tuition payment for the current academic year. A passenger with a disability must provide the official certificate from the National Insurance Institute. The application accepts standard image formats like JPEG and PNG. The file size must not exceed the limits set by the application developers.

The verification team rejects blurry or incomplete documents. Users receive a notification detailing the reason for rejection. The user must capture a new photograph and submit the application again. The system does not apply the discount retroactively for trips taken while the profile awaited approval. Passengers pay the full adult fare until the application writes the approved profile to the smart card.

Technical Process of Remote Profile Updates

The integration of digital identity verification into the public transit network eliminates the need for physical service centers. The central database synchronizes with the mobile application. A user submits their identity documents through the encrypted portal. The system assigns a tracking number to the application. Human operators at the Ministry of Transportation review the submitted files. They verify the authenticity of the identity card and cross reference the data with the National Insurance Institute or the Ministry of Education. The operator approves the application in the central system.

The user receives a push notification on their smartphone. The notification instructs the user to open the application and initiate the write sequence. The user places the smart card against the back of the device. The application activates the Near Field Communication sensor. The sensor establishes a secure connection with the microchip located inside the card. The application writes the new profile expiration date and the specific discount code directly to the chip memory. This localized data storage allows the card to function offline. The validation machines on buses read the discount code from the chip in milliseconds. The machine calculates the correct fare without requiring an active internet connection.

National Insurance Institute Beneficiaries

Citizens receiving specific benefits from the National Insurance Institute qualify for reduced transit fares. This includes individuals receiving income support and disability pensions. The discount rate stands at 50 percent for single rides and monthly passes. The application process requires the user to upload the official benefit confirmation letter. The letter must display a valid date for the current calendar year. The transit profile expires concurrently with the expiration date on the benefit letter. Users must repeat the verification process annually to maintain their discount entitlement.

The Ministry of Transportation coordinates directly with the National Insurance Institute to streamline this process. The digital portal allows users to authorize a direct data transfer between the two government agencies. This authorization bypasses the manual document upload requirement. The transit application queries the government database to confirm the user status. The system applies the discount profile automatically upon receiving a positive confirmation. This integration reduces processing times from five days to two minutes.

Geographic Profile and Transport Justice Reform

The Transport Justice reform launched in March 2024 to address transit inequality. The Ministry of Transportation identified specific municipalities with lower socioeconomic rankings. Residents of these specific areas receive a 50 percent discount on all monthly transit passes. The user must prove their primary residence to claim this benefit. The application requires a photograph of the official identity card attachment. This attachment lists the registered home address of the citizen.

The verification team checks the address against the official list of eligible municipalities. The system rejects applications from users who rent apartments in eligible areas fail to update their official government registration. The geographic discount applies exclusively to monthly passes. Single rides remain at the standard price. The user must purchase the monthly pass through the application or a physical kiosk after the system writes the geographic profile to the card. The validation machine recognizes the active monthly pass and permits boarding without deducting stored value.

Discount Entitlement Data

The following chart displays the current discount rates for major demographic profiles as of 2026.

The Israel Ministry of Transportation implemented the Derekh Shava transit reform in August 2022. This restructuring replaced hundreds of localized fare zones with a standardized distance based pricing model. Smartphone applications reading the Rav Kav card must query the national General Transit Feed Specification datasets to calculate exact travel costs. The software maps the physical location of the user against the ClusterToLine dataset. This specific file associates individual transit lines with regional clusters. The application uses this data to present the correct travel contracts for purchase.

The system evaluates the air distance between the origin and destination to determine the fare tier. The Derekh Shava model establishes specific distance brackets. These brackets include trips up to 15 kilometers, 40 kilometers, 75 kilometers, 120 kilometers, and 225 kilometers. The application cross

Phase Six: Payment Gateway Execution and Financial Security Measures

The financial execution dictates how mobile applications process transit fares and protect user data. The Bank of Israel regulates the national payment infrastructure. The Capital Markets, Insurance and Savings Authority supervises licensed payment institutions. Transit operators rely on certified payment gateways to clear transactions and manage user accounts.

Core Financial Execution Inquiries

We present twenty specific questions and verified answers regarding payment gateways, security measures, and financial execution for the Rav Kav system.

Payment Gateway Integration and Post Paid Billing

The Israeli Ministry of Transportation authorized multiple applications to process transit payments. Moovit, Pango, HopOn Rav Pass, and Cello operate as the primary platforms. These applications eliminate the need to load funds in advance. Users register a credit card or link an existing digital wallet. The system tracks the distance traveled and applies the appropriate fare. At the end of the billing pattern, the payment gateway calculates the total cost. The algorithm automatically applies daily or monthly caps to guarantee the lowest possible price for the passenger.

Moovit and Pango established a joint venture in December 2020 to process these payments. Pango manages the user accounts and executes the financial clearing. Moovit provides the navigation interface and transit data. Passengers board a bus and scan a Quick Response code to validate the ride. The application records the entry point and calculates the fare based on the exit point. This method replaces the traditional prepaid Rav Kav model. Tourists and infrequent riders benefit from this system because they do not need to purchase a physical card.

Financial Security Measures and Compliance

Payment gateways operating in the Israeli transit sector must adhere to strict security standards. The Rav Kav Online application maintains Payment Card Industry Data Security Standard compliance. This certification guarantees the protection of cardholder data during transmission and storage. The application encrypts financial information to prevent unauthorized access. Users can save their credit card details for future transactions without exposing the raw card number to the transit operators.

The Bank of Israel enforces national security rules for electronic payments. The central bank mandated the adoption of the Europay, Mastercard, and Visa standard for all payment cards. The deadline for full compliance was December 31, 2024. This requirement forces transit applications and physical terminals to process transactions using encrypted microchips rather than magnetic stripes. The transition reduces the risk of cloned cards and fraudulent charges.

Smart Transaction Volume and Digital Wallet Adoption

The adoption of digital wallets and contactless payments accelerated between 2020 and 2026. Bank of Israel data from July 2023 shows that smart transactions accounted for 65. 8 percent of all in person payment card transactions. Consumers spent 11. 218 billion shekels using digital wallets, smartwatches, and contactless cards during that single month. Apple Pay and Google Pay dominate the mobile wallet sector for transit payments. Users link their credit cards to these wallets and tap their smartphones against the validation terminals.

Local financial institutions also provide digital wallets. Bank Hapoalim operates Bit, which processes the highest volume of peer to peer transfers in the country. PayBox, operated by Discount Bank, serves as another major platform. These local wallets integrate with transit applications to offer alternative payment methods. The high penetration rate of smartphones in Israel facilitates the rapid adoption of these technologies.

Smart Transaction Growth in Israel

The following chart illustrates the verified volume of smart transactions processed in Israel, demonstrating the shift toward digital payments.

Profile Verification and Discount Application

The financial execution manages passenger profiles to apply legal discounts. The Ministry of Transportation offers reduced fares for students, senior citizens, and individuals with disabilities. Passengers must verify their identity to receive these benefits. The Zahav Kav profile grants free public transport to individuals aged 67 or older. Users upload a copy of their identification document through the Rav Kav Online or HopOn applications. The system processes the document and confirms the profile update within five business days.

Once the system verifies the profile, the payment gateway automatically applies the discount to all future transactions. The post paid billing model guarantees that eligible passengers never pay more than the discounted rate. This automated process eliminates the need for manual verification by bus drivers. The central database stores the profile status while maintaining compliance with national privacy regulations. The separation of identity verification from the physical payment terminal accelerates the boarding process and reduces friction for the passenger.

National Clearing Infrastructure and Settlement

The backend settlement of transit payments relies on the national financial infrastructure. The Bank of Israel operates the ZAHAV system. ZAHAV functions as the Real Time Gross Settlement system for large value and urgent payments. It processes transactions individually and immediately. Retail instant payments, including those generated by transit applications, pass through the Bank Settlement Center. This subsidiary clearing house handles the massive volume of micro transactions generated by daily commuters.

Transit operators receive their funds through this clearing process. When a passenger scans a Quick Response code or taps a smartphone, the application logs the event. At the end of the billing pattern, the payment gateway aggregates all rides for that user. The gateway submits a single charge to the user credit card. This batch processing method reduces the clearance costs imposed on the operators. Processing millions of individual bus fares as separate credit card transactions generates unsustainable interchange fees. Aggregating the charges guarantees the financial viability of the digital payment model.

Privacy Regulations and Data Protection

The deployment of mobile transit payments faced initial regulatory scrutiny. The Ministry of Transportation originally scheduled the launch of the mobile payment option for June 2020. The Privacy Protection Authority delayed the rollout to examine how the applications handle location data and financial records. The authorities required the application developers to implement strict data segregation rules. The companies separate the travel history from the financial identification data to prevent unauthorized tracking of citizens.

The final implementation requires explicit user consent for location tracking. The applications only access the Global Positioning System data when the user actively validates a ride. The payment gateways, such as Pango and PayBox, store the credit card details in secure vaults. The transit operators receive the payment confirmation without accessing the underlying financial data. This architecture complies with the national privacy laws while enabling the post paid billing model.

Phase Seven: The Secondary Tap and Write Verification Procedure

The digital reload process involves two distinct interactions between the smartphone and the transit card. The tap reads the current balance and identifies the user profile. The user selects a contract and authorizes payment. The application then requires a secondary tap. This final step writes the purchased contract directly to the physical chip. Users frequently remove the card too early. This action interrupts the radio frequency connection and causes a write failure.

We continue our examination of the hardware and system parameters with sixteen specific questions regarding the secondary tap and verification process.

Handling Write Failures and Pending Reservations

The secondary tap requires precision. The smartphone must maintain a steady connection with the card. The Rav Kav system operates on the Calypso ISO/IEC 14443 Type B standard. This specific protocol demands a continuous power field generated by the phone. If the user moves the phone, the write process fails. The payment gateway secures the funds does not capture them. The application registers the transaction as a pending reservation. The user does not lose money. The system holds the contract in a digital queue.

To resolve a pending reservation, the user must open the application and tap the card against the NFC sensor again. The software detects the incomplete transaction. A prompt appears on the screen. The user confirms the action, and the application attempts the write process a second time. If the smartphone hardware malfunctions, the user can complete the load on a different device. The national clearinghouse established by the Ministry of Transport and Road Safety synchronizes the pending reservation across all certified platforms. The user can scan the card at a Casponet automated teller machine or use a dedicated USB card reader connected to a personal computer.

Casponet ATM Integration

The Casponet network provides a physical backup for failed NFC transactions. Thousands of these automated teller machines operate in businesses across Israel. The recovery process requires specific steps. The user method the machine and inserts their credit card. The screen displays a menu where the user selects the Rav Kav option. The machine instructs the user to remove the credit card and insert the Rav Kav card into the slot. The ATM communicates with the national clearinghouse, locates the pending reservation, and writes the contract directly to the chip. This physical connection bypasses the radio frequency vulnerabilities of smartphone NFC sensors.

Financial Limits and Refund Procedures

The Ministry of Transport enforces strict financial parameters on the smart card. The physical chip cannot hold more than 1000 Israeli New Shekels. The system calculates this limit based on the final stored value, not the purchase price. For example, a youth profile grants a fifty percent discount. If a user with a youth profile attempts to buy 100 Shekels of stored value, the system tries to load 200 Shekels onto the card. If the card already holds 900 Shekels, the new total would reach 1100 Shekels. The application blocks the transaction. This hardcoded limit prevents massive financial losses if the card is misplaced.

Users can cancel contracts directly through the mobile application. The software evaluates the usage history of the specific contract. Unused contracts qualify for an immediate and full refund. A daily pass qualifies for cancellation if the user scanned it only once. Monthly passes qualify if the user scanned them up to three times. The application processes the refund directly to the original payment method. The user must tap the card against the phone to delete the canceled contract from the physical chip. If the user cancels a purchase outside of these specific parameters, the Consumer Protection Law dictates a cancellation fee amounting to five percent of the transaction price or 100 Shekels, whichever is lower.

Application Ecosystem and Operator Integration

Two primary applications dominate the digital reload market. Pcentra Ltd operates Rav Kav Online. Spark by MWM operates HopOn Rav Kav. Both applications connect to the same national clearinghouse. The user experience remains consistent across both platforms. They accept major credit cards, debit cards, and Apple Pay. The applications also allow users to update their demographic profiles. A user can scan their card, upload a student identification document, and receive the mandated transit discount without visiting a physical service station.

The system distinguishes between personal and anonymous cards. Personal cards contain the user photograph and link to a central database. If a user loses a personal card, they pay a 10 Shekel replacement fee. The operator problem a new card and restores the exact balance from the lost card. Anonymous cards do not link to a user identity. If a user loses an anonymous card, the stored value disappears permanently. The applications permit NFC reloading for both card types, they restrict monthly passes to personal cards only.

Data Verification and Transaction Metrics

The national clearinghouse processes millions of NFC transactions monthly. The success rate of the secondary tap depends heavily on user behavior and hardware quality. We compiled the transaction resolution data for pending reservations across the network.

The data indicates that users resolve the majority of write failures on the same device. The secondary tap requires precision. Users who understand the hardware limitations experience fewer transaction errors. The digital infrastructure secures funds even when the physical connection drops. The integration of the national clearinghouse guarantees that users can access their purchased contracts through multiple hardware channels.

Phase Eight Auditing and Digital Receipt Archival

Once a passenger completes a transit payment via a smartphone application, the system initiates the auditing phase. The application records the transaction details and generates a digital receipt. Passengers rely on these records for personal accounting, tax documentation, and employer reimbursement. The Israeli public transportation network processes millions of transactions daily. Accurate digital archiving ensures passengers can verify their charges and dispute any billing errors.

Core Inquiries Regarding Transaction Auditing

Transaction Verification and App Functions

The Rav Kav Online and HopOn applications read data directly from the smart card chip. When a user scans their card against the back of their smartphone, the Near Field Communication sensor extracts the most recent travel data. The screen displays the remaining stored value, the expiration dates of periodic contracts, and the recent ride history. The HopOn application specifically shows the charge amount, the bus line number, the boarding station, and the travel time.

Passengers frequently need official documentation for their purchases. When a user buys a contract through the Rav Kav Online platform, the system sends a confirmation and a digital receipt to their registered email address. This receipt serves as a valid tax invoice. Bus operators like Egged do not generate tax invoices for transactions processed through third party applications. If a passenger uses the HopOn or Rav Kav Online app, they must request their tax documents directly from that specific software provider.

Employer Reimbursement Regulations in Israel

Israeli labor laws mandate that employers compensate their workers for commute expenses. The calculation relies on the cheapest available public transportation fare, which is a monthly transit pass. As of September 2021, the government caps the mandatory daily employer contribution at 26. 40 New Israeli Shekels. Employers can choose to pay more than this mandated minimum.

Employees do not need to submit physical paper receipts to receive this standard travel allowance. The human resources department calculates the required payment based on the days the employee actually travels to the workplace. If an employee requires specific tax invoices for independent accounting or exceptional travel expenses, the digital archives within the transit applications provide the necessary proof of purchase.

Dispute Resolution and Failed Transactions

Technical errors occasionally disrupt the payment process. A user might experience a situation where the application deducts funds from their bank account, yet the smart card fails to update with the new contract. In these scenarios, the system detects the incomplete transfer and automatically cancels the credit card charge.

If the automatic refund fails, passengers have distinct avenues for resolution. The Rav Kav Online platform includes a built in cancellation feature that allows users to void a recent purchase and receive an instant refund. For persistent billing errors, passengers can visit an Al HaKav service station. The representatives at these physical locations can read the card data, verify the error, and process a manual refund to the original payment method.

Data Retention and Card Types

The type of smart card dictates the volume of archived data. A personal card stores the user identification and maintains a secure backup of all active contracts in the central database. If a passenger loses their personal card, they can pay a 10 New Israeli Shekels replacement fee and restore their entire balance and transaction history.

Anonymous cards operate differently. These cards cost 5 New Israeli Shekels and do not link to any personal user data. The system does not insure the balance on an anonymous card. If a passenger loses an anonymous card, the stored value and the transaction history disappear permanently.

Data Privacy and Archival Security

The transition to digital transit payments introduces strict data privacy requirements. The Ministry of Transportation oversees the central database that archives all personal card transactions. When a passenger uses a smartphone application to load a contract, the software encrypts the payment details before transmitting the data to the central servers. The physical smart card only stores the most recent travel logs and the active contract data. This separation ensures that if a passenger loses their card, unauthorized individuals cannot access their complete historical travel patterns or financial information.

Passengers who prioritize absolute privacy frequently choose the anonymous card option. These cards require no identification during the purchase process. The absence of personal data means the central database cannot link specific travel routes to an individual user. The trade off for this privacy is the complete loss of funds if the card goes missing. The transit authorities cannot verify the ownership of an anonymous card, making balance restoration impossible.

Corporate Travel and Expense Management

Israeli corporations manage travel expenses through structured reimbursement procedures. The national labor laws dictate specific compensation rules for employees commuting to the workplace. The human resources department calculates the travel allowance based on the cost of a monthly transit pass or the daily bus fare, whichever is cheaper.

Employees traveling for specific business purposes follow different reporting procedures. If a worker attends a client meeting or travels to a remote site, they must submit exact receipts for their transit costs. The digital archives within the HopOn and Rav Kav Online applications become essential for these expense reports. The employee exports the digital tax invoice from the application and submits it to their accounting department. The accounting team verifies the transaction date, the route, and the total cost before processing the reimbursement.

Advanced Troubleshooting for Failed Loads

The Near Field Communication loading process requires a stable connection between the smartphone and the smart card. If a user moves the card too quickly during the data transfer, the payment might clear the bank while the contract fails to write to the physical chip. The transit applications employ automated reconciliation systems to handle these exact scenarios. The software compares the successful bank charges against the confirmed card updates. If the system identifies an error, it automatically triggers a refund to the original payment method.

When the automated reconciliation fails, the passenger must initiate a manual dispute. The user opens the application, navigates to the transaction history, and selects the failed purchase. The Rav Kav Online platform allows users to cancel a pending or failed contract directly from this menu, resulting in an immediate refund. If the application cannot resolve the error, the passenger must travel to an Al HaKav service station. The station representatives possess advanced diagnostic tools that read the corrupted card data, verify the missing contract, and manually correct the balance.

Transaction Resolution Metrics

The following chart illustrates the standard processing times for various customer service requests related to transit payments. The data reflects typical resolution windows reported by transit authorities between 2020 and 2026.

Diagnostic Fan-Out: 20 Core Troubleshooting Inquiries

We present twenty specific questions and verified answers regarding error codes and write failures for the Rav-Kav system.

Hardware Interference and NFC Sensor Calibration

The physical mechanics of the NFC write process demand precision. The smartphone must maintain a continuous connection with the card during the entire transaction. Moving the device prematurely severs the connection. This action results in a failed write. The application reserves the transit contract cannot transfer the data to the chip. Users frequently cause this error by pulling the phone away immediately after hearing the initial connection tone. The data transfer requires several seconds to complete. Users must place the card on a flat surface. They then rest the smartphone directly over the card. This method stabilizes the radio frequency link. Thick protective cases or cases containing metal components block the radio frequencies required for NFC communication. Removing the phone case fixes the majority of connection problems. The application displays a specific error code when the hardware fails to establish a secure handshake. Passengers must follow the on-screen prompts to reset the NFC module before attempting a second scan.

NFC Write Error Distribution by Hardware Configuration

The following data table illustrates the recorded error frequencies across different smartphone and card manufacturer combinations.

Identifying Manufacturer Specific Chip Failures

The Ministry of Transport distributes cards produced by five primary manufacturers. The manufacturer name appears in the top right corner on the back of the physical card. The primary manufacturers include ASK, ASK Tango, OTI, Watchdata, and Gemalto. The Rav-Kav Online documentation confirms that ASK cards experience high failure rates when paired with iPhone XR and XS models. The internal NFC antenna on these specific smartphones fails to synchronize with the ASK chip architecture. Users facing this hardware incompatibility must visit an Al-HaKav station. They can exchange their ASK card for a Watchdata or Gemalto card at no additional cost. The representative transfers all existing balances and valid profiles to the new card. Older Apple devices present a different hardware limitation. iPhone 6 and SE models do not support NFC writes. Users require an iPhone 7 or newer running iOS 13 or higher to use the mobile reload feature.

Financial Discrepancies and Ghost Charges

Passengers frequently express concern about being charged for a failed reload. When a user initiates a reload, the payment gateway performs a credit limit check. The bank shows a pending charge on the user account. The actual capture of funds only occurs after the application confirms a successful NFC write to the card. If the write fails, the system voids the transaction. The pending charge disappears from the bank statement within three business days. The application does not finalize the payment for an incomplete transfer. If a user encounters a persistent write failure, they can complete the transaction at a Casponet ATM. The ATM retrieves the reserved contract from the cloud and writes it to the card. Passengers can also load the reserved contract onto their card using a different smartphone. If a passenger receives an incorrect charge from a validation error on a bus or train, they can request a refund. They contact the Egged national public call center at *2800 or visit an Al-HaKav service station to process the reimbursement. The automated refund process credits the original payment method directly. Passengers must provide the specific date and time of the failed transaction to expedite the investigation.

Card Expiration and Profile Lockouts

Personal Rav-Kav cards expire exactly eight years after the date of creation. The application alerts the user when they scan an expired card. The physical chip stops accepting new contracts. The stored value remains intact on the server. Users must order a replacement card through the application or visit a service station. The system transfers all existing balances to the new card. Discount profiles expire independently of the physical card. A youth profile expires when the user turns 18. A student profile requires annual renewal. Users upload current documentation through the Rav-Kav Online application to renew their discount profile. If a user fails to renew their student profile, the system automatically reverts their account to a regular profile. The application then blocks access to any stored value purchased at the discounted student rate. The application also rejects reserved contracts if the card already contains a contract that offers a better discount for the user. This logic prevents passengers from overpaying for transit services. Passengers retain full control over their profile status by monitoring the expiration dates displayed within the mobile application interface.

Core Inquiries for Financial Disputes and Support

We present twenty specific questions and verified answers regarding financial disputes and customer service procedures for the transit payment network.

Escalation Procedures for Failed Transactions

Financial errors occur when the smartphone NFC sensor loses connection with the smart card during the write sequence. The payment gateway authorizes the charge. The application fails to write the travel contract to the physical chip. Passengers face a situation where their bank account shows a pending charge. Their transit card remains empty. The National Public Transport Authority established specific procedures to resolve these matters. Passengers must not attempt to validate an empty card on the bus. Drivers cannot resolve digital application errors. The Ministry of Transport strictly prohibits drivers from handling digital payment disputes. Passengers must follow a strict hierarchy of communication to recover their funds.

The step involves contacting the specific application developer. The Rav-Kav Online platform requires users to send an email to support@ravkavonline. co. il. Passengers must include the email address registered to their account. They must provide the smart card number and the exact time of the failed transaction. Users of the HopOn application must direct their correspondence to support@hopon. co. il or support@ravpass. co. il. The application developers maintain direct access to the national clearinghouse. They can verify if the travel contract reached the physical card. If the system confirms a failed write sequence, the developer cancels the pending credit card charge. The funds return to the passenger within standard banking timeframes.

When application developers fail to resolve the matter, passengers must escalate the dispute to the transit operators. Egged operates a national call center at *2800. Passengers can also visit physical Al-Hakav service stations. Representatives at these stations possess specialized hardware. They can read the exact memory sectors of the smart card. They can manually restore missing contracts if the national database shows a valid purchase. The official pti. org. il website provides a complete map of active service stations. Passengers must present valid government identification when requesting manual contract restoration at these locations.

The final escalation tier involves the Ministry of Transport. The National Public Transport Authority operates the *8787 hotline. Passengers use this channel when operators and application developers deny a valid refund request. The Ministry maintains authority over the national clearinghouse. They can force operators to reverse charges or restore travel contracts. The Ministry requires passengers to submit documented proof of their communication with the application developers before initiating a formal investigation.

Consumer Protection Law and Cancellation Fees

The Israeli Consumer Protection Law governs all digital transit purchases. Passengers hold specific legal rights when canceling travel contracts. The law permits users to cancel a purchase and receive a refund. The operator deducts a cancellation fee. This fee amounts to 5 percent of the transaction price or 100 ILS. The operator must apply the lower amount.

Passengers can execute these cancellations directly through the Rav-Kav Online application. The contract must remain valid and meet strict usage criteria. A daily pass qualifies for cancellation only if the passenger used it exactly once. A monthly, annual, or semester pass qualifies if the passenger used it up to three times. Unused contracts qualify for immediate cancellation.

The Ministry of Transport established a national clearinghouse to process these refunds. Passengers who lose their cards must visit a physical service station to restore their data. The clearinghouse synchronizes transaction records across all public transport operators. This synchronization ensures that a contract purchased through Egged remains visible to Dan or Kavim representatives. The system prevents double billing and ensures accurate data recovery.

When a passenger requests a refund through the digital application, the system presents an alternative option. Users can choose to donate their remaining balance. This action bypasses the requirement to enter payment details for a refund transfer. The donation does not generate a tax credit receipt. Passengers seeking tax credits must donate funds independently. The application developers implemented this feature to clear micro-balances from the national database.

Standardized Communication Scripts for Passengers

Passengers frequently experience delays when they submit incomplete information to customer service centers. We provide verified communication templates. These templates include all mandatory data fields required by the national clearinghouse. Passengers must copy these templates and fill in their specific details. Using standardized formats reduces processing time and prevents automated rejections by customer support software.

Template 1: NFC Write Failure with Pending Charge

Subject: Failed NFC Reload, Pending Charge Reversal Request

To the Support Team,

I attempted to load a travel contract onto my smart card using your application. The payment gateway authorized the charge. The NFC write sequence failed. The contract does not appear on my card. I request an immediate reversal of the pending credit card charge.

Registered Email: [Insert Email]

Card Number: [Insert 16-digit Number]

Date and Time of Attempt: [Insert Date and Time]

Attempted Contract: [Insert Contract Type, e. g., Daily Pass]

Please confirm the cancellation of this charge.

Template 2: Lost Personal Card Balance Transfer

Subject: Lost Personal Card, Balance Transfer Request

To the Al-Hakav Service Center,

I lost my personal smart card. I need to order a replacement and transfer my existing balance. I understand there is a 10 NIS fee for the new plastic card. I have attached a copy of my government identification.

Previous Card Number: [Insert Number if known]

Identification Number: [Insert ID Number]

Full Name: [Insert Exact Name on Card]

Please process the replacement and restore my stored value and active contracts.

Template 3: Ministry of Transport Escalation

Subject: Operator Dispute Escalation, Unresolved Charge

To the National Public Transport Authority,

I am escalating an unresolved financial dispute with a transit application developer. The application charged my bank account. The travel contract was never written to my card. The developer has not reversed the charge after five business days. I request your intervention to resolve this matter.

Operator Name: [Insert Application Name]

Card Number: [Insert Number]

Transaction Date: [Insert Date]

Disputed Amount: [Insert Amount in ILS]

I have attached the original receipt and the email chain with the developer.

Resolution Timeframes for Financial Disputes

Data from the transit network shows clear patterns in dispute resolution. The majority of failed transactions resolve automatically. The payment gateway detects the failed write sequence and voids the charge within one hour. Cases requiring human intervention take significantly longer. We present a breakdown of expected resolution times based on the escalation tier.

Contingency Procedures for NFC Hardware Failures

Smartphone hardware fails. Near Field Communication sensors degrade over time. Software updates frequently break compatibility with transit payment applications. Passengers require immediate alternatives when their primary digital reload method malfunctions. The Israeli Ministry of Transportation maintains a physical infrastructure network to ensure continuous transit access. This network includes automated teller machines, retail kiosks, dedicated service centers, and desktop hardware. We examine the exact specifications and locations of these backup systems. The transition away from cash payments on buses forces every passenger to understand these physical alternatives. A dead battery or a corrupted NFC chip can strand a commuter. The physical reload network prevents this outcome.

Alternative Reloading Contingencies: 20 Core Inquiries

The Casponet Automated Teller Network

The Casponet network provides the most widespread physical backup for transit payments. Thousands of these automated teller machines operate in convenience stores, supermarkets, and shopping centers throughout Israel. Passengers facing smartphone failures can use these machines to load stored value or specific contracts. The direct reload process requires a specific sequence. The user inserts the payment card into the machine. The screen displays a dedicated transit menu. The user selects the reload option and removes the credit card. The user then inserts the transit card into the same slot. The machine writes the new contract directly to the golden chip. This mechanical process bypasses any need for wireless communication.

The Casponet system also supports a delayed load feature. Passengers can purchase a contract through the official website using a computer without a card reader. The system holds this contract in a pending state on the central servers. The passenger then visits any Casponet ATM. They insert their transit card directly into the machine. The ATM connects to the central server, retrieves the pending contract, and writes it to the physical card. This method eliminates the need to insert a credit card into the public machine. It protects financial data while ensuring the transit card receives the purchased funds. The ATM network operates continuously. It provides a reliable contingency during late hours when retail locations close.

Desktop Hardware and USB Card Readers

Passengers who prefer to manage their transit accounts from home can use a dedicated USB card reader. This hardware provides a direct connection between a personal computer and the transit authority servers. The official card reader costs 10 NIS. Passengers can purchase this device at any Al Kav service center. The reader connects to a standard USB port. The user navigates to the official transit website and places their card into the reader. The website communicates with the card through the golden contact chip. The system reads the current balance and displays available contracts.

This desktop method bypasses the need for a smartphone entirely. It provides the exact same functionality as the mobile application. Users can check their balance, review their last six travel logs, and purchase new contracts. The desktop system requires a stable internet connection. It also requires a transit card equipped with the standard golden chip. Older cards without this chip cannot interface with the USB reader. Passengers holding older cards must visit a service center for a free replacement. The USB reader represents a single investment. It guarantees reload access even if a mobile device is lost or stolen. The software supports standard operating systems and requires no complex installation procedures.

Retail Kiosks and Pharmacy Terminals

The Ministry of Transportation licenses third party retailers to process transit payments. Over 1, 200 kiosks operate across the country. Major retail chains participate in this program. AM: PM convenience stores and Super Pharm pharmacies maintain dedicated transit terminals at their cash registers. Selected post offices also provide this service. Passengers hand their card to the cashier and specify their desired contract. The cashier processes the payment and places the card on a specialized terminal to write the data. The terminal confirms the transaction with a printed receipt.

This retail network provides an essential service for passengers who rely on cash. Most automated machines at bus stops and train stations no longer accept paper currency. Retail cashiers accept cash payments and load the equivalent value onto the smart card. The maximum stored value limit remains 1, 000 NIS across all reload methods. If a cash payment exceeds this limit, the terminal rejects the transaction. Retail locations also sell anonymous cards for 5 NIS. Tourists and temporary visitors frequently use this option. They purchase the card and load it with cash in a single transaction. The retail network the gap between digital payments and physical currency.

Al Kav Service Centers and Terminal Infrastructure

Severe hardware failures require professional intervention. When a transit card suffers physical damage or internal chip corruption, automated machines cannot process reloads. Passengers must visit an Al Kav service center. These dedicated offices operate at central bus stations and major train terminals. Tel Aviv hosts several locations, including a primary office at 35 Ibn Gabirol Street. Service center representatives possess the authority to extract data from damaged cards. They transfer existing balances to a new card. This recovery process protects the passenger from financial loss.

Service centers also handle profile modifications. Passengers eligible for senior citizen discounts or student rates must verify their status. The representatives update the internal profile on the card. Once the profile is updated, all subsequent reloads automatically apply the correct discount. Automated machines and retail kiosks cannot process these initial profile verifications. They only read the existing profile and apply the predetermined rates. The service centers serve as the final authority for account management. They resolve discrepancies that automated systems cannot handle. Passengers facing persistent errors with their smartphone applications frequently find resolution at these physical desks.

Anonymous Versus Personal Card Contingencies

Hardware failures expose the serious differences between anonymous and personal transit cards. An anonymous card contains no identifying information. It costs 5 NIS and allows immediate use. If this card suffers physical damage or the internal chip fails, the passenger loses all stored value. The transit authority cannot verify ownership. They refuse to process a refund. The passenger must purchase a new card and forfeit the previous balance. This strict policy prevents fraud penalizes legitimate users during hardware malfunctions.

Personal cards provide complete financial protection during hardware failures. These cards display the passenger photograph and name. The central server links the card number to a national identification number. If a personal card fails, the passenger visits an Al Kav service center. The representative verifies the passenger identity. The system invalidates the broken card and transfers the exact balance to a new card. The replacement process takes minutes. This security method makes the personal card the superior choice for residents. It guarantees that a hardware failure only causes a temporary inconvenience rather than a permanent financial loss.

Distribution of Alternative Reload Infrastructure

The physical reload infrastructure relies on a diverse distribution of machines and service points. The following chart illustrates the verified distribution of alternative reload locations available to passengers. The data reflects the current operational status of the transit network.

The data confirms that automated teller machines provide the vast majority of physical reload points. Retail kiosks offer the secondary of support. Dedicated service centers represent the smallest fraction of physical locations. Passengers must plan their contingencies based on this distribution. A failed smartphone application requires immediate access to one of these physical nodes. The Ministry of Transportation continues to maintain this hardware network to prevent transit lockouts. The system ensures that no passenger is denied boarding due to a temporary digital malfunction.

The physical reloading of a Rav Kav card via a smartphone Near Field Communication sensor represents only one component of the digital transit ecosystem in Israel. Once a passenger writes new contract data to the smart card, the step involves route planning. Applications use data provided by the Ministry of Transport to calculate fares and predict arrival times. The Ministry of Transport maintains two primary data feeds. The General Transit Feed Specification provides static schedule data. The Service Interface for Real Time Information protocol delivers live updates. Developers use these datasets to build applications that allow users to check balances, reload cards, and plan journeys within a single interface.

The Ministry of Transport updates the static General Transit Feed Specification files every night. These files reside on a dedicated government server and contain comma separated values detailing routes, stops, and planned schedules. The live Service Interface for Real Time Information feed updates every five minutes. This live feed provides service alerts and vehicle positions. Applications like Moovit and HopOn Rav Pass consume these feeds to offer accurate transit information to passengers.

Core Route Planning and Data Integration Inquiries

We present twenty specific questions and answers regarding the integration of Rav Kav reloading with route planning datasets.

The integration of payment systems and route planning relies heavily on accurate data. When a passenger uses a smartphone to read a Rav Kav card, the application retrieves the current balance and active contracts. The user then inputs a destination. The application queries the static schedule files to find available routes. It cross