Problem/Motivation

Many payment methods will have to provide a form that POSTs values to a remote server.

Proposed resolution

Provide a helper service to make this easier. It should register routes and build forms automatically. Put the helper in a separate submodule, or even a separate project, so we don't pollute the generic Payment API with popular, but non-generic functionality.

Remaining tasks

Build the helper module.

User interface changes

None.

API changes

None/

CommentFileSizeAuthor
#3 payment_2372041_3.patch20.67 KBxano

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Active » Postponed
Related issues: +#2339397: Better support for remote payment methods / redirects

This is blocked by #2339397: Better support for remote payment methods / redirects.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

We could also put all helper code (of which there really isn't any yet) in a separate namespace instead, such as \Drupal\payment\Helpers.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
StatusFileSize
new payment_2372041_3.patch20.67 KB

This patch builds on the one from #2339397-71: Better support for remote payment methods / redirects.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Postponed » Needs review

#2339397: Better support for remote payment methods / redirects has now been fixed.

Status: Needs review » Needs work

The last submitted patch, 3: payment_2372041_3.patch, failed testing.

Anonymous’s picture

Anonymous (not verified) commented

Where is this at now? This is needed for example for Worldpay hosted payment pages, where we would need to post to Worldpay.

Would the patch still apply after #2339397 has been fixed?