Rapaygo For WooCommerce is a payment Gateway plugin for accepting Bitcoin payments on the lightning network by using rapaygo.com as a payment gateway. To use the plugin you will need to sign up with rapaygo.com and use your API key generated for payments on the site. See Rapaygo For WooCommerce Documentation for our complete Documentation guide.
Take instantaneous Bitcoin payments easily and directly on your store using the Lightning Network
The Rapaygo plugin extends WooCommerce allowing you to take payments directly on your store via rapaygo’s API for the Lighning Network. Rapaygo is a simple way to accept Bitcoin payments online instanaiously using the power of the Lightning Network.
Why choose Rapaygo?
Rapaygo has no setup fees, no monthly fees, no hidden costs: you only get charged 1% in transaction fees when you earn money! Earnings can instantaniously be withrawn from your account at no extra charge.
Please note, v4 of this gateway requires WooCommerce 3.0 and above. Currently only manual installation is supported for Rapaygo For WooCommerce.
The manual installation method involves downloading our plugin and uploading it to your web server via your favorite FTP application. The WordPress codex contains instructions on how to do this here.
What is “The Lightning Network”?
The Lightning Network is a simple, fast, and inexpensive way to pay merchants with Bitcoin. It uses a payment network of thousands of “nodes” that create payment channels across the world. It uses a payment unit called “SAT”, which is short for “satoshis” which makes it easier to communicate about prices. 1 Bitcoin is equivalent to 100 million satoshis.
Why is rapaygo.com exclusively on “The Lightning Network” and does not provide payment services for other crypto currency?
rapaygo.com exclusively accepts Satoshis on The Lightning network for a few reasons:
- The Lightning Network doesn’t charge merchants or customers high fees and chargebacks allowing us to pass savings on to our customers.
- The Lightning Network has instantaneous settlement, allowing you to manage your inventory and finances with more agility.
- We want people in the real world to adopt Bitcoin for uses in the real world as an alternative to fiat currency.
- We believe that the Lightning Network is the future of e-commerce.
What is the regulatory requirements for using trading Bitcoin for goods and services?
Rapaygo is not an exchange. No onramps/offramps to fiat, that’s where the regulatory stuff starts getting meaningful. Essentially rapaygo is just providing merchants a temporary wallet for barter with SATs. Asset law and taxation does apply but for the merchant, not rapaygo.
Rapaygo allows the merchant to export the required data to work with common accounting applications lile Quickbooks so your accountant can apply the appropriate legal tax codes to your use of crypto as a method of exchange.
Is rapaygo a Bank or Exchange?
No. Essentially rapaygo is a custodial Bitcoin wallet with services that make using crypto as a form of exchange easier for small merchants, just like blue wallet or breeze. Our key difference is that we are highly focused on small merchants in real world use cases and providing extended merchant tools.
What is KYC and does it apply to rapaygo?
FinCEN has proposed requiring custodial wallets to collect and report KYC information on hosted wallets for transactions up to $3,000. For this reason we do not permit transactions greater than $2,500 USD on the platform.
How does rapaygo protect my information?
Your personal information, email address, and all data is encrypted in our database and we NEVER share your email address with anyone.
Ez dago berrikuspenik plugin honentzat.
Laguntzaileak eta Garatzaileak
“Rapaygo For WooCommerce” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.Laguntzaileak
Itzul zaitez Rapaygo For WooCommerce zure hizkuntzara.
Garapena interesatzen zaizu?
Araka ezazu kodea; begira ezazu SVN biltegia, edo harpidetu garapen erregistrora RSS-(r)en bidez.
- First GA version.
- All core capabilities included for MVP.
- changed validation and sanitize methods
- added init callbacks
- moved to external class file
- align versions with stable tag
- image assets missing from build