Details
Improvement
Minor
Description
Some gateways do not differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. Similarly, the POST parameters may be necessary as well.
See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256
It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page.
Issue Links
- Discovered while testing
-
CORE-1816
Non-merchant gateway callback redirect not setting company ID in client redirect
-
- Closed
-
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Some gateways do not allow differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 |
Some gateways do not allow differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page. |
Tyson Phillips (Inactive)
made changes -
| Description |
Some gateways do not allow differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page. |
Some gateways do not allow differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. Similarly, the POST parameters may be necessary as well. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page. |
Tyson Phillips (Inactive)
made changes -
| Sprint | 3.6.0 Sprint 3 [ 17 ] |
Tyson Phillips (Inactive)
made changes -
| Description |
Some gateways do not allow differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. Similarly, the POST parameters may be necessary as well. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page. |
Some gateways do not differentiate between a callback URL and a notification URL, in which case the callback URL should be used for both the notification and redirecting the client back to Blesta.
After the client is redirected to the callback URL, they are redirected again to the client/pay/received page. However, the original GET parameters included in the callback are not included in the subsequent redirect to client/pay/received. It may be necessary to include those GET parameters, such as the client ID, as it may be useful in GatewayPayments::processReceived and gateway method calls. Similarly, the POST parameters may be necessary as well. See http://www.blesta.com/forums/index.php?/topic/4339-payment-gateway-redirect-problem/?p=37256 It may be best to have the callback redirect a customer to the given return_url instead of assuming that is always the client/pay/received page. |
Tyson Phillips (Inactive)
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 3.6.0 [ 10600 ] | |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Need to test