¶ In this lesson you will
- Choose free or paid
- Set a fixed price and the payment expiration time
- Fill the payment account, payment code and merchant
¶ Two questions: how much, and to whom
Pricing answers how much the applicant pays (free, a fixed price, or a dynamic price) and where the money goes (payment account identifier, service payment code and merchant, from the SRD or the finance team). The demo charges a fixed 1,000 RWF.
4. Pricing: nothing chosen yet
Paid service: type, expiration and price mode
- Paid (Free skips payment entirely)
- Wizard or Code Editor
- Payment Expiration Time in hours (demo: 72). The bill expires after that
- Fixed price
- Dynamic price (Section B)
- Price Logic (Section B)
Paid service: where the money goes
- Payment Account Identifier: Fixed or Dynamic
- The account, e.g.
GOR-CG-RWF - Service Payment Code Identifier from finance
- Payment Merchant (always fixed)
- Continue
The same pricing in the Code Editor
Pricing rules to remember
| Setting | Rule |
|---|---|
| Payment Expiration Time | Hours, minimum 1. After it, the system fires EXPIRE_PAYMENT; your workflow must handle it |
| Fixed price | One amount for everyone |
| Payment account | Fixed (one account) or Dynamic (chosen from an answer, e.g. the district). Lesson B6 |
| Payment merchant | Always one fixed merchant per service |
Gotcha · a free application skips PAYMENT_PENDING
When the computed price is 0, the
APPLYevent goes to endStateTwo (in the demo, straight toPENDING_ASSIGN_OFFICE) instead of generating a bill. If your workflow has no endStateTwo on APPLY, free applications have nowhere to go.
Tip · reference
Pricing overview in the wiki.
¶ Check yourself
The SRD says "applicants have 3 days to pay". What do you enter in Payment Expiration Time?
- A. 3
- B. 4320
- C. 72
- D. 0.5
Show the answer
C. The unit is hours: 3 days = 72 hours. The minimum is 1 hour.
← A6b · Form logic: show, hide, require and validate · A8 · Workflow fundamentals →