I can't be the only one creating websites for customers that want to use PayPal. PayPal says that I have to use the customers account to create an account specific sandbox. Well, I don't want access to the customers account. I don't want to know their password. Is there a way to test the PayPal functionality without having direct access to the customers account?
Related
Currently, I working with Stripe gateway service. In my integration use only one Dashboard Stripe Account (one Publishable key + Secret key). I intend that my system create charges in two diferrentes Dashboard Stripe Account, depending others conditions.
I have analysed the "Connected accounts" using only one Dashboard Stripe Account, but is not usefull for me. I intend that each billing company have their Dashboard Stripe Account access (without mistake).
Is there any alternative beyond create customers / payment methods in both Dashboard Stripe Accounts?
pic1:
pic2:
You can build your application to manage two separate sets of keys based on the business logic for when to use one account or the other, but outside of Connect there is no other native support for something like this from Stripe. But you can absolutely do it manually. Yes, you would need to create any customers in both accounts, but this is true in a platform-connected account arrangement, too.
I am using Stripe Onboarding on my marketplace to ease the process of getting my customers info (custom accounts). But it does not ask the user his external (bank) account information so payouts stay disabled. Is it normal ?
I am using:
type: 'custom_account_verification',
collect: 'eventually_due',
using the other type does not change anything
Stripe does not collect external account information (bank account or debit card) today in the Hosted Onboarding page. They focus on collecting personal information about the owner(s) of the account/company.
Today, you need to collect this information separately on your website. The easiest solution is to collect bank account details and tokenize this client-side with Stripe.js and then create an external account server-side via the API.
Just for reference Stripe is partnering with Plaid for this.
https://stripe.com/docs/ach#using-plaid
https://plaid.com/docs/stripe/
I am going to build an eCommerce website that supports PayPal.
Buyers connect their PayPal account to the website before they get products.
The website should collect funds without a normal checkout flow whenever buyers buy products.
For this, I've researched the Permissions Service API on PayPal.
But, I can't find enough descriptions to build such a website.
I would like to know how to integrate PayPal for this.
What you are looking for is a "Reference Transactions" solution. It can be tested in sandbox, but to use it in live, the business account would need to be approved for this feature by PayPal. To do this the account owner would need to contact their PayPal account manager or PayPal's general customer support (not MTS), and explain the business need for this feature.
As far as implementing the solution, the only public documentation I'm aware of is for classic APIs: https://developer.paypal.com/docs/classic/express-checkout/ec-set-up-reference-transactions/ . Any newer API or vault solution does not appear to be publicly available at this time, but you could always contact PayPal's support and ask if there's something they'd rather you implement than those classic APIs. The more significant hurdle is the business approval for the feature mentioned earlier.
I am new to Google Actions Development. My organization wants to create some Google Actions for our project so that those Actions can directly call our APIs through Google Assistance and get the required data. Earlier I created POC using my personal Gmail account but as now we want to use it for organizational/commercial purpose I want to know which paid Google developer accounts, subscriptions do I need to purchase to use it for my organization.
I believe that the only paid account you'll need is the Firebase. When you create an Action from the DialogFlow platform it automatically creates a Firebase project for you. In order to make external calls, you'll have to update it to a paid account. So if your organization creates a Google account (or use an existing one of course) to create an action, they can just update the Firebase project to the paid and add you as a developer. If you're interested in a more secure agent, I'd suggest you to have a look at the Dialogflow Enterprise version. It has the same capabilities, but offers the security of the GCP.
We're planning a web service based on recurring monthly payments.
The site would have similar user accounts as Netflix or Spotify. The site would have an account section were the user can manage the billing and other details.
I've looked into different payment gateway provides, but I'm still wondering how to implement the user account as a part of the main site and how to combine that to the billing system.
First some information:
The site would first have just one monthly plan xx$/month
Credit cards need to be accepted
We're based in EU
We don't want to use PayPal
The user account section would contain:
User profile (name, email, etc.)
Website options (features on / off)
Subscription & billing management (edit credit card, current period, cancel, etc)
Questions:
How to combine the basic user accounts on my site with the billing system provider?
What information should I store in my own database?
Should I use a 3rd party user account management software on top of a payment gateway provider?
If so, which one would work similar to Spotify's account management?
How to setup the first sign up flow where user enters CC information?
Thank you for the ideas!
This is relatively easy to do using Laravel (a php framework) and a package called cashier. This package uses a payment service called Stripe which allows you to create recurring payments. There is even a tutorial on how to do it on Laracast.