Skip to main content
PATCH
Update a credit account reminder data

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Path Parameters

id
string<biginteger>
required

The account id for given account

Query Parameters

auditUser
string
required

The audit user to log the request

Body

application/json

The fields that you want to apply to your newly cr, these values will override the predefined template values

Reminder details for update

disableReminderProcess
boolean
reminder1TriggerDate
string<date>

Date when reminder 1 is triggered

Example:

"2019-11-27"

reminder2TriggerDate
string<date>

Date when reminder 2 is triggered

Example:

"2019-11-27"

reminder3TriggerDate
string<date>

Date when reminder 3 is triggered

Example:

"2019-11-27"

reminder4TriggerDate
string<date>

Date when reminder 4 is triggered

Example:

"2019-11-27"

reminder5TriggerDate
string<date>

Date when reminder 5 is triggered

Example:

"2019-11-27"

reminder6TriggerDate
string<date>

Date when reminder 6 is triggered

Example:

"2019-11-27"

reminder7TriggerDate
string<date>

Date when reminder 7 is triggered

Example:

"2019-11-27"

collectionTriggerDate
string<date>

Date when statement is sent to collection

Example:

"2019-11-27"

Response

Successful update of the account

description
string

When a payment is declined, a response description is returned, if available, providing more context on why the transaction failed. This includes a return code and a brief explanation. If multiple issues cause the decline, only one response description is sent; the most recent reason for decline is returned. If the payment is successful, the resourceResponse attribute is returned with null value.

Example:

"061-Usage Limit '24H_RETAIL' Amount Exceeded"

id
string

Will contain the ID of the resource that has been created or updated