One form step/block would be to initiate payment, after which the end-user is redirected to the payment platform and then returns to the form (usual flow, check Ingenico docs if anything is different).
One detail is that in a single Open Forms instance, multiple target bank accounts must be configurable. Different forms can have their payment go to a different account.
Acceptance criteria
[ ] Ingenico documentation checked: do they support multiple accounts on their end, or do we need to implement this explicitly?
[ ] Payment flow implemented on the backend, using API endpoints (headless requirement + the Javascript SDK will initiate this)
[ ] Frontend implementation of the payment phase
[ ] Able to configure which target bank account applies for a form
joeribekker
commented
3 years ago
Ingenico is a payment provider to be implemented.
One form step/block would be to initiate payment, after which the end-user is redirected to the payment platform and then returns to the form (usual flow, check Ingenico docs if anything is different).
One detail is that in a single Open Forms instance, multiple target bank accounts must be configurable. Different forms can have their payment go to a different account.
Acceptance criteria