#ebad_docs

1 messages · Page 1 of 1 (latest)

sly oarBOT
#

đź‘‹ 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/1461031992035639317

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

median silo
#

Hi there

#

Can you link the online feature you are using that you need in offline?

#

Just so I'm clear on what it is that you are doing

past eagle
median silo
#

No we don't do calls

#

This is a public discord server

#

That's the same link as before

#

I just need you to link the online feature that you are using

#

I don't fully understand what you're currently doing in online mode

past eagle
#

ok so here is the steps
What the app does in ONLINE mode

Connects to backend on app launch

Fetches:
Organization details
Fundraisers / Causes
Configuration (fees, recurring rules, cover fee, etc.)
Creates PaymentIntent in real time

Card reader:
Connected live (Bluetooth / USB)
Processes payments instantly

Transactions:
Approved/declined immediately
Receipt sent instantly (email/SMS if enabled)
Dashboard & reports update in real time

but in offline mode we cannot get the connection token on runtime so what is the best way to get a connection token because I have multiple accounts in one screen user can select any one and on selection we need to do the transaction offline

#

the connected accounts are being saved locally

sly oarBOT
past eagle
#

what we need to achieve is to do an offline payment without any delay. what we are doing is

  1. stored all the connected accounts i.e let say we have accounts of zakat, sadaqah and construction if user selects any of them we get the stripeConnectedAccountId and locationId on behalf of that particular account and get the connection token. (it is online)

  2. but on offline what to do for smooth transaction? like connect a card reader with every connnected account one by one and save the paymentIntents for offline transactions?

distant trail
#

hello! fyi i'm taking over for codename duchess - fyi this is a bit of an edge case for me as i'm a little less familiar with offline payments so i might need to consult with some colleagues

past eagle
#

yes please connect someone who is good at it

distant trail
#

just double checking, are you using direct charges for this use case?

past eagle
#

Yes, We process Terminal payments as direct charges on the connected account (the org/fundraiser account selected), using that account’s location and connection token.

distant trail
#

hmmm i am not seeing a good way to manage getting a new connection token while offline

#

still digging

#

just to make sure i fully understand what you're doing with your current integration, are you essentially presenting a UI that allows someone at a POS to select an account, which then changes the stripe-account header you're sending to your backend?

past eagle
#

Functionally, yes, the selected account changes which connected account we act on — but the client is not swapping Stripe headers. The client sends the selected stripeConnectedAccountId, and the backend performs Stripe calls in that connected-account context.

The KIOSK selection determines the connected account ID we use server-side for Stripe Terminal calls; we don’t change Stripe headers from the client, and webhooks only confirm outcomes.

distant trail
#

hmm even then it looks like the reader just uses the most recent stored configuration for a given location

past eagle
#

We use Location IDs per connected account. Offline mode will work only for Locations that have Offline mode enabled via their Configuration. We’re verifying/enabling that setting on the relevant Locations.

Agreed — the reader uses the latest stored config for its current Location. That’s why, for offline, we plan to keep the device bound to a single connected account/location context while offline and queue/sync when network returns, rather than switching accounts/locations during offline

distant trail
#

ok, that makes sense. so if you're planning to keep it bound to a single connected account, is your question resolved? or do you need more clarification on anything?

past eagle
#

when online, our flow is:

We have multiple connected accounts (e.g., Zakat, Sadaqah, Construction).
The POS selection determines the stripeConnectedAccountId and locationId.
We fetch a connection token online and ensure the reader is ready before payment, so there’s no delay at tap time.

The open question is offline behavior:
Once the device goes offline, we understand we can’t fetch new connection tokens or switch account/location context.
For a smooth offline experience, should the device be pre-bound to a single connected account + location, with offline transactions queued for that account only?
Or is there any supported pattern to prepare for offline by cycling the reader through multiple connected accounts/locations ahead of time (e.g., pre-connecting or pre-creating PaymentIntents), so that offline payments can still be accepted regardless of which account is selected?

distant trail
#

i am not finding a way to pre-load multiple accounts, everything i'm finding suggests that you are bound to the location + account that was in use when the reader went offline. so based on that i would recommend pre-binding

past eagle
#

yes letme clear the question in a bit deeper

What we want to achieve is:

While the device is online, we want to prepare everything needed so that later, if the device goes offline, the operator can select any of those accounts and still collect a card payment with no delay.

Concretely, we’re asking whether we can pre-bind / pre-configure the same device+reader to multiple connected account + location pairs during online time (e.g., “warm them up”), store whatever the SDK/reader returns, and then while offline:

switch between those accounts by selection, and

queue offline transactions under the selected connected account/location,

and sync them once the device comes back online.
Can Stripe Terminal support “offline payments across multiple connected accounts/locations on a single device” if we pre-bind them while online?
Or is offline payments only supported for the single connected account + location that the reader is currently bound to (meaning we must restrict offline payments to one account/location and disable account switching while offline)?

distant trail
#

ok, so i am still pretty sure this isn't possible, but i think i understand the shape of the question well enough to test it out and see if there's maybe a way to do this that our docs aren't capturing properly

#

do you mind if i convert this to an email case and spend some time asyncronously trying to see if i can get this to work?

past eagle
#

yes you can for sure.

sly oarBOT
#

Hello @past eagle, we have sent you a direct message, please check it at https://discord.com/channels/@me/1461060034497609813

  • đź”—The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
distant trail
#

ok! you should get a DM shortly with instructions on how to create a case, feel free to let me know once you've done that

past eagle
#

ok so I have created a ticket with same details I've mentioned to you

sly oarBOT
distant trail
#

yep i've got it! i'll get back to you via email asap