#markymark-tokens
1 messages · Page 1 of 1 (latest)
thanks - say we collect users' token include name and card details
for the auth and charge purposes
later on we want to pay back users a lump sum
could we use the same tokens
thinking it as the gambling for the use case
John enter credit card details to pay his $30 bets and later on he wins $3000. instead of asking the cc details again, we want to pack them back to same card
are we able to achieve that?
to clarify, is your business really related to gambling? or is this just an example?
can you provide more detail for your specific use case though? Is this for a cashback or incentive program?
insurance
collect premium later on pay claims
how does that matters from stripe's persepctive tho, is there exemption or workaround given different industries?
the way you originally described it and what i had in mind wasn't really quite linking up i.e. it's not possible. But i think there may be a different way to go about it
it is not possible to use the same token for multi-purpose both inbound and outbound?
Okay thanks
no it's not possible to use the same token for both inbound and outbound for your use case
Could we please get some options how might we able to achieve that?
is your company based in the US?
so the workaround is to consider using Connect [0]. You can invoice your customers, but at the same time also onboard them as connected accounts so that you can pay claims to your customers via their bank account / debit card
the reason why i ask if your company is based in the US is because there could be feature limitations based on the country
i see thanks
We are based in Australia while i think Stripe connect still applicable for this
are your customers all expected to be based in Australia as well?