-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add comment to README about the Middleware as a replacement for the e…
…ID parameter in your payment extensions
- Loading branch information
Showing
1 changed file
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,20 @@ | ||
The extension transactor has the purpose to enable online payments connecting to various gateways. | ||
|
||
You must configure it in the Extension Configuration of the Settings backend module. | ||
Set the compatibility mode (basic.compatibility) to 0 for the new API. | ||
Older extension versions might need the old API and a 1 here. | ||
|
||
|
||
Since version 0.9.0 the transactor extension contains a middleware, which payment extensions can use for a gateway instant message after the payment. | ||
|
||
Use the transactor parameter as | ||
transactor=mygateway | ||
in the backend url to your payment extension page. | ||
|
||
Your extension`s ext_localconf.php file must configure the middleware in TYPO3 10+: | ||
|
||
$GLOBALS['TYPO3_CONF_VARS']['FE']['transactor_include']['mygateway'] = \Foo\Bar\Controller\ServerResponseController::class . '::processRequest'; | ||
|
||
Then your class ServerResponseController can receive the calls from the instant messages from your gateway. | ||
|
||
|