Ogone setup¶
Presentation¶
Ogone is a CreditCard payment provider. Here’s how to configure it in order to use it in your application.
Configuration¶
Here’s how to configure Ogone for Sonata e-commerce:
- Go to the Ogone configuration portal:
Technical Settings
->Global Security Parameters
; setHash Algorithm
toSHA-1
Technical Settings
->Data and origin verification
; add your various domain(s) URL(s) separated by ‘;’ (no spaces)Technical Settings
->Data and origin verification
; fill in your SHA-IN pass phrase (keep it, you’ll need it for your app config)Technical Settings
->Transaction feedback
HTTP redirection in the browser
: leave all fields blankDirect HTTP server-to-server request
:Timing of the request
:always deferred
- URL of the merchant’s post-payment page
- If the payment’s status is “accepted”, “on hold” or “uncertain” ->
{your_host}/payment/callback
- If the payment’s status is “cancelled by the client” or “too many rejections by the acquirer”. ->
{your_host}/payment/error
- If the payment’s status is “accepted”, “on hold” or “uncertain” ->
SHA-OUT pass phrase
; fill in with the same key as the one you’ve given for the SHA-IN
Configure the payment gateway according to the values you’ll get with your Ogone account (or you’ll fill in the Ogone admin)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | sonata_payment:
services:
# ...
ogone:
name: ogone
enabled: true
code: ogone
transformers:
basket: sonata.payment.transformer.basket
order: sonata.payment.transformer.order
options:
url_callback: sonata_payment_callback
url_return_ko: sonata_payment_error
url_return_ok: sonata_payment_confirmation
form_url: "%ogone.form_url%"
pspid: "%ogone.pspid%"
home_url: "%ogone.home_url%"
catalog_url: "%ogone.catalog_url%"
sha_key: "%ogone.sha_key%"
sha-out_key: "%ogone.sha-out_key%"
# ...
parameters:
# ...
# If you've overridden the OgonePayment class
sonata.payment.method.ogone.class: "App\\Sonata\\Component\\Payment\\Ogone\\OgonePayment"
# ...
|