Need help to accept business credit card credentials.
The REST API for credit cards needs the fields "First Name" and "Last Name" in case of a business credit card the card usually shows "Company Name" in line 1 and the name of the employee allowed to use the card which is the second line.
Should I put the company name in "First Name" and the employee name in "Last Name"?
Many thanks for fast response as I have to implement it for my client.
I would just go with the first and last name of the employee and that should work out fine for you.
Related
Loggin into my sandbox I can create a credit card. Whenever i try to change the first address line to "CCREJECT-REFUSED" I can't save the card because it gets rejected.
I can create a address with that line. But when I assing the address to a existing card it rejects to save the data again ...
How should I change the address?
I was able to solve this by upgrading my Sandbox account making the payment from PERSONAL to BUSINESS.
At one point this process also fails for me, but if you log out and back in, your account should be upgraded.
From here you should be able to follow these steps (taken from PayPal support) to create a credit card with CCREJECT-REFUSED.
So, login to your sandbox account of choice, click on profile > my money > debit and credit cards and click on "update" or use the direct URL below :
https://www.sandbox.paypal.com/businessprofile/mymoney
Click on "Add a Card", select the "Add Credit Card" tab near the top and enter the following details.
Card Number: 5411896071554102
Expiration Date : 12/22
CSC : 123
Billing Address : click on "change" and in the "address line 1" section, enter "CCREJECT-REFUSED" and then click on "Add Card".
I am currently using PayPal to handle credit card payments on my website.
I would like to know what fields are absolutely required to process a successful payment.
This is particular important to know when handling credit card payments in other countries, to be specific the address fields as other countries do not uses zip code,state....
Also is the Cvv field required?
My card payment form includes the following fields:
card Type:
Card Number:
Cvv Code:
First Name:
Last Name:
Expiry month and Year:
Street Address:
City:
State:
Country
While testing credit card payments with PayPal test accounts I only needed to supply the card type, number , first and last name and expiry month and year.
This depends on how you have your PayPal account configured. With Payments Pro, you can setup Fraud Management Filters within your PayPal account. There, you can specify whether or not you want to decline cards where AVS or CVV2 does not match or if you just want to accept them (or flag them).
So, the answer to your question is "it depends on your settings."
Whenever our service initiates an express checkout and redirects the user to PayPal page the user sees the cart on the left and the following on the right:
Note that even the address and the phone number are required while we're an online service and don't need shipping information - once PayPal confirms the payment we'll happily "ship" over the Internet, so all we really need is a PayPal payment confirmation and I guess that requires just a credit card number, expiration date and the CSC.
Yes, I know that users who have already registered with PayPal can switch to "my PayPal account" option but that doesn't help people who don't have a PayPal account and those are forced to see this page with 12 fields.
Wait, that was the form for people who have their "country" identified as the USA. Here's what people tracked to Colombia see:
Even more fields and we only need a payment confirmation.
Is it possible to make PayPal limit the set of fields on that page?
Looks like you can avoid user to enter Billing and Contact information on guest checkout only if you properly transmit REAL shipping/contact data by your own in your SetExpressCheckout call.
&METHOD=SetExpressCheckout
&RETURNURL=https://...
&CANCELURL=https://...
&PAYMENTREQUEST_0_AMT=10.00
&PAYMENTREQUEST_0_PAYMENTACTION=Sale
&PAYMENTREQUEST_0_SHIPTOSTREET=1 Main Street
&PAYMENTREQUEST_0_SHIPTOCITY=San Jose
&PAYMENTREQUEST_0_SHIPTOSTATE=CA
&PAYMENTREQUEST_0_SHIPTOCOUNTRYCODE=US
&PAYMENTREQUEST_0_SHIPTOZIP=95131
&PAYMENTREQUEST_0_EMAIL=jsmith01#example.com
&PAYMENTREQUEST_0_SHIPTOPHONENUM=408-559-5948
If you set random data above with invalid city/state/zip PayPal will display Billing and Contact information inputs.
Instant Payment Notification script receives among other parameters the following one:
payer_id = LPLWNMTBWMFAY
What is the meaning of that string?
It's an external unique identifier of a particular PayPal account. Since email addresses change over time. A PayerID is static.
As others have said, payer_id can be used to identify a Paypal account. HOWEVER! -- a single Paypal account can have several payer_ids associated with it, one for each credit card or funding source used by that account. Because of this, a given Paypal account does NOT map one-to-one to a single payer_id.
For example, if Bob buys from my website (through Paypal) using his Visa card, the transaction will include one payer_id. If Bob later buys using his Mastercard, the transaction will include a different payer_id.
I confirmed this in a phone call with Paypal Merchant Technical Solutions, in May of 2013, after running into problems with my order processing (due to an incorrect assumption I had made about payer_id being a reliable way to see if a customer already existed within my customer database).
NB: One ramification of this fact is that, when writing a Paypal IPN-processing script, payer_id should properly be stored only in the "orders" database table, and not stored in the "customers" table.
See also this answer: Is the paypal payer_id unique per credit card?
EDIT:
Apparently, each PayPal account does get just one payer_id. (That is not what I gleaned from my aforementioned phone call with Paypal Merchant Technical Solutions, but I can't find my notes on that call, so perhaps there was some confusion there.) Regardless, the payer_id does NOT uniquely identify a customer – as in a single, unique individual somewhere out there in the world. A customer could use multiple Paypal accounts, or could make some purchases as a "guest" using a different funding source than their primary Paypal account, and merchants would get different payer_ids for each one – even if the person's name, address, and all other identifying information were exact matches.
For these reasons, it is misleading for Paypal to call the payer_id variable a "Unique customer ID". Unfortunately, that description still persists in their documentation (scroll to the bottom of the "Buyer information variables" section):
https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNandPDTVariables/#id091EB01I0Y4
It's just the id of the user who paid. You have to log it, to be able to give it to Paypal in case of conflict.
Payer_id is just paypal id of who pay the payment.
Email id is dynamic and always change, but payer_id is static.
I have set up a website with integration with paypal's Payment Standard. This includes address_override=1 to send to paypal a fixed the delivery address.
A "helpful" feature of paypal is that it pre-populates the uploaded address into the billing address fields for an unregistered user.
If the user then fills in their credit card details their card will obviously be declined as the billing address must match their card. All works fine if the user realises the error and replaces my uploaded address with their real billing address, but the client im working for is nervous that users will not realise to do this... I have to agree somewhat.
Does anyone know of a solution to this? some variable I'm missing in the standard variables docu's from Paypal which says:
"thiis is an address override, but only uise it for delivery adress, never billing address"
a year too late for a reply but I had the same problem.
I cannot separate the billing and shipping address. In my case, users can buy items as gift so the billing and shipping address will be different...and just today, I recently found out PayPal has no way to separate both. Oh boy.
In the script that commnunicates with PayPal, there will be an "address_override" => "1". Simply, change this to "address_override" => "0".