How to use Conbase API as a payment gateway? - node.js

I would like to use coinbase as a payment gateway. likewise online retailers payments done can i use it like that? then help me to do it with Node.js

This is the un-official library for coinbase api that is in node.js https://github.com/otakup0pe/nodecoinbase. Coinbase has a very nice documentation with their api here: https://coinbase.com/api/doc/1.0.html and you might be interested in the transactions. Also if you just planning to sell items, you can just use the "Bitcoins Accepted Here" button VIA the Merchant tools > Tools page.

Related

Can I implement Stripe checkout in React without my own backend server?

I have a React frontend deployed on Netlify. I want to implement a simple payment system where user can enter the amount they want and pay using Stripe checkout or even PayPal. I wanted to know If this is possible without paying for a separate backend. Or is there any other self hosted payment gateway you can suggest?
thanks! :)
Technically, you can use client-only Stripe Checkout, however it's not the recommended path: https://stripe.com/docs/payments/checkout/client
Client-only is not recommended because it lacks many of the features made possible with a client-server integration. Furthermore, the client-only integration is not currently (as of this post) receiving new features or upgrades.
If you don't want to do server-sided development, then Stripe Checkout (client-only integration) is the way to go. Everything you need can be done on Stripe dashboard.
Stripe now has a solution called Stripe Payment Links. It's a client-only solution... in fact it requires no code!
As you can see on Stripe docs The Stripe API uses API keys to authenticate requests. - so this means that you need a secure way to integrate with them, without exposing those keys.
So the best way would be to use some serverless backend (FaaS) for that, like Amazon Lambda, GCP Cloud Functions etc.
Here's a good article, how to integrate Stripe with webtask.io, which should be pretty simple to use

Difference between paypal subscriptions and billing agreement?

I see paypal is upgrading their APIs. I want to collect recurring payments and provide a feature to upgrade / downgrade the plans.
In the samples, paypal is using billing agreements and when I see the docs, it says the API is deprecated please use subscriptions API. I am confused which one to use.
Please help me in this.
PS: Also my product includes one time payments
The PayPal Subscriptions API uses billing agreements and plans, and there are multiple versions. Everything linked from https://developer.paypal.com/docs/subscriptions/integrate/ will be the most recent version.
For one-time (non-subscription) payments, the most robust integration is to have two routes on your server that implement v2/checkout/orders API calls to "create order" and "capture order", combined with this front end: https://developer.paypal.com/demo/checkout/#/pattern/server
For a subscription integration to be similarly robust (in that your server gets an immediate API response of profile activation), you can have those buttons call your server as well: PayPal Smart Subscribe server side

Marketplace that allows payment on behalf of third party

I am currently developing a marketplace type of website. When it comes to handling payments, I would like to be able to charge customers on behalf of sellers.
Which payment gateway API should I use (if this is even possible)? I am using React and Node.
For reference, what I was looking for was something like Stripe Connect. According to their website: "Marketplaces and platforms use Stripe Connect to accept money and pay out to third parties. Connect provides a complete set of building blocks to support virtually any business model, including on-demand businesses, e‑commerce, crowdfunding, and travel and events."

What is the difference between Google Pay API vs Payment Request API?

I saw that Google released a new Google Pay API for the web. However, there is also a Payment Request API fo the web. Is Google Pay just a rebrand of Payment Request API? In what cases would you use one API over the other?
The "Payment Request API" is a W3C standard and a part of "Web Payments" effort. This means the API is expected to be implemented by multiple browsers and it's already landed in Chrome, Edge and Samsung Browser. And it's also expected to be available on Firefox, Safari and so on. Payment Request API is never a Google's property and it's an open standard.
https://www.w3.org/Payments/WG/
The Payment Request API is said to allow users to pick their saved credit card information with just one tap. But it's just a part of larger ecosystem. It can integrate with any third party payment apps and allow users to make payment through those apps via the Payment Request API.
Consider Google Pay one of such payment apps. Other good examples are upcoming Apple Pay (when Safari implements the Payment Request API) or Samsung Pay. Alipay also implemented one and have done a talk about it at Google I/O 2017.
https://www.youtube.com/watch?v=hU89pPBmhds
What makes it look complicated about Google Pay for those who knew about the Payment Request API is that it conceals the Payment Request API behind its library. By initiating Payment Request with just a single payment method without requesting shipping information, you can bypass Payment Request user interface and directly launch the payment app (in this case Google Pay).
https://developers.google.com/payments/web/tutorial
This article should be a good start:
https://medium.com/dev-channel/addressing-common-misconceptions-about-the-payment-request-api-4d0db51dae75
Hope this helps.

How do you hook up Dwolla or Stripe API to accept ACH deposits on website?

I am trying to hook up Dwolla or Stripe API to accept ACH deposits on my website and am having trouble going through the instructions on API connections. What programming language do you need to be able to do this?
Stripe has an ACH guide explaining what you need to do in order to process ACH payments.
You will need to write some frontend JavaScript code, as well as some backend code. The backend code can be in the language of your choice -- Stripe has official libraries for Ruby, Python, PHP, Java, Node.js and Go, but you can use any language as long as it can communicate with Stripe's API (i.e. as long as you can send HTTPS requests and decode JSON).
Jylaw38 - It depends a little on what you want to do with Dwolla. You can use the branded v1 APIs that will allow you to accept payment with a full or a direct account. Basically, that means someone can sign up for the first time and use Dwolla to pay with their bank.
The more popular route these days is to use the v2 API. The v2 API's are bank transfer API's that put you in a position to brand the experience however you want. You can learn a little more about those here - https://www.dwolla.com/bank-transfers
There are libraries available for both API's and developer support on each is available here - https://discuss.dwolla.com/c/api-support

Resources