| Currencies / wallet format | Current application form lists 14 currencies: USD, GBP, EUR, AUD, CAD, SGD, SEK, HKD, JPY, AED, CHF, NOK, NZD and ZAR. | Current YES BANK Visa MCTC material lists up to 14 wallets: USD, GBP, EUR, CAD, AUD, SGD, AED, JPY, SAR, THB, CHF, ZAR, NZD and HKD. Current BookMyForex card material also uses a 14-wallet authorization structure. |
|---|
| Purchase eligibility | Application is tied to an IDFC FIRST Bank account and requires PAN, passport, travel dates/countries, source of funds and FEMA/FETERS purpose. Insta Card and personalized card issuance are both supported. | Travel-only prepaid product subject to branch KYC/passport/travel verification. Current migration page states existing holders can request replacement and new travellers can visit branches for a card. |
|---|
| Load / reload | Current form supports initial issuance and reload. The customer authorizes debit to the linked IDFC FIRST account for the requested currency amount plus applicable service charges/taxes/TCS. | Reloadable subject to FEMA limits. Exact fee depends on the live card programme: current BookMyForex standard schedule lists ₹0 reload while older legacy MCTC material lists ₹100; these are deliberately not merged. |
|---|
| Exchange rate | IDFC FIRST publishes a live exchange-rate table with dedicated Forex Card Bank Buys and Bank Sells columns. The applicable rate is market-linked and should be taken from the bank's current card rate at processing. | YES BANK states the final applicable card rate is the rate prevailing at transaction/processing and may differ from displayed website rates. Conversion from one wallet/currency to another follows the applicable card/programme rate. |
|---|
| ATM cash | The product is a prepaid travel card intended for overseas use, but v1.53 leaves current ATM fee and cash-withdrawal ceilings unfilled because no complete live first-party card-specific table was verified. | Currency-specific ATM fees and limits apply. Current BookMyForex schedule, for example, lists USD 2 ATM withdrawal and USD 1 balance enquiry with USD 1,000 daily ATM ceiling; legacy MCTC schedules differ. |
|---|
| POS / e-commerce | Multi-currency prepaid travel-card use is supported for overseas spend. Channel-specific current limits are not inferred from debit- or credit-card schedules. | Designed for overseas POS/e-commerce/ATM use. BookMyForex FAQs describe wallet-priority authorization and decline where no single wallet has sufficient funds; DCC usage should be avoided. |
|---|
| Cross-currency | Cross-currency conversion can apply when spending outside the loaded wallet structure; the exact current card-specific percentage is not asserted from generic bank blog examples. | Current BookMyForex schedule lists 3.5% cross-currency markup. Older legacy MCTC schedule shows 2.75%, so the rate must be tied to the actual issued/replacement card programme. |
|---|
| Wallet conversion | Multiple listed currency wallets are supported. Current first-party forms do not expose a complete public wallet-to-wallet fee table, so v1.53 keeps this field qualitative. | Card uses a defined currency-authorization order when matching wallet funds are insufficient. Cross-currency conversion applies and partial aggregation across multiple insufficient wallets is not allowed. |
|---|
| Fees | Applicable service charges, taxes and TCS are acknowledged by the current application form. Exact current issuance/reload/ATM/refund figures are not populated without a verified current card-specific schedule. | Programme-specific. Current BookMyForex standard schedule: ₹0 issuance/reload/refund, 3.5% cross-currency, ₹250 India replacement and ₹3,000 overseas replacement; older legacy YES MCTC has different fees. |
|---|
| Refund / closure | IDFC FIRST publishes a current encashment form supporting partial refund, full refund and full refund with card closure to an IDFC FIRST Bank account. | Current migration page provides branch support for card balance/status. BookMyForex standard schedule lists ₹0 refund fee, while legacy MCTC terms historically differed. |
|---|
| Replacement / emergency | Current change-request and dispute forms support card servicing; card-loss/dispute handling is documented. Exact emergency/replacement pricing remains source-gated. | Migration workflow specifically requires replacement for continued use of affected/legacy cards. Existing balances/details are transferred to the replacement card; replacement pricing depends on programme. |
|---|