> For the complete documentation index, see [llms.txt](https://ambr4-scripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ambr4-scripts.gitbook.io/docs/scripts/banking-system/changelog.md).
# Changelog
Update: v1.0.2
**New Features**
* Added physical bank cards as real inventory items.
* New accounts can now issue their own matching bank card item.
* Added configurable physical card support through `Config.PhysicalCards`.
* Added configurable ATM card requirement support.
* Players can now be required to carry the correct account card to use ATM withdrawals.
* Added per-account-type card item support through `Config.AccountTypes`.
* Each account type can now use its own separate physical card item.
* Added card status actions directly inside the `Card Details` section.
* Added `Block Card` and `Unlock Card` actions through the card status dropdown.
* Added full replacement card flow through `New Card`.
* Replacement cards now keep the same account and IBAN while generating a new card number, new CVC, and a new PIN.
* Replacement cards now return to `Inactive` status until signed again.
* Old cards now stop working after a replacement card is issued.
* Added support for stolen card gameplay.
* Players can now use stolen physical cards at ATMs if the card is still valid and not blocked.
* If the account requires a PIN, the correct PIN must still be entered before access is granted.
* Stolen card access now appears separately inside the ATM interface under its own access section.
* External card balances are now hidden until the card is successfully authenticated.
* Account owners can now protect themselves by blocking lost or stolen cards directly from the banking UI.
**Interface Updates**
* Updated ATM account selection spacing and layout behavior.
* Improved ATM scrollbar spacing for a cleaner and more consistent look.
* Added separate ATM account access display for external card usage.
* Improved card interaction flow inside the `Card Details` module.
⚠️ Update is live. If you don’t see it immediately, give it a few minutes to propagate.
Update: v1.0.1
**Fixed**
* Main account balance now updates correctly after **deposit**, **withdraw**, and **transfer** actions.
* Cash and bank values now sync properly with the real QBCore `players.money` data.
* Banking UI no longer shows outdated main account balances after transactions.
* Receiver and sender balances now update correctly when transferring money between accounts.
* Main account data now follows native QBCore money behavior more accurately.
**Improved**
* Main account money flow was adjusted to use the proper QBCore-style handling for bank and cash changes.
* Balance refresh after successful actions is now more reliable in the banking UI.
* Main account balance rows are now kept aligned with the actual framework bank balance.
**Result**
* If money is added or removed through the banking UI, it now updates correctly in:
* the QBCore player money data
* the banking UI
* the main account balance records
⚠️ Update is live. If you don’t see it immediately, give it a few minutes to propagate.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ambr4-scripts.gitbook.io/docs/scripts/banking-system/changelog.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.