I am trying to create app id with pro account.I have integrated paypal Getvarified status api with sandbox APP Id .Its working fine.For integrate that api i need live app id ,I am using LIVE REST API STEPS from following link:
http://geekmechanics.weebly.com/paypal-rest
then api code display the app id wrong error.
I am stucked here from last 3 days .Anyone can help me please.Thanks In Advance.
Rest APP id is different from Adaptive APP id. Getverified status API needs Adaptive APP ID. Please refer the following link:https://www.paypal-apps.com/user/my-account/applications. Sign into your PayPal account and submit the application. For PayPal support refer the following link: https://www.paypal-techsupport.com/app/ask.
Related
I am working on a project about payments with stripe, I have done the Api for mobile with Laravel. I have also done a admin panel to watch and manage the data of the mobile. Now what I need to do is set payments for mobile stripe. Can u help me on the idea now, do i need to create Api for mobile to make payments like on a website stripe payments or mobile can use stripe api and just post me the data for 'user_subscriptions' and than this data can be watched by my admin panel.
Thanks in advance for your time if you stop by!
You can use Webhooks for this for example once a payment is done Stripe Server will automatically call a API on your server with all the necessary data.
I want to setup the neteller merchant api in my website that my client can pay me.
anyone can give me a overall guideline? I search over the internet but cannot find the proper solution
thanks In advance
Are you going to integrate just wallet payments, or you want to integrate the NETELLERgo! payment gateway as well? The steps for both solutions are different.
Anyway, in general, first off you will have to setup your merchant account for use with the NETELLER REST API. The steps include:
Go to your merchant account >> "Developer" tab >> "Documentation" page and download the latest REST API Reference guide. You will need that a lot.
Set up the IP addresses from which your webserver will be accessing the NETELLER API. You can do it from your merchant account >> “Developer” tab >> ”API Settings” page. See the the REST API guide, page 18.
Create a new App. This step is necessary in order to get REST API access credentials. This can be done from your merchant account >> “Developer” tab >> ”Apps” page. See the REST API guide, page 19.
Now you are ready to use your merchant account for requests to the NETELLER REST API.
If you are going to integrate just NETELLER wallet payments, the rest of the steps would be:
Get access token. Your application will first need to obtain an access token in order to be able to make a request to a resource in the API. To do that, you will need the “client_id” and “client_secret” values, which were generated during Step 3) above. More details are available in the REST API guide, page 41. Please note that you will need to get a new token for each request you make to the API.
Create a deposit/withdrawal. Using a new token from Step 1) above, make a request to the REST API for an incoming/outgoing transfer. You will need to build a form, which collects the customer's payment credentials and passes them in the API request. More details are available in the REST API guide, pages 54 and 58.
This integration requires you to build the payments page - there is no redirection to the NETELLER gateway, just 2 API requests and the payment is done.
If you are going to integrate NETELLERgo!, follow these steps:
Get access token. (see above)
Create an order. Using a new token from Step 1) above, make a request to the REST API for a new order. More details are available in the REST API guide, page 63.
Redirect the user – In response to step 2) above, you will receive a link to a hosted payment page where you need to redirect the customer to complete the payment.
Implement webhooks – You will need to implement webhooks for payment events, which will handle confirmation of the transaction status. More details on webhooks are available in the REST API guide, page 108.
I am trying to integrate authorize.net payment gateway in my e-commerce based website. The payment is recurrent, so I am using Authorize.net Automated Recurrent Billing (ARP) API here : http://developer.authorize.net/api/arb/
Now, I would like to know if it is possible to configure the notification url in the API ?
I read, that I can configure the silent post URL in the account settings here :
https://sandbox.authorize.net/UI/themes/sandbox/merch.aspx?page=settings&sub=adcsilent&xhtml=ADCSilent-settings&operation=get
I am trying to set the notification URL in the API iteself.
Thanks
You cannot set it in the API call. It can only be set in the account settings.
I am trying to integrate webmoney transfer api to my website. I downloaded the sample code in php, set up the database but when I am executing, it is giving error "Purse is not activated"
Also using this method how will I exchange webmoney from buyers webmoney to merchant webmoney.In this example it is just taking static money.
Please help me to integrate this.Thanks!
You should first activate your WM wallet at https://merchant.wmtransfer.com/conf/purses.asp
I try sample files inside latest php API for adaptive payment (1.96) and creating a primary pay. then did pay with my sandbox account and every things working fine. I use the same process and integrate API with my php application.I'm able to create primary payment and get payKey. I use payKey and do payment. I login with my sandbox personal account and click pay then see this problem:Your payment can't be completed. Please return to the participating website and try again.
Note: I did not change any config.ini information.I create multiple pre-confiq accounts in my developer and put them as sender or receiver through sample and application test.both API sample and application environment are virtual hosted on my local machine.this is paymentDetail object info
I found problem.
I was resetting test account and creating new test emails that noted on one suggested solution and forgot to replace new email in my integrated application.
by the way replacing new email solved my problem.