Problem/Motivation

kessai_worldline has no README. A site builder wiring up the Worldline gateway has no documentation for the two things that are not obvious from the UI: that a hosted-checkout payment settles through both the browser return and a server-to-server webhook (so a payer who never returns is still settled), and how to actually turn the webhook on (register the endpoint, set the key id and secret).

Proposed resolution

Add a kessai_worldline/README.md covering the requirements, the settings-form fields, keeping secrets in settings.php, the two settlement channels and their idempotency, the abandoned-browser guarantee (and how it resumes an orchestra workflow step server-side), and a short checklist for enabling the webhook. Also add Worldline, HMAC and finalizer to the project cspell dictionary.

Remaining tasks

  • Review.

Issue fork kessai-3609156

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mably created an issue. See original summary.

mably’s picture

mably commented
Status: Active » Needs review

Pushed to the issue fork branch 3609156-add-a-kessaiworldline: a new kessai_worldline/README.md covering the two settlement channels (browser return and HMAC-verified webhook), the abandoned-browser guarantee and how it resumes an orchestra workflow step server-side, keeping secrets in settings.php, and a checklist for turning the webhook on. Added Worldline, HMAC and finalizer to the project cspell dictionary. cspell clean.

mably opened merge request !1

  • mably committed f7879124 on 1.x 
    task: #3609156 Add a kessai_worldline README documenting webhook...
mably’s picture

mably commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.