#noro0x01
gray ibex
hollow inlet
Could you elaborate a bit more on the flow? Just click on US bank and tap con add details manually?
Do you have a test URL?
fickle ivy
Unfortunately I don't have a test URL for you to interact with.
The flow is if the user clicks on update payment method ("Change" in SS) button they gets redirected to stripe checkout session in setup mode.
hollow inlet
Yes, and can you paste the redirected URL here?
fickle ivy
There they can either use credit cards or ACH Direct Debit as a Payment Method. When I try to use ACH and use first tile (test institution)
Here you go
When user completes the flow, they can redirected back to app and a post request is made to update their payment method. But incase of Enter bank details manually instead (takes 1-2 business days) paymentMethod id not verified, hence it can not be attached to the customer.
Can we have them verify their payment method while they are being on stripe checkout page?
if not, then can you shed some light on how to swap their payment method once they verify their micro-deposit?
hollow inlet
Okie when adding manually, did they use the testing number here? https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=checkout#test-account-numbers
fickle ivy
yes, the first one
hollow inlet
I succeeded added it
fickle ivy
when they click on start setup, it creates a setupintent where I can see the payment Method ID. Which I then use it to attach it to customer, but while attaching that newly received paymentMethodId, it throws an error as shown in ss
hollow inlet
Okie, on the SetupIntent, does it give you a next_action block?
Can you paste the SetupIntent object here?
fickle ivy
yesss
setupIntent {
id: 'seti_1OHgMDK4Am3IWL1tOXelTqnJ',
object: 'setup_intent',
application: null,
automatic_payment_methods: null,
cancellation_reason: null,
client_secret: 'seti_1OHgMDK4Am3IWL1tOXelTqnJ_secret_P5s6uJFqt058UnLAqeWx8f7jPv09X3q',
created: 1701235845,
customer: 'cus_Ovp378PdBpb6zj',
description: null,
flow_directions: null,
last_setup_error: null,
latest_attempt: 'setatt_1OHgMjK4Am3IWL1tDNGD79Hb',
livemode: false,
mandate: 'mandate_1OHgMjK4Am3IWL1te3JWcIgU',
metadata: { customer_id: 'cus_Ovp378PdBpb6zj' },
next_action: {
type: 'verify_with_microdeposits',
verify_with_microdeposits: {
arrival_date: 1701331200,
hosted_verification_url: 'https://payments.stripe.com/microdeposit/sacs_test_YWNjdF8xTHgybUtLNEFtM0lXTDF0LHNhX25vbmNlX1A1czZIanB3dmpvVngzdFViVE9jaFl1ZDlZTndUWGE00009yHts5ch',
microdeposit_type: 'descriptor_code'
}
},
on_behalf_of: null,
payment_method: 'pm_1OHgMiK4Am3IWL1tiIg7FAZg',
payment_method_configuration_details: null,
payment_method_options: {
card: {
mandate_options: null,
network: null,
request_three_d_secure: 'automatic'
},
us_bank_account: {
financial_connections: [Object],
verification_method: 'automatic'
}
},
payment_method_types: [ 'card', 'us_bank_account' ],
single_use_mandate: null,
status: 'requires_action',
usage: 'off_session'
}
How does customer received hosted_verficication_url? Does stripe email it to them?
hollow inlet
No you will need to send them somehow
Then they can use these information on the Doc to verify. It's an expected flow
fickle ivy
Does verifying the payment method returns any webhook event? Like how would developers know weather they have verified their payment method and now it can be used