I am working on a project where I have integrated stripe connect which is working fine, but now the problem is how I can check that returned details on redirect url are for a specific project.
Projects functions as follows.
1.Registered users add Non-Profit.
2.Connect to their stripe account to accept payments.
Stripe connect button has been placed on project addition page, users clicks on it and returned to a url (given in application) with connected users details, but on this page I have lost the project id for which user was connecting stripe account so I cant save it in database ( i assume that they needs to be saved in database to use at time of donation).
Am I doing something wrong ?
Is there any other way to get it done ?
I have used https://gist.github.com/amfeng/3507366 as reference.
After trying different code approaches and code samples available on net I found that we can use state parameter to get the respective id to which you want to connect the stripe account.
On my application iu https://connect.stripe.com/oauth/authorize?response_type=code&scope=read_write&client_id=CLIENT_ID&state=705 where state is the user ID to connect with.
To open authorization window I used window popup and connect to stripe account by filling details after authorization popup window is closed and then I used $_GET to get user id and saved it in database.
Related
I've signed up for a developer account with Docusign. We have about 15 users that access a Windows Forms page from another program where they fill out the proper information and click a button that calls a NET Core Web API which creates an envelope and sends to the signer. Those 15 users don't have accounts in Docusign and don't need them to. I want to use one admin or service account that will send and receive the emails, but I can't figure out how to do this.
I used my name for the developer account and now all my (test) Docusign emails show they are from me and once the signer signs, my email receives the signed documents. I've tried creating another "Admin" account, but I don't see any way to associate that user as an "API User". When I try using that user's GUID as the ImpersonatedUserID, my RequestJWTUserToken request comes back with "consent_required". But, when I go to the link I just get an error with "The client id provided is not registered with Docusign".
Everything in the Web API is working perfectly except for the emails showing they are from me and then the signed docs coming back to my email. This should be an easy thing to change the user, but apparently it's not, or I just can't figure it out.
You were on your way to fix this, but didn't follow through.
Create new user (you did it)
Find the new userId (you did)
Update JRequestJWTUserToken (you did)
Consent error - expected, the new user did not consent.
Obtain consent. You need to have a URL built correctly like this to do this:
https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=7c2b8d7e-xxxx-xxxx-xxxx-cda8a50dd73f&redirect_uri=http://example.com/callback/
Once you do 5, you need to log in with the same new user account you created (you may be automatically logged in with your original developer account, so log out) and provide consent.
Then step 4 will work just fine.
https://developers.docusign.com/platform/auth/consent/obtaining-individual-consent/
This is my scenario: I have clients who have their accounts with DocuSign. They want to record the documents information onto our app. Our app would have to call DocuSign to "import" envelope data into our app. We will need account_id to call the Rest API /envelopes, etc...
How do our clients find their account_id to give to our app?
The client need to go to the apps and keys page and find where it says API Account ID and copy the value (There's even a little icon to copy it to your clipboard).
Note that only administrators can access the above page, so your client admin must do this.
(Unfortunately, after a long research I could not find the answer for my question in stackoverflow).
I am currently integrating the PAYPAL REST API V2 in an e-commerce application and in principle it works fine, but not the way it is supposed to.
According to the documentation I am using the following steps:
Create order with user data and purchase details in the backend (nodejs)
Upon successful order creation, the front-end receives the approve_url and capture_url
The user is redirected to the approve_url and login with its credentials, and in case it is successful, the user is redirected to the predefined return_url (which is defined in the step 1)
If the user agrees with the order, the capture_url is manually called at the end of the checkout and the corresponding amount is transferred.
Since the data returned by the order is not persistent (url is being redirected), I am saving the order id and the capture_link in the local storage, which I don't think it is correct. Therefore, I have two questions:
Upon successful approval of the purchase, is it possible to redirect the user directly to capture?
If not, how can I get the order_id details in the return_url?
Thanks in advance
I figured out that the order Id was being appended to the return_url automatically. The misleading thing was that it was named token instead of order. With the order already approved by the user, I was able to complete the transaction without having to redirect the user again to the front-end.
I have sample mobile app with username and password authentication,need to valid my sample app username & password exists in netsuite based website. Please provide API info and steps to access netsuite based user info to valid my app login, currently we are using nodeJS API in app. I mean if signup/existing customer from my app would exists or not in netsuite based website
Any help appreciated !
If you are trying to log in as a customer or employee you need to ensure the records have login access, and credentials set, in NetSuite.
Not completely sure from your post if you are trying to log them in, or just access your NetSuite instance and see if they exist in the NetSuite instance, though.
Can you provide more information, and clearly state what you have tried? Code samples are a very nice thing to include, along with the errors you are receiving.
With all other web-hooks one can use an account's stripe access token to retrieve the event and then update based on the response of the API call, thus preventing possible spoofing. But with account deactivated, one is no longer able to use that account's stripe access token since the account is deactivated. Any other suggestions? Basic auth is a no-go since each account can see the webhook url.
Stripe returns an error when you attempt to retrieve that event but that error is specific to this situation. You'll get an authentication_error if you attempt to retrieve it while if your weren't connected before you'd get invalid_request_error.
You can see an example in Ruby in this connect app here