UK Direct Debit
This functionality handles the direct debit payment operations for UK area.
Below are the journeys, entities, libraries and scripts related to this functionality:
Digital Journeys
On Demand Scripts
Business Workflow Configuration Actions
FTOS_PYMT_DirectDebitMandate is the master business workflow that handles the different types of changes affecting a direct debit mandate during its lifetime. For more details about the mandate behavior, its states and the business workflow diagram consult the Direct Debit page.
Transition | Description |
---|---|
_Proposal | Initial state. |
Active_Cancelled | When the system registers a notification about the mandate cancellation. The transition to this status is made according to the 0, 1, 2, 3, B, C Reason Codes. These values, received in the ADDACS file, are specific for mandates deletion. |
Active_Expired | When the mandate reaches its end day. The expiration triggers the automatic change of the payment type on the policy, from Direct Debit to Bank Transfer (OP). |
Active_VersionClosed | When a version of the mandate is closed. Used for mandate versioning. |
Approved_Active | When the mandate reaches its start day. |
Approved_Draft | When a change of the policy payment type from Bank Transfer (OP) into Direct Debit is performed on a policy. |
Approved_Expired | When the number of days for the activation of a mandate were exhausted. |
Cancelled_Active | The transition to this status is made according to the R reason code, received in the ADDACS file. The R value is specific for mandates reactivation. |
Draft_Active | When the mandate reaches its start day. This transition is triggered by the DIDEUK_Instructions job, which verifies if the current date is the mandate begin date and changes the status to Active for all eligible mandates. |
Draft_Cancelled | When the system registers a notification about the mandate cancellation. The transition to this status is made according to the 0, 1, 2, 3, B, C Reason Codes. These values, received in the ADDACS file, are specific for mandates deletion. |
Draft_Expired | When the number of days for the activation of a mandate were exhausted. The expiration triggers the automatic change of the payment type on the policy, from Direct Debit to Bank Transfer (OP). |
Draft_Pending | After the instruction file for the mandate's activation is generated, and the mandate is pending approval from the bank. |
Draft_VersionDraft | When the mandate versioning process starts. |
Pending_Active | When the mandate reaches its start day. |
Pending_Cancelled | When the system registers a notification (e.g. AUDDIS file) about canceling the mandate, or a user manually cancels the mandate. |
Proposal_Active | When the mandate reaches its start day. |
Proposal_Draft | When the mandate is registered in the system but it is not activated yet, or its begin date is yet to come. |
Proposal_Expired | When the number of days for the activation of a draft mandate were exhausted. |
VersionDraft_Approved | When a version of the mandate is approved. Used for mandate versioning. |
VersionDraft_VersionUnapproved | When the opened version is not approved. Used for mandate versioning. |
Endpoints
Processors
The FTOS_PYMT_DIDEProcessor is used for setting the following parameters:
Below is an example of processor settings:
Server Side Script Libraries
Scheduled Jobs