...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
UC-P-USCT-001: Payment - Unconditional Social Cash Transfer (bank payments)
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
UC-P-USCT-001:PI/projects/1 | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
ID | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
UC-P-USCT-001 |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Name | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment - Unconditional Social Cash Transfer |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Description | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The use case implements single scheduled electronic payment to beneficiaries of the programme, irrespective of whether it’s a one time or recurring payment| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Verify payee account information prior to payment transaction |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Trigger
(the event that triggers the use case) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Due date of payment has been reached |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Preconditions
(list of conditions that MUST be met in order for the use case to be successful) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The payment building block enables different payment types. | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The beneficiary has registered with the SRIS (Social Registry) system| Anchor |
|---|
| _yeo5ibfqb9dz |
|---|
| _yeo5ibfqb9dz |
|---|
|
The potential beneficiary’s needs have been assessed and required details captured| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The beneficiary has been verified and enrolled into a programme| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The beneficiary’s account details are known or knowable to the payment block. (this often includes a verification process within the payment building block) .| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The repeating payment cycle has been scheduled| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Note that some preconditions come from the other user journeys and use cases, see steps 2-5 of https://solutions.dial.community/use_cases/unconditional_social_cash_transf/use_case_steps/payment |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Data inputs | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Reference ID the the social registry programme (from the previous step in the user journey)| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment due date| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
List of eligible beneficiaries| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment amount for each eligible beneficiary| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment account details for each eligible beneficiary |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Actors
(a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Clock/timer from scheduling building block| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
SRIS (social registry information system) screen flow| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment building block| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Workflow building block (for handling the overall process, computing payment amounts and scheduling payments) |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Normal Course (what happens if the event is triggered and the preconditions have been met) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Workflow building block receives a trigger from the scheduling building block that the due date has been reached| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Extract the beneficiary’s bank account details from the SRIS (Social Registry)| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
A workflow building block computes the payment amounts for the beneficiary| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
A workflow building block generates a transaction ID for the beneficiary| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Request a payment for the beneficiary with the payment building block |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Alternative Course
(links to other use cases in case there are different ways how to solve the same use case) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Add links to related use cases here, e.g. UC-P-USCT-002: Payment - Unconditional Social Cash Transfer (non-electronic/SMS payments) | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
UC-P-USCT-003: Payment - Unconditional Social Cash Transfer (direct payment based on family relationship) | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
If the user’s payments have failed, they can utilize the Registration - Unconditional Social Cash Transfer, see Logical process blueprint |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Data output | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
The list of beneficiaries| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
IDs, alphanumeric code e.g. EE123456| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
PNO-EE37702272723| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Names, e.g. Raul Carlson| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Account numbers, alphanumeric| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Amounts tied to the beneficiaries, decimal number e.g. 333.33| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Process/session ID (reference to the audit trail record, e.g. 1231289371)| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Transaction ID for each successful payment transaction, alphanumeric code, e.g. PAID123456290 |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Post-Conditions (the success criteria) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment response (as code) for each payment transaction| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Transaction ID for each successful payment transaction| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Each eligible beneficiary has been paid according to scheduled date| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Audit trail of the process has been recorded |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Exceptions
(error situations) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
A payment has failed (e.g. due to missing/incorrect beneficiary bank account details and/or violating bank rules)| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
A payment has failed due to insufficient funds for withdrawal |
| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Related BBs
(working groups related to that particular use case) | | Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Payment BB - payment processing| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Workflow BB - workflow management| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Registries BB - data source for the use case| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Information Mediator BB - providing interfaces| Anchor |
|---|
| _9l9ar3fqqo6u |
|---|
| _9l9ar3fqqo6u |
|---|
|
Security BB - supervision| Anchor |
|---|
| _l2mhq38t7gnk |
|---|
| _l2mhq38t7gnk |
|---|
|
Identity BB - no relation |
| Anchor |
|---|
| _xoybluhd8wkw |
|---|
| _xoybluhd8wkw |
|---|
|
Payment - Unconditional Social Cash Transfer (bank payments)From https://github.com/GovStackWorkingGroup/BuildingBlockA
| Anchor |
|---|
| _mqpuqufvl5gd |
|---|
| _mqpuqufvl5gd |
|---|
|
Cross building block interaction diagram...
Diagram source here.
| Anchor |
|---|
| _kqzx9d3rm4y4 |
|---|
| _kqzx9d3rm4y4 |
|---|
|
Original DIAL user journeyUse Case | User | Agent | Interaction | Processes |
Unconditional Social Cash Transfer | Target group | Social welfare staff | If a social cash transfer programme has enabled electronic payment processes (e.g. via banks, mobile money, etc.), payments are subsequently paid cyclically according to the programme schedule e.g. often bi-monthly. In the context where a digital financial service system is not employed, each beneficiary would be requested to travel to the nearest designated pay-point* and collect money by programme-specific authentication. In either case, the money is transferred to the selected payment provider or treasury as per generated payroll and is subsequently verified against the individual’s identification of program enrolment. | 1. processing beneficiary payment directly to their account, or for generating payroll to deposit payment amounts for withdrawal by beneficiary from designated banking institution(s) / pay-point(s) 2. identifying and authenticating individual that is making a withdrawal, or to recall / verify deposit account information prior to payment transaction |
The original DIAL user journey comes from here: https://solutions.dial.community/use_cases/unconditional_social_cash_transf/use_case_steps/payment