- Add multi-invoice payment support (link one bank transaction to multiple invoices) - Add payment unlinking feature to correct wrong matches - Show linked payments, invoices and bank entries in transaction detail view - Allow linking already paid invoices to bank transactions - Update README with new features - Add CHANGELOG.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
27 lines
1.2 KiB
PHP
Executable file
27 lines
1.2 KiB
PHP
Executable file
<?php
|
|
/** @noinspection PhpUnused */
|
|
|
|
namespace Fhp\Model;
|
|
|
|
/**
|
|
* For two-step authentication, users need to enter a TAN, which can be obtained in various ways. After choosing one of
|
|
* these ways, i.e. choosing a a {@link TanMode} (SMS, TAN generator device, and so on), the user might have to choose
|
|
* which of their TAN media they want to use within this mode, in case they have multiple. For instance, a user might
|
|
* have multiple mobile phone numbers configured for smsTAN, might have multiple TAN generators, or multiple iTAN lists.
|
|
* Each {@link TanMedium} instance describes one of these options.
|
|
*/
|
|
interface TanMedium
|
|
{
|
|
/**
|
|
* @return string A user-readable name for this TAN medium, which serves as its identifier at the same time. This is
|
|
* what the application needs to persist when it wants to remember the users decision for future transactions.
|
|
*/
|
|
public function getName(): string;
|
|
|
|
/**
|
|
* @return string|null In case this is a mobileTAN/smsTAN medium, this is its (possibly obfuscated) phone number.
|
|
*/
|
|
public function getPhoneNumber(): ?string;
|
|
|
|
// TODO Consider making more information from TanMediumListeV4 available here.
|
|
}
|