Delinquency buckets

In credit terms, an overdue amount refers to the unpaid (after real due date) amount a customer owes after paying less than the minimum amount due (MAD) on their last closed statement. In addition, if the customer keeps doing this - paying less than MAD over and over - their overdue amount continues to increase due to interest accruals and probably fines/fees.

Credit card issuers are often only concerned with the total overdue amount for in the current cycle. In India, however, there is the concept and requirement for delinquency buckets, which indicate how much of the overdue amount applies to each cycle with a less than MAD paid amount after each corresponding real due date.

📘

Current limitation

Only credits that have transaction type ID=7253 can clear delinquency buckets. Not all issuers are currently using this transaction type. See your Pismo representative if you need to set this up.

Take a customer whose statement closes on the 10th day of each month and has the 15th as the due date. (To keep it simple, assume this is the real due date.) Also, suppose after a couple of cycles, the following scenario occurs:

📘

Date format

In the tables below, the date format is MM/DD/YY (month/day/year)

Transactions for Cycle 3 - February 11th:

Statement: (Key: C = Cycle, OA=Overdue amount, DA=Delinquent amount)

Transactions for Cycle 4 - March 11

Statement (Key: C = Cycle, OA=Overdue amount, DA=Delinquent amount)

The first due date took place at cycle 2 and the customer fully paid the corresponding amount, so the overdue amount and delinquency bucket for cycle 2 is zero.

At cycle 3, the due date for closed cycle 2 statement took place and the MAD was $35.00. The customer paid exactly that amount, so even though they started to revolve, the overdue amount and delinquency bucket for cycle 3 is equal to zero.

At cycle 4 however, customer finances seem to run out of control. The cycle 3 due date has come and its MAD amount is $49.61. This time, the customer does not pay anything. Now, the customer has an overdue amount of $49.61 and the first greater than zero delinquency bucket - also $49.61.

In cycle 5, the cycle 4 closed statement due date occurs, and the corresponding MAD is $104.57. Once more, the customer does not pay any amount, so their updated overdue amount is $104.57. Part of it is the $49.61 (delinquency bucket for cycle 4). Another part of it is exactly the difference between the total overdue amount and the previous delinquency bucket, that is, the delinquency bucket for cycle 5 is $54.96.

Transactions for Cycle 5 - April 11

Statement (Key: C = Cycle, OA=Overdue amount, DA=Delinquent amount)

Notice that the total overdue amount is equal to $104.57, composed of two delinquency buckets - $49.61 (cycle 4) and $54.96 (cycle 5).

As with cycles 4 and 5, the customer made no payment for cycle 6 which led them to an updated overdue amount of $168.20, out of which, $63.63 corresponds to the cycle 6 delinquency bucket and the remaining amount as previously summarized.

So this is the current state:

Transactions for Cycle 6 - May 11

Statement (Key: C = Cycle, OA=Overdue amount, DA=Delinquent amount)

At cycle 7 something new happens, the customer pays an amount that matches precisely the first greater than zero delinquency bucket (cycle 4, $49.61). As a result, that delinquency bucket is fully cleared and the current one is calculated as follows: overdue amount (-) sum of previous non cleared delinquency buckets’ amounts. Customer payments must clear delinquency buckets from oldest to newest.

Transactions for Cycle 7 - June 11

Statement (Key: C = Cycle, OA=Overdue amount, DA=Delinquent amount)

In conclusion, delinquency buckets are only for issuer’s follow up on the existing overdue amounts and are meant to be completely transparent to customers - unless platform client wants to or is obligated by regulations to do so.

Delinquency bucket API endpoints

• Get delinquency bucket
• List delinquency buckets

Delinquency bucket events

Delinquency buckets are automatically created and updated, there are no endpoints for doing that.

• statements_delinquency_bucket_created-1
• statements_delinquency_bucket_updated-1