cc586b0afa
Summary: various stripe stuff, including - external stripe library - payment form - test controller to play with payment form, sample business logic My main questions / discussion topics are... - is the stripe PHP library too big? (ie should I write something more simple just for phabricator?) -- if its cool, what is the best way to include the client? (ie should I make it a submodule rather than the flat copy here?) - is the JS I wrote (too) ridiculous? -- particularly unhappy with the error message stuff being in JS *but* it seemed the best choice given the most juicy error messages come from the stripe JS such that the overall code complexity is lowest this way. - how should the stripe JS be included? -- flat copy like I did here? -- some sort of external? -- can we just load it off stripe servers at request time? (I like that from the "if stripe is down, stripe is down" perspective) - wasn't sure if the date control was too silly and should just be baked into the form? -- for some reason I feel like its good to be prepared to walk away from Stripe / switch providers here, though I think this is on the wrong side of pragmatic Test Plan: - played around with sample client form Reviewers: epriestley Reviewed By: epriestley CC: aran Differential Revision: https://secure.phabricator.com/D2096
21 lines
618 B
Plaintext
21 lines
618 B
Plaintext
= Installation
|
|
|
|
Obtain the latest version of the Stripe PHP bindings with:
|
|
|
|
git clone https://github.com/stripe/stripe-php
|
|
|
|
To get started, add the following to your PHP script:
|
|
|
|
require_once("/path/to/stripe-php/lib/Stripe.php");
|
|
|
|
Simple usage looks like:
|
|
|
|
Stripe::setApiKey('d8e8fca2dc0f896fd7cb4cb0031ba249');
|
|
$myCard = array('number' => '4242424242424242', 'exp_month' => 5, 'exp_year' => 2015);
|
|
$charge = Stripe_Charge::create(array('card' => $myCard, 'amount' => 2000, 'currency' => 'usd'));
|
|
echo $charge;
|
|
|
|
= Documentation
|
|
|
|
Please see https://stripe.com/api for up-to-date documentation.
|