I'm using PayPal Smart Payment Buttons to enable payments on my website.
I managed to disable the shipping address fields, but I can't disable the billing address.
From what I've seen most of the sites that accept online payments don't require billing address or any information except for the credit card details and the name of the card holder.
Why does PayPal require to enter billing address and is there a way to disable it?
Thank you!
Billing fields are used for payment processing by PayPal, as they are necessary for communication with credit card companies for example. They are not returned to you or included as part of the transaction that you see. You cannot remove them.
Most websites that directly collect credit card information, also collect a billing address. It is relatively uncommon to process cards online without a billing address, especially in countries that use address verification (AVS) responses from credit card processors/issuers, since doing so without the billing address is less secure (no address verification can take place) and so more prone to fraud.
Related
I have a problem with google cloud's billing verify. I added a debit card, which has received an X amount of eurocents from Google. To verify my billing, I need to type that amount into the 'billing account'. However, when I click 'billing' it says there are no accounts, when I try to create one, it tells me my billing account is awaiting confirmation. Any ideas?
TL;DR You could experience some issues when adding a payment method to your billing account in Google Cloud. The best you can do if you face any issue after reading the documentation is to contact Billing support.
If you receive an error such as Your card does not support automatic recurring payments or General decline of the card, please select a different form of payment.
As I can see from your question, you tried to verify Your Bank Account, as stated in the documentation:
A small test deposit will appear in your bank account within a few days of adding the account as a payment method. After you see the test deposit, you should verify the deposit as described in Find and enter a test deposit.
Instant bank verification
We offer instant bank verification for Google Cloud customers. Unlike the test deposit verification method, which takes several days to complete, instant bank verification allows you to verify your bank account within seconds.
You can use instant bank verification in either of the following situations:
If you haven't entered your bank account information yet
If you've recently entered your bank account information
Verify your payment method (US only)
Note: Currently, this service is available only to customers with a U.S. bank account.
In the resolve errors when attempting to add or update a payment method section, it mentions that
you might receive an error such as:
Your card does not support automatic recurring payments.
or
General decline of the card. No other information was provided by the issuing bank.
You might encounter these errors if you are using a debit card that requires two-factor authentication...
When you enter a debit card as your form of payment, Google checks whether your issuing bank approves subscriptions or recurring payments using that card. If your bank does not approve, this card will not work for automatic recurring payments.
If you receive an error such as Your card does not support automatic recurring payments or General decline of the card, please select a different form of payment. You can also contact Cloud Billing Support for help.
Therefore, some of the issues when adding a payment to your Cloud Billing account could be related to some bank restrictions and could even be related to some domestic and international regulations, as it occurs to customers in India.
As stated in the Payment Methods documentation:
The payment methods available for your self-serve (online) Cloud Billing account depend on your currency and country. In many countries, you can set up a credit card, debit card, or bank account as a primary payment method.
So in the first instance, I suggest you review the List of countries and regions.
If your country or region is not listed here, this might indicate that your country or region's currency is not supported for Google Cloud charges. In these instances, your Cloud Billing account might incur charges in USD.
For countries or regions not listed here, check the payment options tool for information.
Then, you should check the Supported payment methods:
The types of cards Google services lets you add to payment profiles vary by location and by product.
American Express
MasterCard
Visa
Discover (U.S. only)
JCB (Japan and U.S. only)
Visa Electron (Outside the U.S. only)
Elo credit cards (Brazil only; We don't allow you to add Elo debit cards)
Debit cards with the Visa or MasterCard logo
Bank account
If supported in your country, you can add a bank account to pay.google.com to pay your Cloud Billing account.
Verify Your Bank Account
Depending on your country, you might need to verify your bank account to use it as a payment method by direct debit. A small test deposit will appear in your bank account within a few days of adding the account as a payment method. After you see the test deposit, you should verify the deposit as described in Find and enter a test deposit.
Also, there are some unsupported payment methods:
Debit cards that require two-factor authentication
are not accepted for payment.
Prepaid cards and Virtual Credit Cards (VCCs) are not accepted for payment.
Bank accounts that only support disbursements are not accepted for payment.
Payment via wire transfer is not supported for monthly charge or threshold billing
accounts.
You may pay with a bank account by adding it as a payment method, if
supported in your
country.
So, as long as your payment method is supported, you could add it to your Cloud Billing account.
See also:
Fix payment and billing issues
How to fix a payment issue - YouTube video
I know how to get the device address from the Alexa app.
Now I need the addresses located in settings --> my locations. When I add a business address, I can use this address by saying "work".
I would like to use this address in my skill for work as well. How can I get it?
(Maybe the naming of settings is not 100% correct. I translated it myself.)
I don't think Amazon currently offers this to skill developers. Home & Work addresses are part of the user's Alexa account and would likely be accessed through the Customer Profile, but only name, email, and phone number seem to be available for skills to use according to their Customer Profile API docs.
Skills can only access an individual Alexa device's saved address through the Device Address API.
You can submit a feature request on their Developer Voice and Vote site.
I am new to cryptocurrency application development. I am using web3js library and reference is
https://web3js.readthedocs.io/en/1.0/web3-eth-accounts.html for managing wallet balance and multiple account address link with single wallet. How can i do this?
We want every user deposit ether comes to out(application) wallet so we can reduce transaction charges as for individual it will many times(between our app, ethernet, user address, so on) from one account to other.
Many exchanges implement an overlay SQL Database to manage account balances, as banks do.
The accounting API on bitcoin (or its' inheritance crypts) does not support that very well and it might get you confusing, which is why the accounting API has been deprecated.
You would need to:
Allow users to register accounts at your database.
Create an address using the RPC API, and associate it to the user logged in.
Monitor the user balance by logging every transaction associated to his wallets.
I have a website(PHP) which has payment functionality with recuring/autopayment feature where user will enter their credit card detail once for shopping and from next time onward they don't need to enter their credit card detail again. Credit Card detail will not be saved to my database but will be saved in payment gateway with unique id/reference. I just need to use reference id for payment whenever user do shpping.
Earlier, i was using authorize.net payment gateway with its CIM(Customer Information Management) feature for auto payment which was working fine but now my client does want this payment gateway. I want some alternate payment gateway which support CIM feature.
If someone has already done same kind of stuff then please help me.
Authorized.net is the best option, because of reputation, costs and developer friendly environment. However there are alternatives as stripe, 2checkout, braintree...
I have seen a disturbing trend where websites are starting to require verification sent to cellphones by text message (SMS). Gmail and Facebook are two of them. What I want to know are the following:
Is it a good idea to start requiring cellphones instead of emails now?
How do I do it on my own website?
Edit
Here are some of my new questions on the topic in response to the answers:
I see that most of you are saying that SMS registrations is ok. But what about the people who don't have cell phones? And why is it accepted to give out your cell phone information freely?
Do those big providers really pay per message to a gateway service? Is it not possible to set up a server with the correct SMS software, or at least buy a subscription directly instead of having a middleman?
Most SMS Gateway services have some kind of API. An HTTP interface seems to be the norm.
Just make sure you sign up for a service that allows receiving of messages because not all do. It's more work for them since they have to send some kind of data back to you.
Some services offer send receipts too which lets you see if the receiver got the SMS.
Some examples follows.
Esendex API docs
TxtLocal
In regard to question number one, I think Commander Keen's advice is sound.
It is a good idea if you want to limit the number of fake accounts. I see it used lots in local newspapers here in Norway. I guess it makes people think twice before posting useless crap on their discussion forums.
But do you really hate your users that much? Gmail and Facebook are big enough now that people will accept jumping a few hurdles to use the service, but you need something really interesting to make the user accept this inconvenience.
SMS is the reason I can't use App Engine ().
The first problem is that some people do not have cell phone. I can use Facebook almost completely without validating cell, but uses CAPTCHA to get through certain actions. Therefore, CAPTCHA is one of the good alternatives.
I personally think, cell phone stuff belongs to cell phones and should not be in the Web.
What if every forum admins and newbie PHP developers in the world used SMS validation and someone hacked (cracked) into their database? Do you trust a small forum? Is anti-fraud measure required so desperately?
If your site is very large and popular, it may be good to get SMS validation.
As a member of CS Networks Support team. I am going to give you some answers.
People use their cell phones as a medium of verification, so the service providers can be sure that registered member is not a bot or something else.
Yes it is true. Big providers pay for SMS gateway services. Yes it is possible to have an infrastructure like that, but it is recommended that you have a team of people that are in this business for a long period of time.
The one main reason for using SMS as a way of authentication is that you link the account to a mobile phone, which effectively reduces the chance of fake user accounts by a very large margin.
To implement this feature, you will need to sign an agreement with a SMS Gateway that has coverage for the countries (and operators) that your customers are located in..
Most SMS Gateways can easily be integrated in your software, and will most often provide you with access to all the mobile operators that you require.
I would not recommend using an email to sms gateway if you can use an API, as these are most often less responsive than using a proper API to send messages, where you will get a live connection with the SMS gateway itself, not an email server in front of the gateway.
Examples of SMS Gateway providers:
PSWinCom - www.pswin.com (Note: I am employed in this company.)
Clickatell - www.clickatell.com
HSL - http://www.hslsms.com/
Answer to 1st question: One reason which I can think of that led Gmail and Facebook to follow this trend is the emergence of bogus accounts. Now-a-days, there are use-n-throw email availabe for free like www.10minutemail.com which gives u an email address for 10 minutes. So the use can take such an email address and start a new account in the site.
But in the case of 'sms'-registration, I dont know of any such use-n-throw service provider. So everyone needs to give his own number for registration. This leads to registration by legitimate users.
Answer to 2nd question: This depends on which language u are using. Moreover, you may need a SMS gateway to achieve this.
Since you dont care about the language, try to look for SMS gateway for sending sms through computer or your web server. Some of the cellphone network providers provide an email service to send sms to a phone. For example, you are sending an sms to +910123456789 of 'xyz' network provider, you just need send the sms in the body of an email with the to-address as +910123456789#xyzmail.com
'xyzmail' part of the mail address will change according to the network provider. Plus this option is not found to be reliabe.
check out TeleSign.com
they offer phone verification solutions that you can implement into your website
phone verification is a way to reduce fraud and spam significantly
There's a trust issue here that goes both ways. If you're the provider of a service that can be spammed, you can trust that your users are people and that their email addresses are legitimate. This is probably irrational. Or you can force your users to trust that you'll deal with their cell number information safely. Many users will feel this is irrational.
And then there are people without cell phones (I happen to be one). Most discussions on the web aren't very important, but if you're trying to foster a discussion on anything important, limiting the discussion to people that have cell phones and know how to receive text messages will limit your discussion to the viewpoints of the rich and technologically savvy. If you're providing an important service like email, a texting requirement sets up a barrier to entry and saps the democratizing power of the web. It amounts to shunting the cost of your spam problem onto the disadvantaged. To me, that's unacceptable. Again, though, if your site is just inane pop culture or a marketing exercise, as most are, who cares, go right ahead.