Create statement minimum amount due (MAD) for the current cycle, or update it if it already exists. Using this endpoint bypasses the configured strategy for calculating the MAD. For more information, refer to Minimum amount due calculation.

Notes:

• Running this endpoint bypasses the configured strategy only for the current cycle. The configured strategy, if it exists, still applies to future statements.
• The following example demonstrates how the Pismo platform handles the request when you run this endpoint.
  Suppose the due date for Cycle A is March 10. The next cycle after Cycle A is Cycle B.
  
  • If the Pismo platform receives the "Create or update statement minimum amount due request" on March 9, it updates the MAD for Cycle A.
    
  • If it receives the request on March 10, and the platform has not finished closing Cycle A, the endpoint returns an error.
    Note: This happens even if the platform hasn't started the process of closing Cycle A. The platform doesn't update the MAD for Cycle A on it's cycle closing date.
    
  • If it receives the request on March 10, and the platform has finished closing Cycle A, it updates the MAD for Cycle B.
    
  • If it receives the request on March 11, it updates the MAD for the next cycle (Cycle B).
    
• To use this endpoint, the Allow overriding the minimum amount due for the current statement program parameter must be set to true. Otherwise, the endpoint generates an error.