The WePay API exposes a number of WePay’s core functions to developers who would like to customize the process of accepting payments. With it, a developer can be more flexible in designing payments for their own websites and applications.
On a very high level, the WePay API allows websites and applications to make calls on WePay’s payment engine.
Any WePay user is free to use the WePay API, although coding experience will be required. To comfortably interact with the API, a user should have a solid background in web development. A list of Software Development Kits can be found here for various languages.
WePay’s terms of service still apply for users of the API. If you can’t sell it with the core platform, you won’t be able to sell it with the API.
Absolutely! You can use the WePay API to accept payments on your own website in a number of different ways. Current sellers use it for everything from simple checkout to complex marketplace integrations.
If you’re interested in using WePay for checkout on your own website, but aren’t completely comfortable with coding, make sure you take a look at WePay’s payment buttons first - it might save you some time!
Yes, WePay’s API gives you a flexible way to create recurring charges. You can use it for anything from yearly product subscriptions to recurring rent charges. Most subscription charges are created using the /preapproval call.
Yes, a use case in which you need your own users to be able to accept payments is the WePay API’s specialty. WePay’s own flexible account structure makes it very easy to quickly provision accounts to your users via an Oauth2 connect. Money collected through your application can easily be stored in these accounts until your users are ready to access it.
WePay takes security very seriously. We encrypt our data in a PCI compliant environment, and apply our rigorous standards to our API as well. If you'd like more information, you can read about it here.
Absolutely. Out of the necessity to protect the hundreds of thousands of people that use the WePay core platform, WePay has developed state of the art systems to detect fraudulent or inappropriate usage of the product. This same technology applies to all payments run through our API. The WePay engine protect all of your payments equally well.
With each transaction, WePay analyzes a variety of helpful data, all of which helps to create an accurate picture of payee and payer.
Easy! Just log in to WePay and click the WePay API application button. Referential documentation can be found at wepay.com/developer!
Yes, your WePay API application serves as the repository for all of your transactional data. You can use it to analyze your transaction history.
stage.wepay.com is our staging server. It’s the best place to test your application before pushing over to production. The two environments are otherwise almost identical except that new changes will be pushed to stage a day or two earlier than to production.
API applications are usually approved within 24 hours.
Check out our calls and reference sections on our developer page, and feel free to browse through our examples. Also, you may get started on our production server right away if you feel like you don’t need to be testing on Stage.
WePay’s API is language-agnostic, but we do provide SDKs for the most popular languages, including PHP, Ruby, Python, and NodeJS.
Use WePay’s staging server! You can create an application on stage.wepay.com and run tests just as you would on our production server. Quick note, though - you will need two sets of login credentials - one for staging and one for production.
Send us an email at [email protected]!
Your access_token is the key by which you get your application or website to interact with the WePay API. Without it, you won’t be able to do much. It’s a random series of numbers and letters that is completely unique to your application.
Your access_token and account_id can be found on the first visible page of your API application when you log in. If you don’t see it, click the API Keys section header.
You can easily issue refunds to your customers via the checkout/refund call. The WePay API also supports partial refunds, if that applies to your use case.
Refunds issued via the API don’t cost your account anything, and your customer receives 100% of the original charge back.
For additional information and documentation, please visit wepay.com/developer.