Not getting payment response in onTransactionResponse(Bundle bundle) method when paytm app is not installed

[tyagi-priyam]

Payment flow is working fine when paytm app is already installed in the device but in case paytm app is not installed, sdk is launching a webview and after payment completion the callback url is getting loaded in the same webview and i am not receiving payment response in the callback method of PaytmPaymentTransactionCallback() interface. And the webview stays there only unless i press back button.
`PaytmOrder paytmOrder = new PaytmOrder(order_id, BuildConfig.PAYTM_KEY, token, amount, BuildConfig.PAYTM_CALLBACK_URL.replace("[[order_id]]",order_id));

TransactionManager manager = new TransactionManager(paytmOrder, new PaytmPaymentTransactionCallback() {
@OverRide
public void onTransactionResponse(Bundle bundle) {
Log.d("ecedcc: ", "onTransactionResponse called");
if (bundle != null) {
for (String key : bundle.keySet()) {
Log.e("ecedcc: ", key + " : " + (bundle.get(key) != null ? bundle.get(key) : "NULL"));
}
} else {
Log.d("ecedcc: ", "paytm result bundle null");
showPaymentFailed(Constants.DEFAULT_WALLET);
}
}

            @Override
            public void networkNotAvailable() {
                Log.d("ecedcc: ", "networkNotAvailable called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onErrorProceed(String s) {
                Log.d("ecedcc: ", "onErrorProceed called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void clientAuthenticationFailed(String s) {
                Log.d("ecedcc: ", "clientAuthenticationFailed called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void someUIErrorOccurred(String s) {
                Log.d("ecedcc: ", "someUIErrorOccurred called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onErrorLoadingWebPage(int i, String s, String s1) {
                Log.d("ecedcc: ", "onErrorLoadingWebPage called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onBackPressedCancelTransaction() {
                Log.d("ecedcc: ", "onBackPressedCancelTransaction called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onTransactionCancel(String s, Bundle bundle) {
                Log.d("ecedcc: ", "onTransactionCancel called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }
        });
        manager.setShowPaymentUrl("https://securegw.paytm.in/theia/api/v1/showPaymentPage");
        manager.startTransaction(GatewayActivity.this, PAYTM_REQUEST_CODE);

`

callback url = https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=[[order_id]]

[tyagi-priyam]

The callback url which is getting loaded in the webview after payment process is
https://payments.circle.page/verify

This callback is being used to generate txnToken in the backend

[Wangab]

I have the same problem, how can I solve this problem

[puneet8-sharma]

Hi Guys
The problem you have been facing is wrong callback url.
Whenever you generate txnToken, you are expected to pass a callback url field which will be configured against that transaction and that callback url should be Paytm Static callback url (https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=order_id), any other url will prevent webview from getting closed.
Please make changes accordingly and let us know if issue still persists.

[harshabhadra]

Hi Guys
The problem you have been facing is wrong callback url.
Whenever you generate txnToken, you are expected to pass a callback url field which will be configured against that transaction and that callback url should be Paytm Static callback url (https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=order_id), any other url will prevent webview from getting closed.
Please make changes accordingly and let us know if issue still persists.

I'm using the same callback url you mentioned still I'm facing the same issue. If PayTm app is not is in user's phone then webview is opening after payment.

[puneet8-sharma]

Hi Guys
The problem you have been facing is wrong callback url.
Whenever you generate txnToken, you are expected to pass a callback url field which will be configured against that transaction and that callback url should be Paytm Static callback url (https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=order_id), any other url will prevent webview from getting closed.
Please make changes accordingly and let us know if issue still persists.

I'm using the same callback url you mentioned still I'm facing the same issue. If PayTm app is not is in user's phone then webview is opening after payment.

For clarification, this is the callback url configured against your mid on merchant dashboard and this is the same callback url you are passing to generate 'txnToken' from backend.

[harshabhadra]

Hi Guys
The problem you have been facing is wrong callback url.
Whenever you generate txnToken, you are expected to pass a callback url field which will be configured against that transaction and that callback url should be Paytm Static callback url (https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=order_id), any other url will prevent webview from getting closed.
Please make changes accordingly and let us know if issue still persists.

I'm using the same callback url you mentioned still I'm facing the same issue. If PayTm app is not is in user's phone then webview is opening after payment.

For clarification, this is the callback url configured against your mid on merchant dashboard and this is the same callback url you are passing to generate 'txnToken' from backend.

Thank you it solved my issue and it's working fine now.
The problem is in Initiate transaction api documentation callbackurl parameter is optional but in sdk integration documentation(Android) callbackurl is mandatory that's why we are facing this issue.

[puneet8-sharma]

Happy to help.

[puneet8-sharma]

@harshabhadra please mark the issue closed.

[harshabhadra]

@harshabhadra please mark the issue closed.

I didn't open this issue

[shivamdev-lgtm]

@puneet8-sharma In that case how am I going to get a callback to my backend about the status of the payment?

[puneet8-sharma]

@puneet8-sharma In that case how am I going to get a callback to my backend about the status of the payment?

You can use order status API to get the status of specific order or you can use the response provided in onTransactionResponse

[shivamdev-lgtm]

@puneet8-sharma In that case how am I going to get a callback to my backend about the status of the payment?

You can use order status API to get the status of specific order or you can use the response provided in onTransactionResponse

When should I call the order status API? I mean should I schedule it to call after a fixed interval of time after I create a transaction token on my backend or am I missing something here?

About using onTransactionResponse, I don't think we should depend on the client to do this, should we? Stripe have a concept of webhooks which paytm also seems to have but we have to contact the support to set it up? That seems too weird, shouldn't we just have an option on the dashboard?

[puneet8-sharma]

@puneet8-sharma In that case how am I going to get a callback to my backend about the status of the payment?

You can use order status API to get the status of specific order or you can use the response provided in onTransactionResponse

When should I call the order status API? I mean should I schedule it to call after a fixed interval of time after I create a transaction token on my backend or am I missing something here?

About using onTransactionResponse, I don't think we should depend on the client to do this, should we? Stripe have a concept of webhooks which paytm also seems to have but we have to contact the support to set it up? That seems too weird, shouldn't we just have an option on the dashboard?

Well you can hit that API once you receive callback in onTransactionResponse and also you can poll this API if possible on certain repetitive interval.

[gharShaddi]

I'm also facing the same issue still webview is opening after a transaction is complete or failed or canceled now I don't understand what to do if I set callback URL as mentioned above then when to execute callback from application to my server and one more thing where do can add additional payload like notes or id of post ?

[rohitthakre]

Hi Guys
The problem you have been facing is wrong callback url.
Whenever you generate txnToken, you are expected to pass a callback url field which will be configured against that transaction and that callback url should be Paytm Static callback url (https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=order_id), any other url will prevent webview from getting closed.
Please make changes accordingly and let us know if issue still persists.

I'm using the same callback url you mentioned still I'm facing the same issue. If PayTm app is not is in user's phone then webview is opening after payment.

Payment flow is working fine when paytm app is already installed in the device but in case paytm app is not installed, sdk is launching a webview and after payment completion the callback url is getting loaded in the same webview and i am not receiving payment response in the callback method of PaytmPaymentTransactionCallback() interface. And the webview stays there only unless i press back button.
`PaytmOrder paytmOrder = new PaytmOrder(order_id, BuildConfig.PAYTM_KEY, token, amount, BuildConfig.PAYTM_CALLBACK_URL.replace("[[order_id]]",order_id));

TransactionManager manager = new TransactionManager(paytmOrder, new PaytmPaymentTransactionCallback() {
@OverRide
public void onTransactionResponse(Bundle bundle) {
Log.d("ecedcc: ", "onTransactionResponse called");
if (bundle != null) {
for (String key : bundle.keySet()) {
Log.e("ecedcc: ", key + " : " + (bundle.get(key) != null ? bundle.get(key) : "NULL"));
}
} else {
Log.d("ecedcc: ", "paytm result bundle null");
showPaymentFailed(Constants.DEFAULT_WALLET);
}
}

            @Override
            public void networkNotAvailable() {
                Log.d("ecedcc: ", "networkNotAvailable called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onErrorProceed(String s) {
                Log.d("ecedcc: ", "onErrorProceed called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void clientAuthenticationFailed(String s) {
                Log.d("ecedcc: ", "clientAuthenticationFailed called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void someUIErrorOccurred(String s) {
                Log.d("ecedcc: ", "someUIErrorOccurred called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onErrorLoadingWebPage(int i, String s, String s1) {
                Log.d("ecedcc: ", "onErrorLoadingWebPage called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onBackPressedCancelTransaction() {
                Log.d("ecedcc: ", "onBackPressedCancelTransaction called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }

            @Override
            public void onTransactionCancel(String s, Bundle bundle) {
                Log.d("ecedcc: ", "onTransactionCancel called");
                showPaymentFailed(Constants.DEFAULT_WALLET);
            }
        });
        manager.setShowPaymentUrl("https://securegw.paytm.in/theia/api/v1/showPaymentPage");
        manager.startTransaction(GatewayActivity.this, PAYTM_REQUEST_CODE);

`

callback url = https://securegw.paytm.in/theia/paytmCallback?ORDER_ID=[[order_id]]

hello there anyone find that solution in paytm web view