Skip to content

Account Limits and Transaction Controls

Chinese source: 账户限额与交易控制
Locale: en-US
Audience: Internal learning

Key Terms

ChineseEnglishUsage Note
限额LimitCan be amount, count, channel, or transaction scope.
当前值Current LimitLimit value currently in effect.
申请值Requested LimitNew value requested by user or customer.
限额范围Limit ScopeTransaction, channel, period, or product scope.

Concept

A limit is a pre-transaction control on future transaction capability. It is not an accounting transaction, but it affects whether later transactions pass, how much can pass, and whether extra authorization or workflow is needed.

text
System allowed range >= current effective limit >= actual transaction amount.

If the transaction amount exceeds the current limit, the system may reject the transaction, show an over-limit message, or trigger higher authorization depending on transaction type, channel rules, product parameters, and risk policy.

Common Limit Dimensions

DimensionDescriptionTypical Question
Customer levelControls the customer across accounts or businesses.How much can this customer transact overall?
Account levelControls a specific account.How much can this account transact?
CurrencyControls different currencies separately.Is this limit for RMB or foreign currency?
ScopeSingle transaction, daily cumulative, monthly cumulative, channel, or transaction type.What does this limit apply to?
Current valueActual effective limit.What is currently allowed?
Requested valueNew value being requested.What is being changed to?

Lower Bound, Upper Bound, Current Value, Requested Value

ConceptMeaning
Lower boundMinimum value allowed by system or product rules.
Upper boundMaximum value allowed by product, channel, risk, or regulatory rules.
Current limitCurrently effective limit value.
Requested limitNew limit value requested in this maintenance action.

Risk Controls

  • Raising limits increases exposure to fraud, mistaken transfers, and loss.
  • Lowering limits may block normal customer activity.
  • Customer-level and account-level limits must not be mixed.
  • Currency, scope, current value, and requested value must be read together.
  • Limit maintenance should preserve operator, authorizer, before/after values, timestamp, and business basis.