Creating a payment takes up to 3s on average

[zealoushacker]

Creating an account with a card uri and creating a hold takes up to 3s on average:

External Net::HTTP[api.balancedpayments.com]: POST 53.3% 2.7 calls 3,356 ms

While we understand the nature of the roundtrip that occurs, this doesn't make it any easier. When we load the overhead of our own request processing, we sometimes find ourselves taking 4s to process payments.

Obviously processing a payment is a very high touchpoint in the app. We are experiencing transaction fairly rapid txn volume growth. This poses a good problem to have, but a problem nonetheless.

We have a couple of options:

1. implement some sort of delayed job/queued solution.
2. count on balanced for this.

I am guessing that you guys queue payment processing on your end as well.

My question is this:
Would you guys consider implementing a callback/web hook based interface to notify systems that initiate holds of the success or failure of the creation of a hold?

If this is already in the works, please let us know so that we don't spend a bunch of engineering resources working on one ourselves =)

[mjallday]

Webhooks / Push notifications is something that's been proposed (#70) but has yet to be prioritised, please "+1" or add your comments.