mirror of
https://we.phorge.it/source/phorge.git
synced 2024-12-11 08:06:13 +01:00
49ef13e876
Summary: Ref T2787. I //think// we could also use WePay as a recurring payment provider, but this is somewhat messy (OAuth + requires account) -- basically it's "add a WePay account" instead of "add a credit card". The WePay checkout workflow is a bit upsell-y but basically reasonable. I like that their API just has a `request($method, $params)` method instead of 30,000 lines of methods for each request type. I did hit one bug; I'll send a pull for that. Test Plan: Got as far as the charge callback in testing; the rest isn't implemented for any provider yet. Reviewers: btrahan, vrana, chad Reviewed By: btrahan CC: aran Maniphest Tasks: T2787 Differential Revision: https://secure.phabricator.com/D5982 |
||
|---|---|---|
| .. | ||
| _shared.php | ||
| accountlist.php | ||
| index.php | ||
| login.php | ||
| logout.php | ||
| openaccount.php | ||
| README | ||
| user.php | ||
After registering your application at wepay.com (or stage.wepay.com), you need to make two updates to this application: 1 - set your client_id and client_secret in _shared.php 2 - set the redirect_uri in login.php That should be enough to start making API calls against WePay's API. While this is by no means a production-ready example, it should provide you a couple ideas on how to get running. It also defaults to requesting all possible scope fields in the authentication request. We suggest limiting the request to the minimum your application requires, which will maximize the chance the user grants permissions to your application. You can customize this in login.php. If you have any questions, please contact the API team: api@wepay.com - WePay