Bank Account
Optional holder name, IBAN, account number, bank/institution, branch and SWIFT/BIC.
Triplem VIP
Optional bank, wallet and card details built into Expenses accounts
Keep useful identification fields beside each account while limiting payment-card storage to safe last-four references and using concise details in transfers and PDFs.
Holder details IBAN & account Last four only Masked PDFs
Financial account details
Store useful account context without turning a wallet into a credential vault.
Triplem VIP lets users add optional details according to account type so records, transfers and PDFs can carry the context that actually helps identify an account.
Cash Account
Optional custodian, cash location, cash box/register ID, purpose and internal reference.
Travel Card
Optional card holder, last four digits, Tag ID, card tier, issuer/operator and expiry month.
Debit / Credit / Prepaid
Optional card holder, last four digits, issuer, network, expiry and type-specific account context.
Cheque / Savings
Optional holder, IBAN, account number, institution, branch and account-specific reference fields.
Digital / Crypto / Other
Optional provider, holder, wallet or account reference, registered contact context, network/memo where relevant and custom references.
Card-data boundary
Payment cards are deliberately limited to the last four digits.
The optional-details model is designed for identification and audit context, not for storing full payment-card credentials.
Triplem VIP normalizes card input so only the final four digits are retained. Legacy or test values that resemble a full card number are reduced to their final four digits by the current client data-normalization path.
Full PAN, CVV and PIN are not part of the account-detail model. Customer-facing displays and PDFs use masked card formatting such as xxxx-xxxx-xxxx-1234 rather than a full card number.
StoredLast four onlyEnough to identify a card without retaining its full PAN.
ExcludedNo CVV or PINAuthentication secrets are not normal account-detail fields.
PDFMasked card referenceMinimal account context is used in exported records.
EditableExisting wallets can be enrichedOptional details can be added or updated through account editing.
Where details appear
Account context follows the places where it is useful.
Account Details overlay
Opening a wallet can expose a dedicated account-details view with the optional information recorded for that account.
Transfers
Wallet-to-wallet transfers can show concise account context so users can identify the source and destination more confidently.
Wallet PDFs
Statements use minimal useful details such as IBAN and holder or masked card reference rather than dumping every optional field.
Receiving / Add Money
Add Money records in Receiving support separate optional source, method, institution, reference, payer, purpose and document fields.
Expense records
Expenses can carry merchant, paid-to, payment method, reference, invoice/receipt, project, cost center, beneficiary, location and business-purpose context.
Internal Transfers
Internal Transfers can carry transfer method, channel, institution, reference, purpose, recipient, project, cost center, location and document context.
Audit usefulness
Optional does not mean decorative.
Structured context improves searching, human review, receipt identification and downstream audit evidence without changing the underlying transaction amount.
Practical principle.
Record only details that help identify, explain or reconcile the account or transaction. Never place passwords, PINs, recovery codes, private keys or other authentication secrets into free-form account or transaction fields.
Account-detail questions
Useful context without turning account records into a credential store.
Which bank details can be recorded?
Relevant bank accounts can carry optional holder name, IBAN, account number, institution, branch and SWIFT/BIC so the wallet is easier to identify in records and exports.
Does Triplem VIP retain a full card number?
The current optional card-detail model retains only the final four digits for identification. Full PAN, CVV and PIN are not normal account-detail fields.
What appears in relevant PDFs?
Exports use minimal useful account context, such as holder and IBAN where appropriate or a masked card reference, rather than exposing every optional field.
Can an existing account be enriched later?
Yes. Existing wallets can be edited to add or update the optional details appropriate to their account type without changing the underlying transaction history.
Global currency support
International finance for India, Europe and users worldwide.
Triplem VIP is designed for international personal and business finance. Current supported currencies include AED, SAR, PKR, USD, EUR, INR and BTC where applicable, while regional subscription pricing can present a locally supported billing currency.
India with INR
Users in India can work with Indian Rupee (INR / ₹) across supported multi-currency finance workflows and regional subscription pricing.
Euro-region support
Users in Belgium and other countries where the euro is used can work with EUR / € in supported finance workflows and regional subscription pricing.
Need another currency?
Triplem VIP is built to serve users in any country. If your currency is not currently available, contact Triplem VIP and support can review adding it for your country.
Currency availability can expand as user demand grows. USD remains the regional default where another supported local billing currency does not apply. Tax, reporting and statutory requirements still depend on the user’s jurisdiction.