stripe-http-streams alternatives and similar packages
Based on the "stripe" category
Do you think we are missing an alternative of stripe-http-streams or a related project?
Stripe API coverage for Haskell (Stripe API)
All Stripe commands are supported, including but not limited to:
- Invoice Items
- Recipients (Deprecated)
- Application Fees
- Application Fee Refunds
- Events and Tokens
All code written for this library is documented to completion with the haddock documentation tool
Thoroughly unit-tested with hspec. All API commands are unit-tested before inclusion into the API (see the tests directory). To run the tests, perform the following:
cabal clean cabal configure --enable-tests cabal build tests dist/build/tests/tests # You will be prompted to enter your *TEST* key
Pagination is possible on all API calls that return a JSON array.
Any API call that returns a
StripeList is eligible for pagination.
To use in practice do the following:
import Web.Stripe import Web.Stripe.Customer main :: IO () main = do let config = StripeConfig (StripeKey "secret key") Nothing result <- stripe config $ getCustomers (Just 30 :: Maybe Limit) -- Defaults to 10 if Nothing, 100 is Max (StartingAfter $ CustomerId "customer_id0") (EndingBefore $ CustomerId "customer_id30") case result of Right stripelist -> print (list stripelist :: [Customer]) Left stripeError -> print stripeError
Stripe API calls can take multiple optional parameters.
stripe-haskell supports optional parameters through the use of type-families and typeclasses.
In practice, the function to use is
(-&-) to specify optional parameters on a request.
For a deeper dive into how this works, please see this blog post.
chargeCardByToken :: TokenId -> Currency -> Amount -> IO (Either StripeError Charge) chargeCardByToken tokenId currency amount = stripe config $ createCharge amount currency -&- tokenId
All versioning is hard-coded (for safety) to version
Stripe API versions specified in the HTTP headers of Stripe requests take precedence
over the API version specified in your Stripe Dashboard. In an attempt to ensure
API consistency and correct parsing of returned JSON, all Stripe versions are hard-coded, and are
inaccessible to the end-users of this library. When a new Stripe API version is released
this library will increment the hard-coded API version.
Object expansion is supported on Stripe objects eligible for expansion though the
Object expansion allows normal Stripe API calls to return expanded objects inside of other objects.
For example, a
Customer object contains a Card ID hash on the default_card field.
This default_card hash can be expanded into a full
Card object inside a
As an example:
import Web.Stripe import Web.Stripe.Customer main :: IO () main = do let config = StripeConfig (StripeKey "secret key") Nothing result <- stripe config $ getCustomerExpandable (CustomerId "customerid") (["default_card"] :: ExpandParams) case result of Right customer -> print (defaultCard customer) -- Will be an `ExpandedCard` Left stripeError -> print stripeError
Stripe objects allow the embedding of arbitrary metadata. Any Stripe object that supports the embedding of metadata is available via this API. As an example:
import Web.Stripe import Web.Stripe.Coupon main :: IO () main = do let config = StripeConfig (StripeKey "secret key") Nothing result <- stripe config $ updateCoupon (CouponId "couponid") [("key1", "value2"), ("key2", "value2")] case result of Right coupon -> print $ couponMetaData coupon Left stripeError -> print stripeError
Any API recommendations or bugs can be reported on the GitHub issue tracker. Pull requests welcome!
This project exists thanks to all the people who contribute. [[Contribute](CONTRIBUTING.md)].
Become a financial contributor and help us sustain our community. [Contribute]
Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]
*Note that all licence references and agreements mentioned in the stripe-http-streams README section above are relevant to that project's source code only.