Limits - Overview¶

This functionality enables the financial institution to establish limits for their customers within the Zelle network. Presently, PayCenter exclusively supports the Zelle network; however, future iterations will encompass additional networks.

Limit Scopes¶

There are seven scopes in the limit system and a particular scope has a priority value.

Scope Name	Scope Priority
PayCenterMemberFIId	0
Network	1
RoutingNumber	2
NetworkProduct	3
CustomerId	4
BankAccount	5
PaymentId	6

PayCenterMemberFIId¶

This represent the financial institution member id which has been registered in PayCenter.

Network¶

The network is the scope to define payment happens through. Most of the times it would be 1 (one) and it represents the Zelle network.

NetworkProduct¶

This scope indicates the product for which the limit is established. Currently allowed values are 1020 (inbound) and 1010 (outbound).

CustomerId¶

When establishing the 'CustomerId' scope value, it applies specifically to the designated customer. To apply this setting universally across all customers, the wildcard character (*) must be passed."

BankAccount¶

Upon defining the 'BankAccount' scope value, it is allocated to the individual bank account. To implement this allocation universally across all bank accounts, the wildcard character (*) is required."

RoutingNumber¶

This scope designates the branch of the financial institution for which the limit is to be established.

PaymentId¶

This will be used to set a limit to a specific payment.

Note

Empty value is not allowed for all the above scope keys.

Note

A limit will be applied to the scopes which are defined for the particular limit.

An example of JSON payload

{
    "Scope": {
        "Network": "1",
        "NetworkProduct": "1010",
        "PayCenterMemberFIId": "1313",
        "RoutingNumber": "076921842",
        "CustomerId": "*"
    }
}

Limit Periods¶

These are the predetermined time intervals within which the transaction amount limit can be configured.

Limit Period Definition	Limit Period Definition Id
Single Transaction	1
Daily Transaction	2
Weekly Transaction	3
Monthly Transaction	4

Single Transaction¶

It could be set up the amount for a single transaction that expects to limit the transaction amount. When setting up the single transaction limit period, the velocity should be 1.

An example of JSON payload
```
{
  "LimitId": 252,
  "LimitPeriodDefinitionId": 1,
  "Amount": 20,
  "Velocity": 1
}
```

Daily Transaction¶

The daily allowable transaction amount can be configured.

An example of JSON payload

{
  "LimitId": 252,
  "LimitPeriodDefinitionId": 2,
  "Amount": 150,
  "Velocity": 5
}

Weekly Transaction¶

The weekly allowable transaction amount can be configured.

An example of JSON payload

{
  "LimitId": 252,
  "LimitPeriodDefinitionId": 3,
  "Amount": 700,
  "Velocity": 25
}

Monthly Transaction¶

The monthly allowable transaction amount can be configured.

An example of JSON payload

{
  "LimitId": 252,
  "LimitPeriodDefinitionId": 4,
  "Amount": 5000,
  "Velocity": 40
}

Graduated Limit Parameters¶

By configuring graduated Limit, the ability is provided to establish a limit that will be incrementally applied.

Graduated Limit Parameter Definition
DaysSinceCustomerIdRegistered
DaysSinceBankAccountRegistered
DaysSinceDeviceRegistered
DaysSinceFroudeActivity
DaysSinceFirstPaymentReceived
RTFOffline

DaysSinceCustomerIdRegistered¶

The limit required to be applied since the customer's registration in Zelle.

DaysSinceBankAccountRegistered¶

The limit required to be applied since the bank account registration.

DaysSinceDeviceRegistered¶

The limit required to be applied since the device registration.

DaysSinceFroudeActivity¶

The limit required to be applied since the fraud activity detection.

DaysSinceFirstPaymentReceived¶

The limit required to be applied since the first payment received.

RTFOffline¶

The limit required to be applied when the RTF offline.

This is the example of JSON paload

{
  "LimitId": 252,
  "PayCenterMemberFIId": 1313,
  "FieldName": "DaysSinceCustomerIdRegistered",
  "StartRange": 0,
  "EndRange": 200,
  "Status": "Enabled"
}

An example of configuring the graduated limit

Suppose there is a need to configure a graduated limit (DaysSinceCustomerIdRegistered), whereby one limit configuration applies within 0-200 days, and another limit applies within 200-500 days. This configuration can be set up accordingly. Notice that there are two limitIds contain below JSON payloads.

{
  "LimitId": 300,
  "PayCenterMemberFIId": 1000,
  "FieldName": "DaysSinceCustomerIdRegistered",
  "StartRange": 0,
  "EndRange": 200,
  "Status": "Enabled"
}

{
  "LimitId": 301,
  "PayCenterMemberFIId": 1000,
  "FieldName": "DaysSinceCustomerIdRegistered",
  "StartRange": 200,
  "EndRange": 500,
  "Status": "Enabled"
}

Note

When configuring the graduated limit, it is imperative to ensure there are no gaps between the graduated limits. For instance, the first graduated limit spans from 0 to 200 days, while the second graduated limit covers the period from 202 to 300 days.