#unibit-pending-balance

1 messages · Page 1 of 1 (latest)

fiery widget
#

Hi 👋 this is because even after a successful transaction, there is a settlement time where the funds are actually moving. Until that completes the funds are stored in your pending balance rather than your available balance. This simulates real-world timing scenarios better, but can make it more challenging to test flows such as payouts.
So we've included two test cards (the first two in this section) that when used skip the pending balance stage:
https://stripe.com/docs/testing#cards-responses

Learn about the different methods to test your integration before going live.

midnight oak
#

is it a real world scenario? cause if its true we have a prob

#

some of these transactions were made 2 months ago🙂

fiery widget
#

Well that sounds very different. Can you tell me more about your integration?

midnight oak
#

what you want to know?

#

we are using stripe.js

fiery widget
#

Are you also working with Payment Intents?

midnight oak
#

we are using checkout.js

#

no we are not using intents

#

check this id please

#

po_1KLHLGLoffM3pbuK7fnpAeQG

#

it was posted 2 months ago

fiery widget
#

Okay, so you're using our Legacy Checkout integration. I'm a bit confused though because that object you linked is a payout (rather than a payment) and it appears to be in a paid state.

midnight oak
#

now am confused too

#

this is a credit card payment, isnt it ?

fiery widget
#

No, that's a payout from a Stripe balance to a bank account.

midnight oak
#

😫

#

we are totaly lost

#

where is your credit card integration?

fiery widget
#

I'm not sure what you mean.

midnight oak
#

we need our client to pay using his credit card and the funds to be transfered on our stripe account, so simple

fiery widget
#

Do you already have a functioning integration built on checkout.js, or are you still in the process of building an integration?

midnight oak
#

we alredy have checkout.js integration

fiery widget
#

Sorry, I'm really struggling to understand what you're looking for. Let's take a step back. You said you have successful payments but that you're not seeing your balance increase. Is that payout that you linked from your account?

midnight oak
#

sorry, but we totaly confused

#

on your reference help you are saying

#

Checkout

Stripe Checkout is the quickest way to start accepting payments on Stripe. Send your customers to pay on Stripe’s conversion-optimized page instead of building your own.

#

isnt that correct ?

fiery widget
#

Yes, Checkout is a great option, but that is our new Checkout flow that's being discussed there. Checkout.js is our legacy checkout experience.

#

Is that payout that you provided the ID for from your account?

midnight oak
#

we are using legacy checkout

fiery widget
#

When you log into the Stripe dashboard, do you see any payments listed on the Payments page?

midnight oak
#

yes

fiery widget
#

In the top right of the page, is the Test Mode toggle on?

midnight oak
#

but our balance is empty

#

yes

fiery widget
#

Your account is set up to receive automatic payouts daily, so funds won't sit in your balance for very long.

midnight oak
#

we are still confused sir

#

these are not payouts

fiery widget
#

There are, you linked me one earlier.

midnight oak
#

are payments from our clients credit card

fiery widget
#

I'm not seeing any real transactions on the account. They're all test payments using test card numbers.

midnight oak
#

of course, these are all test payments

#

anyway, this is what we want to achive

#

we need our client to pay using his credit card and the funds to be transfered on our stripe account, is that possible ?

fiery widget
#

Yes, and as it sounds like this integration hasn't gone live yet, I strongly recommend that you don't use checkout.js. Instead I would recommend that you use the new Checkout experience:
https://stripe.com/docs/payments/accept-a-payment?integration=checkout

If you're looking for a no-code approach instead, then I'd recommend that you look at our Payment Links:
https://stripe.com/docs/payments/payment-links

Securely accept payments online.

Create a custom payment page with the Dashboard and share a link to it.

midnight oak
#

i dont see any difference from what what we are currently have, why should we change it ?

fiery widget
#

If you're using checkout.js, then the above approaches are different, and as I'm seeing Charge objects for payments rather than Payment Intent objects you do appear to be using the legacy approach.

midnight oak
#

this is what we are using

fiery widget
#

So yes, that is the legacy checkout experience, and rather than going live with it I recommend that you look at one of the other options that I provided. The most recent link is actually a migration guide intended to help move from Legacy Checkout to the new Checkout experience.

#

If you're selling a small set of products, then I'd strongly recommend Payment Links. They're the easiest integration path and require no coding. If you need more flexibility then the new version of Checkout will likely be a better fit.

midnight oak
#

yes but our problem is that do not have an MVC environment we need to use a client javascript as per our example

fiery widget
#

That doesn't seem like it would be an obstacle, can you help me understand how that's blocking your integration progress?

midnight oak
#

if we keep the system as it is using legacy checkout, will this be a problem ?

fiery widget
#

This conversation seemed to start because you didn't your integration was working, so I don't think keeping it the way it is would be a good idea. Additionally legacy checkout doesn't support 3DS authorizations, or wallet payment methods.

midnight oak
#

our integration is working and its based on your specs, now accidentally we realize that your system confuses card payments with payouts, so this is not our issue

fiery widget
#

We really don't recommend that Checkout.js be used for new integrations, but ultimately the choice is yours. If you can provide more specifics on the behavior you're seeing that you don't understand, then I can try to provide clarity on that.

midnight oak
#

if you go to our account you will very clear see the iisue

#

all these payments are done using legacy payment system and are recorded on your dashboard as payouts!!!!!!!!!

#

payouts from which account????

fiery widget
#

No, you're using a legacy approach so your integration is creating Charge objects (prefix ch_), and these are displayed on the Payments page:
https://dashboard.stripe.com/test/payments

Payouts are the objects that represent money being moved from your Stripe balance to your associated bank account (but this is all in test mode so money is actually moving) and are shown on the Payouts page:
https://dashboard.stripe.com/test/payouts

midnight oak
#

ok i understand now

#

is it possible the funds to stay to my stripe account and not move to my bank account ?

fiery widget
#

Yes it is, you can transition your account to use manual payouts where you're able to control when payouts occur.
On the payouts page, you click on "More" (near the top right) -> "Configure payouts"
Here you can either adjust your payout schedule or toggle your account to manual payouts.

midnight oak
#

now another question

#

if i want to move funds from my account to another connected account, the funds must be on my stripe account or in my bank account or doesnt matter ?

fiery widget
#

For Connect scenarios, when creating a Transfer from your Platform Account to a Connected Account, the funds for that Transfer need to be in your available Stripe balance.

midnight oak
#

i could not found "Configure payouts" on my dashboard

fiery widget
midnight oak
#

if i set it on manual that means i will not be able to do payouts to my connected accounts?