I am using these credit card test number for test. but got null response form some of these number
test paypal credit number.
for example visa : 4012888888881881 i got null response form this number. not even i got any error. is all the number are valid or all are changed .
I found it is randomly . so if i will got no response with no error it will create recurring profile or not.
I checked your account, and I do show that requests are reaching PayPal and PayPal is sending back an API response for every request. Most were successful, some returned an API error but none the less everyone did generate a successful response back to your system. Make sure that the code that you are using is correct, and that it is set up to read the response that is being sent back. You can find some sample code that may help you here.
Related
UPDATE: After troubleshooting on postman, I've found that start_date and end_date are nessesary fields. Everything now works fine on postman with 200 code. However I am still getting a 400 error on zapier...
I've managed to POST my API credentials and generate an access-token from the previous step in my zap sequence using a Webhook. I then used this token in a GET Webhook in the next step to try and retrieve transaction information (PayPal processing fee, etc...) using transaction_id and fields queries. The transaction ID I am using is being pulled from an actual Woocommerce order on our store, where the customer decided to use PayPal (I've also searched the ID in paypal and it is valid).
The reason I'm doing this is to try and pull extra information from PayPal- Such as payment processing fees about the transaction that Woocommerce does not provide through their app on Zapier.
Unfortunately I am seeing the following error 'The app returned "Invalid request - see details."'
I suspect it is because I am calling for the information incorrectly. In my mind, I am using transaction_id as the unique identifier for the specific transaction, and fields to retrieve all information regarding the transaction.
Error code in Zapier: "Status Code 400 Bad Request" - PayPal docs state: "INVALID_REQUEST. Request is not well-formed, syntactically incorrect, or violates schema"
Update: If you use this method to pull transaction information, you will need to set a delay long enough where the activity time on your paypal dashboard switches from a time to a date (meaning it is the next day). If you don't do this, no important information will be pulled.
I've figured it out. If anyone has a similar issue, set it up like this (probably use more dynamic dates though):
I am using the simulator at https://developer.paypal.com/webapps/developer/applications/ipn_simulator to check my IPN script located at www.domain.com/ipn.asp
as part of my own IPN script, i need to re-post the IPN message that i receive, back to Paypal.
if i post back to https://www.sandbox.paypal.com/cgi-bin/websc -
the IPN simulator gives me a failed message ("We're sorry, we could not send an IPN.").
But if i post back to https://www.paypal.com/cgi-bin/webscr (the
live script) - the IPN simulator gives me a success message ("IPN sent successfully") - BUT,
my own IPN scripts tells me that the final response from paypal -
was INVALID, even though i am posting everything back along with
the cmd=_notify-validate&
So - what URL should i be using, and could there be any reason i keep getting this INVALID final response?
thanks!
https://www.sandbox.paypal.com/cgi-bin/webscr is the correct address for testing with the sandbox. The address you listed in your question is missing the r at the end of webscr.
There are a lot of reasons you could be getting an INVALID response. You'll need to debug your code to find the issue. I used PHP for my IPN listener, so I can't be of much help with that.
I am trying to set up a test process to get some authorizations completed. I managed to get a response other than Invalid Vendor (I had set up the account wrong), but now we get this response:
RESULT=52&PNREF=XXXXXXXXXXXX&RESPMSG=Insufficient permissions to perform transaction
Any thoughts on how to correct this? Request string:
TRXTYPE[1]=A
&VERBOSITY[4]=HIGH
&ACCT[16]=411111XXXXXX1111
&TENDER[1]=C
&AMT[4]=1.99
&CURRENCY[3]=USD
&USER[8]=MyPayFlowUser
&VENDOR[8]=MyPayFlowUser
&PARTNER[6]=PayPal
&PWD[10]=XXXXXXXXXX
&ORIGID[13]=XXXXXXXXXXXXX
You should have API_FULL_TRANSACTIONS. Result code 52 usually means you are trying to make a Payflow API call when you only have a Payflow Link account. Payflow Link accounts are only allowed to make an API call for the SECURETOKEN.
Without more details and looking at the account, it is hard to say what is happening. If I had to guess just based on these details you provided, it sounds like you do not have permissions to perform the type of API call that you are trying to. If you can provide the PNREF number for the transaction I can take a look at it on my end.
For the last couple of days, I have been working on realising a payment integration using the PayPal SDK for PHP (which uses the REST API). However, I have been experiencing some issues.
When a payer is redirected to the PayPal site for approving his payment and redirected back to the return URL, PayPal returns a HTTP 400 status code upon executing the approved payment. The code for executing the payment is as follows. Note that $paymentId is the ID returned after creating the payment and $payerId is the PayerID sent along with the approval.
$payment = Payment::get($paymentId);
$paymentExecution = new PaymentExecution();
$paymentExecution->setPayer_id($payerId);
$payment->execute($paymentExecution);
It says the payment is invalid:
{"name":"PAYMENT_STATE_INVALID","message":"This request is invalid due to the current state of the payment","information_link":"https://developer.paypal.com/docs/api/#PAYMENT_STATE_INVALID","debug_id":"223647e6e42fb"}
While figuring out where all goes wrong (note that the samples included with the API also give the same error), I stumbled across the following line in my log files:
PPHttpConnection: Invalid or no certificate authority found - Retrying using bundled CA certs file
I checked to make sure that the SDK locates the certificate included with the SDK. So my guess is that it's an invalid certificate. I'm kind of lost now about what to do. Does anybody have an idea how to fix this issue?
You should always check your payments state before running an execute. The error indicates that the payment already was executed
Payment state. Must be set to one of the one of the following:
created; approved; failed; canceled; expired; pending. Value assigned
by PayPal.
You probably ran the method Create on your payment, and the Create method executes the same submethods as Execute.
I am getting the response as below.
{"status":21002, "exception":"java.lang.NullPointerException"}
I am encoding the receipt using Base64 only.
I am testing it in sandbox.
What will be the problem? Can anyone help me?
hi all i got the solution
just send the receipt data after encoding into base 64 as json with key "receipt-data"
VIP Worth noting that 21002 is also the message you get back when trying to verify a transaction that was initiated via rooted iTunes hack software like the Urus app.
We verify all transactions server side, so are not device dependant, the only transactions that get the 21002 response are ALL not real payments.
an easy way to spot it to look at the transaction id returned Urus gives com.urus.iap.XXXXXXX (x being random numbers), other ones include returning the pack name as the completed transaction id, all very different to the id's you get from the various iTunes servers.
I can't recommend more that everyone verifies server-side in an environment you can control, test and prove, that cant be manipulated (unless your hacked). If this is not an option, then do not pay out on a 21002 response.
verifying in a java environment the json response for the 21002 will be:
json: {"status":21002,"exception":"java.lang.ClassCastException"}
We had the same problem - until we discovered that we didn't include the post body in the request and only sent an empty request.
The only option that work for me after 2 days of hitting my head against the wall:
Testing in the sandbox
Pay attention to this advice by apple
"Important Do not sign in with your test account in the Settings application."
Make sure on the test device you are signed out of the "test" apple store account before encoding to base 64.