Use cases provide a set of requirements for processing financial transactions, such as merchant payments, bill payments, or commission settlements. A fee type use case configuration identifies the fee type based on organizational unit and payment instrument for both the payee and payer. A use case is linked to one or more fee types.
| Field | Description |
|---|---|
| Use Case | Indicates the use case for which this fee applies. |
| OrgUnit Payee | Indicates the organizational unit of the payer. |
| OrgUnit Payer | Indicates the organizational unit of the payee. |
| PI Type Payee | Indicates that this fee is applicable only to transactions where the payee’s payment instrument is of this type. |
| PI Type Payer | Indicates that this fee is applicable only to transactions where the payer’s payment instrument is of this type. |
| Fee Type | Indicates the fee type that is to be applied to the transaction. |
| Payee Fee | Indicates whether the fee must be paid by the payee or payer. |
| Sub Txn Type | Indicates that the fee is applied only to the specified subtransaction type. |
| Copy from Auth | Indicates whether the fees should be copied from the authorization subtransaction. |
| Include in Limit | Indicates whether the fee is to be used when checking the customer’s limits. |