#heenatejwani_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1395057297830449283
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
If I am senging below data then getting lastest_charge null in response but I saw on portal it is available there -
mandate_data[customer_acceptance][type]:online
mandate_data[customer_acceptance][accepted_at]:1751900674
mandate_data[customer_acceptance][online][ip_address]:136.226.230.188
mandate_data[customer_acceptance][online][user_agent]:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
If I am sending only mandate:mandate_1RlW9hL1EaqoB8vx9qq4MnRn in request then getting latest_charge value
May I know why it is happening because I dont have mandate id always
Can you send an example of this so we can compare?
request id (Null latest charge in response )- pi_3RlWnDL1EaqoB8vx17ORW6Cu
request id (with latest charge in response)-
pi_3RlWiqL1EaqoB8vx0yU1akYL
check these above request id
one more thing its happening for GB , for AU its working fine
Can you share the AU requests to compare?
ok
pi_3RlX7sR7qASe9sGe1euGQM8f - with mandate_data
pi_3RlX7ZR7qASe9sGe0Ihn54E1 - with mandate_id
in these both responses I am getting data
Ok my colleague who's more familiar with bank debits said this is expected. latest_charge reflects the charge we send to the network. bacs_debit has a pre-debit notification period. The mandate must be active before sending charge to the network. au_becs_debit doesn't have this
It takes 4 business days to confirm the success or failure of a Bacs Direct Debit payment when a mandate is already in place and 7 business days when you must collect a new mandate.
You created a test charge, so you didn't need to wait 4-7 days
But the same logic applies
When you pass mandate_data, you're creating a new mandate
We wait for mandate to be active before sending charge to the network
but if I am immediately fetching same payment intent then in response I am getting latest charge and it is available on stripe portal
You wouldn't see it if fetching immediately
It's populated about 20 seconds later
In test mode
Because that's when mandate became active
Actually less than 20 seconds
Looking at logs it's only a few seconds
But it only is populated once mandate becomes active
And the charge is submitted
Why this is not happening in AU , can you make me undersatnd ?
You can see timing of au_becs_debit documented here: https://docs.stripe.com/payments/au-becs-debit#timing
Payment is submitted immediately at T+0
Whereas with bacs_debit you have to wait until t+3 if creating a new mandate: https://docs.stripe.com/payments/payment-methods/bacs-debit#timing
but we are activating mandate and submitting payment in same step -
Mandate is active and the payment is submitted
Are we sure this is the reason ?
Is there any other way we can get latest charge for payment intent?
Mandate isn't active though
That's how bacs debit works
There's a waiting period
T+0 Mandate submitted
T+3 Mandate is active and the payment is submitted
T+5 Funds leave the customer’s bank account
T+7 Funds are available in Stripe```
You don't get latest_charge until payment is submitted
Is there any other way we can get latest charge for payment intent?
You can get it, it just won't be available immediately on creation
A charge isn't created until the payment is submitted to the network
ok so in test mode how it works?
It depends which test credentials you use
The one you used it transitions quick
Seconds