remear | 12 years ago | on: Payments Startup Balanced (YC W11) Is Processing $370M a Year
remear | 12 years ago | on: Stripe adds multiple account support
Balanced employee here.
You're right. That tutorial could be made much more clear. In fact, this guide and others are being extensively rewritten. The example itself is specific to charging a Card. Therefore, the guide assumes you have an existing Customer since Customer creation is a separate topic. You are correct that the card_uri is an example of one that would be obtained from the previous example. Let me clear up how to charge a credit card.
First, the card needs to be tokenized (information sent to Balanced and securely vaulted), https://docs.balancedpayments.com/current/api.html?language=....
Next, either find an existing Customer or create a new one, https://docs.balancedpayments.com/current/api.html?language=....
Now add the Card to the Customer, https://docs.balancedpayments.com/current/api.html?language=....
Lastly, go ahead and create a new debit, https://docs.balancedpayments.com/current/api.html?language=....
A requirement of the current API is that a Card or BankAccount must first be associated to a Customer before it can be used. This is mainly due to the fact that v1.0 of the API is very Customer resource centric, something that's changing in the upcoming 1.1 release. A Customer resource will no longer be required to charge Cards.
If you have any other questions feel free to hop in #balanced on freenode IRC. We love questions!
remear | 13 years ago | on: jQuery.payment
remear | 13 years ago | on: Is Tokaido (rails.app) Dead?
remear | 13 years ago | on: Is Tokaido (rails.app) Dead?
remear | 13 years ago | on: Looking Glass - Full screen web view on any connected display on OS X
Chrome has to be relaunched from time-to-time for updates or system restarts. Users are left up to restoring "Recently Closed" tabs and windows or sizing out the window again. Sometimes users "close all windows", "minimize all" or hide the application without thinking about the one containing the "dashboard" view in the background. These inconveniences become distracting and require users to always be careful to remember that they have that one view they never want to dismiss.
Looking Glass was designed to avoid these issues. It doesn't render your other displays useless when presenting a web view full screen. It's meant to be a set-it-and-forget-it solution. Users can still do their normal work without fear of accidentally closing their "dashboard" view. A major concern of web-baseed kiosk application is that it's easy for people to navigate away from the page because the address bar is easily accessible. In Looking Glass there isn't an address bar immediately available for users to change the desired location. In the future, I imagine Looking Glass will also include a password lock feature so the start page URL cannot be changed by anyone who is not an administrator.
These are the main v1.0 differences between Looking Glass and Chrome's page presentation modes.
remear | 13 years ago | on: JewelryBox v1.3
----------------------------------- Changes in version 1.3: -----------------------------------
Mountain Lion Compatible
Multi-User installation support
Black and white system menu bar icon. Thanks simoc!
Updated RVM URLs
Auto detect options for ruby arch and linking
Expire disk usage meter cache after RVM operations
Switch default ruby from main window
Reduced area header heights
New area icons
Add gemsets
Remove gemsets
Empty gemsets
Copy gemsets
Toggle gemset globalcache
Install gems
Remove gems
Remove old versions of gems
Spawn gem servers
Fixed duplicate first ruby in switch default ruby menu list
Fixed runtime crash on "continue" after RVM install (OS X 10.6)
Fixed crash when attempting to check for RVM update with no available internet connection
-
RVM users, enjoy. rbfu, ry, ruby-switch, and rbenv users, you can go about your business.
-
On a side note, if you're interested in seeing a Linux or Windows version, please ping @remear.
