| Topic | Situations when betaclient is useful |
|---|---|
| Default Test client | You want a non-sensitive full test client, consistent in UAT and PROD environment |
| Test without data anonymisation | With betaclient you can test without data anonymisation |
| You need a complete client | You need a client with eBanking, LEI (Legal Entity Identifier), MiFID II details, securities account, FIX, EBICS, FX, EQ, ETD, … |
| Multi-Banking | you need to test with a client that has accounts at various banks |
| Feature toogle in production | You want to ship early and often. You don’t want to spend too much time testing in test environment. Use feature toggle to enable the feature just for client betaclient |
| Guinea Pig | You’ve shipped an exciting new feature. No client has used it so far. betaclient might use it as the first real client |
| On request transaction | You need a transaction in production environment outside the normal business hours (e.g. Sunday at 22:00 CET) |
| Notifications | Sometimes E-Mails or SMS could accidentally be sent from the test environment to real clients. Mitiage this risk by using betaclient as a non-sensitive client |
| Client output (docs) | Only few bank employees see the real production document output result for clients. Relax those restrictions for betaclient |
| Trouble Shooting | You need to reproduce some error. Use betaclient to reproduce the issue in prod environment |
| Trouble Shooting | You need to send logfiles that might include client data to company in the U.S. but you’re not allowed to. |
.