Skip to content

Releases: vapor-community/stripe-kit

StripeKit 3.0.1

09 Dec 23:09
3f5dec6
Compare
Choose a tag to compare

This patch release fixes #13

StripeKit 3.0.0

03 Dec 23:40
62174cd
Compare
Choose a tag to compare

StripeKit 2.0.1

06 Nov 03:00
2e6d1c4
Compare
Choose a tag to compare

Fixed a typo in customer update routes.

StripeKit 2.0.0

06 Nov 02:43
1cc8418
Compare
Choose a tag to compare

Updated to support the latest 2019-11-05 API.

StripeKit 1.0.11

03 Nov 06:46
970e510
Compare
Choose a tag to compare

Use release version of AsyncHttpClient.

StripeKit 1.0.10

18 Oct 19:31
92c4aae
Compare
Choose a tag to compare

Fixed decoding for an optional property.

StripeKit 1.0.9

06 Oct 18:44
c6d1ffc
Compare
Choose a tag to compare

Fixes an issue where we weren't shutting down the AsyncHTTPClient on deinit

StripeKit 1.0.8

11 Aug 00:11
0ddc94d
Compare
Choose a tag to compare
StripeKit 1.0.8 Pre-release
Pre-release

Fixed issue with the Products API

StripeKit 1.0.7

03 Aug 23:36
163274e
Compare
Choose a tag to compare
StripeKit 1.0.7 Pre-release
Pre-release

Updated to use latest AsyncHTTPClient

StripeKit 1.0.6

16 Jul 00:12
a6142b3
Compare
Choose a tag to compare
StripeKit 1.0.6 Pre-release
Pre-release

This release adopts the NIO pattern of retuning failed EventLoopFutures rather than having throwing functions. So instead of a do catch pattern you would opt for something like this instead

stripe.charges.create(amount: 2500,
                       currency: .usd,
		       description: "A server written in swift.",
                       source: "tok_visa")
 .flatMap { (charge) -> EventLoopFuture<Void> in
	  if charge.status == .succeeded {
	      print("New servers are on the way 🚀")
	  } else {
	      print("Sorry you have to use Node.js 🤢")
	  }
  }
  .flatMapError { error in
     print("Stripe error \(error.message)")
  }