#josh-issuing-balance

1 messages · Page 1 of 1 (latest)

crimson harborBOT
fervent musk
#

Trying to pay out acct_1LEELh2Hw1Q3MX72 with this request is the one that fails: req_hSHsl6EMX2f3rF

wanton pendant
#

Hello 👋
Looking..

#

huh interesting, the account seems to have enough balance.
Can you try something for me? What exactly do you see if you try to retrieve the balance using /v1/balance endpoint?

fervent musk
#

One moment

#

Also note i just started using issuing this week, this is the only connected account with issuing enabled, and is 1/140 that payouts are now failing for

wanton pendant
#

Gotcha

fervent musk
# 
{
   "object":"balance",
   "available":[
      {
         "amount":4326933,
         "currency":"usd",
         "source_types":{
            "bank_account":194111,
            "card":4132822
         }
      }
   ],
   "instant_available":[
      {
         "amount":4376738,
         "currency":"usd",
         "source_types":{
            "bank_account":194111,
            "card":4182627
         }
      }
   ],
   "issuing":{
      "available":[
         {
            "amount":0,
            "currency":"usd"
         }
      ]
   },
   "livemode":true,
   "pending":[
      {
         "amount":49805,
         "currency":"usd",
         "source_types":{
            "bank_account":0,
            "card":49805
         }
      }
   ]
}
#

I can try initiating a payout again for that amount if you'd like, it will likely just error with that amount instead of the amount from last night though

wanton pendant
#

Can you try setting source_type to card and see if that fixes it?

fervent musk
#

Should the payout amount be 4132822 or 4326933?

#

with source_type: 'card'

wanton pendant
#

I believe it needs to be equal or less than the balance available for card
so 4132822 or less

fervent musk
#

The issue is that we have a custom integration and match payments in our DB to stripe payments so doing anything that isnt the exact balance is going to mess us up

#

This has never been a problem or happened before until issuing was enabled which is why I'm on support atm

#

We're like 1000+ payouts into this integration

wanton pendant
#

Ah gotcha. Hmm, I wasn't aware that enabling issuing affected payouts.

fervent musk
#

I wasn't either

#

I think its a bug

#

Again this is the only account with issuing enabled out of 140+, never had an issue with payouts until I enabled issuing

wanton pendant
#

Let me check with a colleague

fervent musk
#

thank you

wanton pendant
#

I can try initiating a payout again for that amount if you'd like, it will likely just error with that amount instead of the amount from last night though
In the meantime, can you re-try the payout with available balance amount?

#

without the source_type

fervent musk
#

ya one sec

#

req_NFQ6EFUGUCzCtd

#

same thing

#

with new balance

tame hull
#

josh-issuing-balance

#

I'm taking over, looking

#

you still passed the old full amount and without source_type

fervent musk
#

thats what @wanton pendant asked me to do

tame hull
#

Really you have 2 balances here, the bank_account one for all old ACH payments, and one for card with all the other payments (including card)
You can't pay out the sum of the two, you have to pay out the 2 separately

fervent musk
#

by old ACH payments you mean ACH v1?

tame hull
#

yes

fervent musk
#

how is that possible if the connected account was made june 24

tame hull
#

I looked at the balance.available Events in that connected account and you only had a card balance until Dec 28

fervent musk
#

ACH v2 came out in ~jan/fed

#

feb

tame hull
#

that's not really relevant

#

whether to use ACH v1 or v2 is based on your own integration

fervent musk
#

can you tell me the customer ID with an ACH v1 payment method?

#

we had a full ach v1 integration, swapped the entire thing to ach v2 during beta

#

for this exact purpose

#

we were one of the first live mode customers of ach v2

#

and havent had a single v1 payment since then so i would like to email that customer

tame hull
#

you should be able to figure this out on your end, I can't share this information here

#

Look at all your ACH payments with that account as the destination

fervent musk
#

okay

#

thanks

#

Is there a way to disable ach v1 banks

#

are those created as sources instead of PM?

tame hull
#

no

#

it's all about your integration, it's not something you "disable"

fervent musk
#

our integration doesn't create ach v1 banks anymore, someone must have a year old version of the app. Which is why im wondering if one is sources

tame hull
#

this is a request in your own platform account with that account as the destination. You created a Charge via /v1/charges this is legacy/ACHv1

fervent musk
#

Ok so charges is the route i should delete

#

thank you

#

We use payment intents for 30,999/31k tx, but thank you for the log

tame hull
#

it's not just the /v1/charge, it's the way you use PaymentIntent too

#

if you pass source: 'ba_123' for example on PI confirmation it's also ACHv1

#

you have to make sure to pass payment_method: 'ba_123' on confirmation for old/legacy BankAccount objects, to use ACHv2
Or move to PaymentMethod objects pm_123 for good

fervent musk
#

Yeah we did do that, i think that user has a really old version of the app

tame hull
#

gotcha so yeah in that case you need to track the separate balances in that case

fervent musk
#

thanks