Bank Otsar Hahayal¶
CompanyTypes | OtsarHahayal |
| Engine | Browser (Pipeline) |
| Credentials | username, password (plus otpCodeRetriever callback in options) |
| OTP | Required |
| Phase chain | INIT → HOME → LOGIN → OTP-TRIGGER → OTP-FILL → BIND-API-MEDIATOR → API-DIRECT-SCRAPE → TERMINATE |
| Source | Banks/OtsarHahayal/OtsarHahayalPipeline.ts |
Known quirks¶
- Part of the Beinleumi group — same OTP-TRIGGER + OTP-FILL flow as Beinleumi, Massad, Pagi.
- Balance is single-bank-account (
balanceKind: ACCOUNT), resolved by the hard-model balance step.
Hard-model post-auth¶
After login, Otsar Hahayal uses the hard-model post-auth path (withBrowserApiDirect): instead of the generic AUTH-DISCOVERY / ACCOUNT-RESOLVE / DASHBOARD / SCRAPE / BALANCE-RESOLVE chain, the OTSAR_HAHAYAL_SHAPE IApiDirectScrapeShape (Banks/OtsarHahayal/scrape/OtsarHahayalShape.ts) declares the exact accounts, balance, and transactions API calls, issued directly through the live login page. AUTH-DISCOVERY's cross-origin postLoginNav navigates to the appsng SPA shell (/appsng/Resources/PortalNG/shell/#/accountSummary) first, minting the online-origin session so the cookie-authed fetches don't fire on a blank page. See api-direct-scrape for the phase contract.