Ability to test bank account debit transitions

[shlomozippel]

At the moment we are able to test debits that get a status during creation (paid, failed, pending) using the test bank account numbers. Unfortunately, we have no way to test an async transition from pending to paid/failed. Ideally we'd like to be able to trigger a status change for a pending test debit and consume an event for that change.

[kurioscreative]

+1

@shlomozippel How are you testing the status during creation? I've only received the "succeeded" status on a bank account debit.

[shlomozippel]

There are test bank accounts that automatically succeed, fail, or remain pending: https://docs.balancedpayments.com/current/overview.html?language=bash#test-bank-account-numbers

[jonez734]

In my testing, the bank accounts always showed paid. They would never "transistion" from pending to failed or whatever.

I have an idea for resolving this, and it involves a mod to the dashboard where I am allowed to set the state/status of any transaction and have my webhook(s) fired.

[mjallday]

👍 on this issue. I cannot test bank account debits. e.g.

1. Create a bank account that has pending transactions according to the docs.

   curl https://api.balancedpayments.com/bank_accounts      -H "Accept: application/vnd.api+json;revision=1.1"      -u ak-test-1PPfI4CmXSaOHFgIYzWdA5fpdkYe9mvLL:      -d "routing_number=121000358"      -d "account_type=checking"      -d "name=Johann Bernoulli"      -d "account_number=9900000001"
   

2. Verify bank account (not shown for brevity)

3. Debit bank account

   curl https://api.balancedpayments.com/bank_accounts/BA7M24Ka1z1agCPjus6O0Qkh/debits      -H "Accept: application/vnd.api+json;revision=1.1"      -u ak-test-1PPfI4CmXSaOHFgIYzWdA5fpdkYe9mvLL:      -d "appears_on_statement_as=Statement text"      -d "amount=5000"      -d "description=Some descriptive text for the debit in the dashboard"
   

   {
   "debits": [
     {
       "status": "succeeded",
       "description": "Some descriptive text for the debit in the dashboard",
       "links": {
         "customer": null,
         "source": "BA7M24Ka1z1agCPjus6O0Qkh",
         "order": null,
         "dispute": null
       },
       "updated_at": "2014-04-24T00:48:56.953208Z",
       "created_at": "2014-04-24T00:48:56.688716Z",
       "transaction_number": "W501-753-1933",
       "failure_reason": null,
       "currency": "USD",
       "amount": 5000,
       "failure_reason_code": null,
       "meta": {},
       "href": "/debits/WD1Gkl1rndj2QsfLIkZvs7r3",
       "appears_on_statement_as": "BAL*Statement text",
       "id": "WD1Gkl1rndj2QsfLIkZvs7r3"
     }
   ],
   "links": {
     "debits.customer": "/customers/{debits.customer}",
     "debits.dispute": "/disputes/{debits.dispute}",
     "debits.source": "/resources/{debits.source}",
     "debits.order": "/orders/{debits.order}",
     "debits.refunds": "/debits/{debits.id}/refunds",
     "debits.events": "/debits/{debits.id}/events"
   }
   }

This is impacting the ability of the front end team to test operations on transactions in certain statuses. e.g. balanced/balanced-dashboard#1186

[mjallday]

I believe that the issue is that we're not configuring the PENDING_BANK_ACCOUNT_HASHES values in precog. I just checked the cookbook that configures these values and it's being set to an empty list. This should be an easy fix. https://github.com/balanced-cookbooks/precog/blob/master/attributes/default.rb#L101

[steveklabnik]

That would be amazing because this has been broken for an embarrassing amount of time. 😬