A scenario allows to create steps defining the actions to be carried out in interaction with a "PaymentRequest".
Scenario creation
A scenario is a blank container in which steps must be inserted.
Step creation
Steps of a scenario allows to trigger a notification action on the basis of an event occurring in interaction with a "PaymentRequest".
REQUIRED FIELDS
| Reference date |
- Creation date
- Payment Deadline
- Expiration link date
|
| Delay |
|
| Type of delay |
|
OPTIONAL FIELDS
| Request status |
- Active = allows payments
- Canceled = Request has been canceled - doesn't allows payment
- Closed = Payments can't be performed
|
| Payment status |
- Pending = Payment is expected
- Partial = A Partial payment has been completed and registred
- Paid = Payment has been completed
- UNPAID: unpaid, payment not completed
|
| Breakdown status |
- Pending = Payment is expected
- Partiel = A partial payment has been completed and registered
- Paid = a Breakdown Payment has been completed
|
| Notification |
- SMS : association of an existing template
- E-mail : association of an existing template
- E-mail list: association of an recipient from an existing list
- Webhook : Activate a Webhook notification
|
