#mas-usequeuecom_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/1355223413307736185
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mas-usequeuecom_api, 22 hours ago, 18 messages
Image for referece for payment method. We had to manually turn the BACs direct deposit on. Is there a way to automatically sync them or an api endpoint that lets the customer enable it from our platform?
Hi! What kind of Stripe Accounts are you using?
Ahh, ok. There's no API-based way to affect their accounts at all.
How are you creating charges? Presumably destination charges since you talk about creating sessions on your Platform?
We're creating checkout sessions through embedded. afaik i don't think we're doing destination charges since it goes directly to their stripe account when a payment is created.
Stripe::Checkout::Session.create({
ui_mode: 'embedded',
Can you share the whole API call there?
session = Stripe::Checkout::Session.create({
ui_mode: 'embedded',
line_items: extracted_data,
custom_fields: [
{
key: 'company',
label: {
type: 'custom',
custom: 'Company name',
},
type: 'text',
},
],
mode: mode,
payment_method_collection: @service.disable_payment_method_collection ? 'if_required' : 'always',
discounts: [{ coupon: coupon }],
customer: customer,
automatic_tax: @organization.stripe_account.automatic_tax.present? ? {enabled: true} : nil,
tax_id_collection: {enabled: @organization.stripe_account.tax_collection.present?},
billing_address_collection: @organization.stripe_account.billing_address_collection ? 'required' : 'auto',
subscription_data: {
application_fee_percent: application_fee,
trial_end: trial_end_date_seconds
},
return_url: "#{params[:domain]}/stripe/checkout_successful?session_id={CHECKOUT_SESSION_ID}&organization_id=#{@organization.token}&service_id=#{params[:service_id]}&service_price=#{params[:chosenPrice]["id"]}&project_service_checkout_id=#{params[:project_service_checkout_id]}&coupon=#{coupon}&referral_code=#{params[:referralCode]}"
})
Do you make that API call with a Stripe-Account ID then?
I use their access token.
@organization = Organization.find_by(token: params[:organization_id])
Stripe.api_key = @organization.stripe_account.access_token
Hi, taking over as my teammate needs to step away. Let me catch up.
We talke about this here: https://docs.stripe.com/connect/dynamic-payment-methods
If you can set it for your Connected Accounts here: https://docs.stripe.com/connect/payment-method-configurations#section-2
Then, when you create the CheckoutSession, https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_method_configuration you can pass that configuration
Got it thank you!