I am putting the values of mandatory parameter in step-2. but it gives error that Something went wrong. The transaction request sent by you is incorrect. Kindly email your MID - XXxVMh74422683748269, Order ID - TEST_1593759129069 and order time - Jul 3, 2020 12:22
Here is the link for subscription-payments in paytm
https://developer.paytm.com/docs/v1/subscription-payments/
Paytm Subscription is enterprise solution and it require to be enable on the paytm backend system on the merchant ID (MID).
Looks like the subscription is not configured for your merchant id( mid) at Paytm side. Please raise the request to developer support. Kindly check after subscription gets configured on your mid in staging environment.
Related
I’m trying to setup a payment method for a subscription on mobile with flutter and .net as backend.
For that here is my flow :
I create a customer and a SetupIntent backend side
I send the details to flutter and it present the payment sheet to customer letting him choose Apple Pay as a payment method
when SetupIntent is completed mobile side I’m listening for it on web-hook backend side and I create the subscription with a trial period and the SetupIntent Id just created.
It works pretty well but I have a problem with apple validation.
When customer choose Apple Pay as a payment method It display « amount pending » instead of the subscription plan price and recurrence. Which is normal since I didn’t create the subscription at this step. But it’s rejected by Apple.
I checked the SetupIntent to see if I can attach a subscription to it to let the pricing appear but it seems not.
I checked the doc and the only sample I see is related to checkout portal but I want to use the element payment sheet to the customer.
As you can see in the Apple guide it should be display like the first screenshot of this page : https://developer.apple.com/design/human-interface-guidelines/apple-pay/overview/subscriptions-and-donations/
Does anyone know how to achieve this ?
I have some rough Idea but want to know timelines regarding End of Life plan for below in Production Environments. So that I can plan my development plan accordingly well.
For new/Existing Customers till when API 2.0 will be valid and after which date we must use API 2.0?
For new/Existing Customers till when basic authentication will be valid and after which date we must JWT base OAUTh2 authentication?
Kindly help me with all this information as I need to plan my integration changes accoridngly.
Beginning Feb 2022, esig rest API will enter maintenance mode. It will still work but will receive few updates after that. Blog post
All rest API clients must update to an oauth V2 flow by September 2022. See the blog post
I have a basic plan of docusign which gives me 5 envelop per month. I am testing my integration key on demo api before going live. It needs 20+ api test calls before upgrading demo integration key to live. But after 5 demo api calls it is giving me following error:
Exception: ENVELOPE_ALLOWANCE_EXCEEDED The envelope allowance for the account has been exceeded.
Can someone please help as I am new to docusign.
Demo accounts should not have such a strict envelope limit. First, I would recommend confirming your calls we're actually hitting your Sandbox. To do so, log in to the demo environment: from https://developers.docusign.com/ click on Go to Sandbox. If you log in through that method, do you see the envelopes you created using your integration?
If so, your Sandbox may have been incorrectly provisioned. Please send an email to go-live#docusign.com with your Production account ID and your Demo account ID.
i have mailed to 20 clients from demo account.All 20 docs sign is completed still i am getting integrator key Review status failed Review Result: Please ensure you have 20 or more consecutive error-free API transactions. Verify that your transactions comply with API rules and limits. What is mean by 20 or more consecutive error-free API transactions.? What exactly have to do for this issue?
You have to make actual Api calls to send envelopes in the Demo environment.
See more information here
To promote an Integrator Key from a developer sandbox to a live production account you need at least 20 API test transactions run in the DocuSign Demo environment. DocuSign analyzes those transactions to ensure they are in compliance with API Rules and Limits before allowing the key to be enabled in production.
I'm getting a 401 error when I try to create a PayPal invoice. I'm using the nodejs REST API:
https://github.com/paypal/rest-api-sdk-nodejs
I did a quick test with the create invoice sample, changing the id and secret in the configure.js to those my app in sandbox. I get the 401 when this happens as well. The app is setup to allow invoice actions (it's in the scope parameter when I request the token), is there something else I need to enable?
I contacted PayPal technical support, they said to contact PayPal MTS. When I contacted them they said to contact technical support... I'm assuming it's something account related as that's the only thing I changed in the sample.
Edit 2014-09-17
I can get a token with curl:
{"scope":"https://uri.paypal.com/services/applications/webhooks https://uri.paypal.com/services/invoicing openid https://api.paypal.com/v1/payments/.* https://api.paypal.com/v1/vault/credit-card/.* https://api.paypal.com/v1/vault/credit-card","access_token":"A015QDaSWWVrhK.FNSZVZd-vDGflSm.g1H.4PnDeXaYDFqo","token_type":"Bearer","app_id":"APP-80W284485P519543T","expires_in":28800}
I'm using the samples from github (configure.js and invoice/create.js specifically) the only thing I changed was the client and secret in configure.
The e-mail in the request was the issue. It worked with the sample because it was the e-mail associated with the app. Changing the config id and secret to mine wasn't enough, the e-mail needed to be changed to mine as well.
Just spent a couple of hours trying to solve this very issue. The answer Dave gave above led me on the right track.
The "merchant e-mail" in the request has to be the Paypal Sandbox Developer Account associated with the REST API app in question. I hope this helps someone.
Below is a screenshot highlighting the property in Visual Studios and PostMan.