HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
balanced
balanced-api
Ruby2012–2014
balanced / balanced-api

balanced-api

Balanced API specification.

15Distinct people
50Mentions
0Explicit recommenders
220GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Balanced API specification.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month50 dated mentions

Observed mentions: 2012-08-17 19:37:53 UTC to 2014-07-22 19:16:43 UTC.

02468102012-08-01 00:00:00 UTC to 2012-09-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsAug 20122012-09-01 00:00:00 UTC to 2012-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-10-01 00:00:00 UTC to 2012-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-11-01 00:00:00 UTC to 2012-12-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2012-12-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-01-01 00:00:00 UTC to 2013-02-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2013-02-01 00:00:00 UTC to 2013-03-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2013-03-01 00:00:00 UTC to 2013-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-04-01 00:00:00 UTC to 2013-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-05-01 00:00:00 UTC to 2013-06-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-06-01 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-07-01 00:00:00 UTC to 2013-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 20132013-08-01 00:00:00 UTC to 2013-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-01 00:00:00 UTC to 2013-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-01 00:00:00 UTC to 2013-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-11-01 00:00:00 UTC to 2013-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-12-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2014-02-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2014-02-01 00:00:00 UTC to 2014-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-03-01 00:00:00 UTC to 2014-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-04-01 00:00:00 UTC to 2014-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-05-01 00:00:00 UTC to 2014-06-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2014-06-01 00:00:00 UTC to 2014-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-01 00:00:00 UTC to 2014-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 2014

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20122012-08-01 00:00:00 UTC2012-09-01 00:00:00 UTC321
Sep 20122012-09-01 00:00:00 UTC2012-10-01 00:00:00 UTC000
Oct 20122012-10-01 00:00:00 UTC2012-11-01 00:00:00 UTC000
Nov 20122012-11-01 00:00:00 UTC2012-12-01 00:00:00 UTC725
Dec 20122012-12-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
Jan 20132013-01-01 00:00:00 UTC2013-02-01 00:00:00 UTC303
Feb 20132013-02-01 00:00:00 UTC2013-03-01 00:00:00 UTC1019
Mar 20132013-03-01 00:00:00 UTC2013-04-01 00:00:00 UTC101
Apr 20132013-04-01 00:00:00 UTC2013-05-01 00:00:00 UTC202
May 20132013-05-01 00:00:00 UTC2013-06-01 00:00:00 UTC202
Jun 20132013-06-01 00:00:00 UTC2013-07-01 00:00:00 UTC202
Jul 20132013-07-01 00:00:00 UTC2013-08-01 00:00:00 UTC000
Aug 20132013-08-01 00:00:00 UTC2013-09-01 00:00:00 UTC000
Sep 20132013-09-01 00:00:00 UTC2013-10-01 00:00:00 UTC000
Oct 20132013-10-01 00:00:00 UTC2013-11-01 00:00:00 UTC000
Nov 20132013-11-01 00:00:00 UTC2013-12-01 00:00:00 UTC101
Dec 20132013-12-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
Jan 20142014-01-01 00:00:00 UTC2014-02-01 00:00:00 UTC707
Feb 20142014-02-01 00:00:00 UTC2014-03-01 00:00:00 UTC101
Mar 20142014-03-01 00:00:00 UTC2014-04-01 00:00:00 UTC202
Apr 20142014-04-01 00:00:00 UTC2014-05-01 00:00:00 UTC101
May 20142014-05-01 00:00:00 UTC2014-06-01 00:00:00 UTC404
Jun 20142014-06-01 00:00:00 UTC2014-07-01 00:00:00 UTC000
Jul 20142014-07-01 00:00:00 UTC2014-08-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Balanced API Specification This repository contains an executable specification of the Balanced API. The goal of this repository is two-fold. First, to ensure that the API is working according to the spec. Second, to provide a place to have discussions around the API as a product. An Executable Specification Specifications don't matter if they're not followed. Therefore, this specification is executable, so we can ensure conformance to the spec. There are more details in the README file inside the features directory, but to run these tests yourself, simply: $ git clone https://github.com/balanced/balanced-api.git $ cd balanced-api $ bundle $ bin/rake cucumber This requires Ruby. We run the changes with Ruby 2.0, but other versions will probably work as well. Let us know if you have any problems running these specs, and we'd be happy to help. If you're working on a new scenario, the 'focus' task is useful. Tag a scenario with @focus, and then run bin/rake focus. It will only run that single scenario. Discussions around changes Speaking of issues, that's the second purpose of this repository. If you would like to see a new feature implemented in the Balanced API, please open an issue and we'll discuss it. For example, one of our biggest requests is to support non-USD currencies. Here is the issue with the discussion, and when we support this feature, we close the issue via a pull request that implements the specification, and then everyone on the issue gets notified. Sometimes, Issues are great for collecting feedback, as well. For example, all implementation of the current framework was done via PR, and some issues need more explanation around use cases by those who want the feature, like Bitcoin support. We try to do as much 'internal' discussion in these issues as well, it's not just for public feedback. If you want to know what we're thinking, just search for a relevant issue! Edit field descriptions for scenarios Field descriptions are from balanced.rev1.json, which are generated from balanced-api. The "forms" used in balanced-docs are assembled from parameters supplied in the scenarios in balanced-api. Those scenarios should be updated to include the fields missing the specific scenario section and a newly generated balanced.rev1.json be committed into the docs. To generate balanced.rev1.json in balanced-api run: bundle exec rake features:all DO NOT run bundle exec rake parallel:features doing so causes the file to overwrite itself.
Read the full README on GitHub

What Hacker News says

2 sources
As someone who has previously used Balanced and played around with Stripe enough to get a feel for it, I feel like I need to chime in here. Balanced initially reached out to me, and I initially somewhat dismissed them, because I didn't have the time to look in to their platform as I was busy building a marketplace product for which we thought we had already picked the payment provider for, PayPal. However, few weeks later I decided to take the time to investigate Balanced's offering and I was quite simply blown away by what they had to offer at the time (since then their offering has significantly expanded). As a result, I decided to make some time to rewrite our payments to use their APIs, because they solved the one hard problem I had yet to solve, which is the payouts. I distinctly remember that I had just spent the earlier part of tha
Read the rest
t week going over the various alternatives to how we could handle payout, and none of them seemed optimal. While paypal certainly would've gotten the job done, it was far from ideal especially considering that our merchants would've had to sign up for a paypal account and the fact that they have a track record of mistreating individuals and businesses by freezing accounts and funds. The other alternatives I had considered would've been much more work to integrate with and would've probably eventually driven me up a wall. This was the first thing that struck me as the truly valuable feature of their product. When I actually began integrating with Balanced, my "developer relations" experience with Balanced has been quite the opposite. Heck, I had a phone call with one of the Balanced founders (Jareau) where he took the time to answer all of my questions and explain to me how everything worked. In addition, I was able to simply hop on to Balanced's IRC channel (#balanced on Freenode) and talk to their whole team right there and then in real time. When I had questions about any of the functionality, there would always be someone from Balanced's team available to answer my questions. I should also mention that even some people outside of Balanced (i.e. customers) are also helping out on that channel. Yet again, I was impressed. I never had issues with getting the kind of support I needed from Balanced, they are very responsive and helpful in solving any problems I have encountered. Not to knock on Stripe or anything, but I never quite felt like their product was suitable for the situation that Balanced is suitable, a marketplace that needs to do payouts (or nowadays I suppose anything that needs to payouts). I feel like Balanced really hits the sweet spot when it comes to payouts, and they continue to work hard on making sure that their product is the best that there is in that category, and I certainly think that is the case right now. One thing that I think bears mentioning is the fact that Balanced is also very receptive to customer feedback. In my experience, they are constantly weighing out what's the next thing they should be building/doing to make their customer's lives easier, and so their process is very much driven by the feedback provided by their customers (check out their API docs github to see the process in action, https://github.com/balanced/balanced-api/issues) Overall, I do think that Stripe and Balanced to have overlap in what they do for you (charging a credit card), but I also feel like both of them have their strengths in differing features. I do think that for marketplaces that need payouts, Balanced is vastly superior because of the feature set that they have built, but if you had to something like subscriptions, then Stripe would be the way to go.
In Working with the Stripe Payouts API

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.