Paypal API and several emails in same PayPal account - api

I can not praise with my contribution here, because I am new user,
but would help if I can.
I have a big problem and I do not know how to solve it, please help.
In the same Paypal account with the default email address: email1#somedomain.com, there is 7 more emails:
email2#somedomain.com
email3#somedomain.com
email4#somedomain.com
email5#somedomain.com
email6#somedomain.com
email7#somedomain.com
that's the maximum allowed number of emails under one PayPal account (8).
So we are using API on several pages, and only one API signature can be done in the paypal
interface, so same API signature is used for each web page.
We would like to define where will money go - to which email address inside the same PayPal account.
We use Premium PayPal account, and we know that for logo change, email remove and so on, we would need Business account,
but for defining money receiver email address inside the same PayPal account
we suppose that it can be defined, otherwise we do not se a point of having several email addresses inside one same PayPal account.
The problem is that always is shown default email when making a purchase :S
We tried to define SUBJECT:
SUBJECT=merchantEmailAddress
N O T E: Typically, a merchant grants third-party permissions to a shopping cart...
And set merchantEmailAddress email2#somedomain.com.
In sandbox it works like a charm as soon as we put it on production, default mail is shown again.
Please if anyone had the same issue help.
Thank you very much, this forum is great and I realise that without nice people and contribution as well there would be no answers.
regards

You would not be using SUBJECT unless dealing with Permissions and making calls on behalf of 3rd party PayPal accounts.
You're working with a single PayPal account, so you won't be using SUBJECT at all. You'll use the credentials like you are already.
That said, I'm not sure I'm following you entirely what trying to send to different emails. I don't understand the end goal with that..?? The API credentials are what are going to tell the system where to drop the money, or pull data from, or whatever.
If you're just trying to get different logos to show up during checkout you can do that with parameters in your standard button code or API requests.
Let me know if that helps or not. Again, I'm not sure I'm understanding what you're after here.

Related

PayPal and payment implementation

I am designing a website that accepts payment through simple PayPal or Stripe buttons, but also has a section that pays out users through PayPal. What is the best way to do this?
Current setup: The user builds up coins through an action (NDA won't allow me to discuss in detail) and when their coins reach a certain amount, they can cash out in real $. I have designed this flow: Pay Me Now Button -> Screen with PayPal email address input. Repeat email for typos, then Confirm Button -> Success screen
However, the client would prefer a direct link out to PayPal instead of manual input of email addresses. The reasoning is that they would prefer it being arranged through PP's service to reduce manual errors and typing out. As far as I am aware the only way to get paid is through writing down an email address/phone number. I have researched PayPal.me buttons but it still isn't making sense. Maybe there's another service altogether that I can suggest to the client for paying out users in a no-friction way?
I'm looking at how user testing sites pay people, but not getting very far.
If the money is in your client's PayPal account and they wish to send it to a user's email address (that may or may not have a PayPal account already), this can be automated with PayPal Payouts.
If the user does not have a PayPal account already they will receive an email notification and have 30 days to create an account or add the email to an existing account. If they don't, the payment will be refunded automatically.

How does one associate a website user with a Paypal subscription?

I am implementing subscriptions to a premium service on a website using Paypal as the payment service. I have successfully created a Catalog Product and Billing Plan through the API, and I am able to get to the payment page on Paypal, but it's not clear how I'm supposed to persist a user identifier through the purchase process.
I assumed it would be something along the lines of passing a user id somewhere, but there's nothing in the Paypal documentation about this. I need to be able to let the user make a purchase and have the Paypal webhook send the confirmation to an endpoint on my site, and that's where I'd expect to get their user id to toggle the subscription on their account on my end.
Is there something I'm missing? There has to be a way to do this cause I'd imagine it's a pretty common use case. If anyone has information or has done this before, I'd love to hear. Thanks.
The only truly secure way I've found when using javascript SDK, is to securely generate a unique custom_id on your server side associated with the user.
Then when you create the buttons, the 'createSubscription' function takes custom_id as a parameter.
Then use a webhook to receive events from your subscription and the custom_id will be present in the body of all BILLING.SUBSCRIPTION events under resource.custom_id.
I am able to get to the payment page on PayPal,
You are vague about what you are doing here. There are multiple ways (and some ways have multiple versions) of accepting subscriptions via PayPal, so it is important that you provide full details about the method you are using.
The time to associate a created subscription ID with a user ID is when it is approved, in the onApprove function if you are using a Smart Payment Button: https://developer.paypal.com/docs/subscriptions/integrate/#4-create-a-subscription

OmniPay support for 2checkout API token payments?

Does anyone know how / if it is possible to use token billing? The 2Checkout API supports it and OmniPay supports token billing, but I've not had much luck and a quick look at the Official Gateway code doesn't seem to show support for it?
Anyone doing this / have any idea?
I can categorically state that it's possible to use token billing, I do so regularly. I'm not that familiar with 2Checkout but I have used token billing on stripe, paypal, PaymentWall, MultiCards, Fat Zebra and other gateways.
Is there a specific problem you're having that you can illustrate with some example code?
Does 2Checkout support token billing? Yes, and it works. However, there are some quirks with it:
You have to turn Demo Mode off on the dashboard or the 2Checkout and OmniPay API doesn't seem to work properly.
You have to send a Billing Address in order for the transactions to go through. If that doesn't work for you, such as for digital downloads, then you'll want to consider another payment gateway.
The billing address must contain a customer email and cannot be empty. Again, if that doesn't work well in your sales workflow, then you'll want to consider another payment gateway.
The billing address must contain a phone number, but CAN be empty.
I discuss this here as well as provide an OmniPay sample code snippet: https://stackoverflow.com/a/36807292/105539
Take a look at my project, TokenPay. I've weeded through the confusing docs and got it working on 2CO.
P.S. Don't ever forget your sandbox password -- they don't tell you this in the docs, but found out via tech support that their password reset on the sandbox login doesn't look disabled, but is disabled. (It would have been nice if they made that quite clear.) Instead, you'll have to create another sandbox account entirely when you forget a password there.

PayPal. Charge a security deposit

I was wondering If I could charge a "security deposit" using PayPal ?
On my site, user can pay for an item (service). But I have no idea, how to charge a security deposit, because it is NOT guaranteed that user will pay using his PayPal account - That way I could simply use MassPay API to refund the deposit back to the user (payer_email).
But, PayPal allows to pay even without creating an account. Although, user has to specify his email address, I'm not sure that sending back money to this email address would put the money on related credit/debit card.
Is there some API for doing this ? Because charging price for the item + security deposit doesn't feel right for me.
I know that, for example, airbnb.com has some similair functionality for that one, but I don't know how it works
I would be very grateful if someone helped me with that one.
Thank you!
It sounds like your primary issue is that users can checkout without a PayPal account. If that's the case, this can easily be solved by disabling the "PayPal Account Optional" feature in your PayPal profile under Website Payment Preferences. This will causes users to either sign in to PayPal or create an account to pay.
If you'd rather leave that option enabled there are plenty of ways to handle security deposits and returning money, each with their own advantages and disadvantages. I won't get into all those details yet, though, if simply disabling that option solves your issue.
Let me know if you want more info on the other options.

SMS authentication for a website

I'm looking to implement an SMS authentication for one of my projects, basically before a user is able to register an account with us, we would like to authenticate the user by sending sms containing a code to his mobile phone, and get him to put in the code in our form before he can proceed.
I've been looking around and found onVerify to be a pretty good way to go
http://www.onverify.com/
But I'd like to know if there're any other alternatives similar to onVerify as it is a bit expensive, so if I could go with cheaper one, that'd be great.
Thanks!
You can do this easily enough if you have access to an SMS provider.
Typically you send an SMS to the user by making an HTTP request, containing the verification code. You'd store this code, and the recipient number, in some persistent database, against which you can compare when they fill in the details on the form.
You don't mention which geographic regions you expect your users to be in, which can be important given the variable delivery quality in some markets.
Have a look at the HTTP API for BulkSMS, message pricing and coverage.
Note that you can register in various regions, if you, for example, want to price in USD.
Disclosure: I work at BulkSMS