riddlic_api

[inner nova]

👋 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/1229790294430716015

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[glass arrow]

Or, can a virtual card be created on our front end that's entered into this 3rd party POS system and then multiple forms of payment be stored on Stripe's platform and be cycled through when the from of payment tied to the virtual cc fails etc

basically I want to allow users to have multiple forms of payment on file despite this car wash pos system only allowing 1, thus increasing their decline rate

[merry vortex]

Hi there 👋 I can't comment on what the third-party POS system does or doesn't support.

From the Stripe side, you won't be able to access the raw card details if you use Stripe to store Payment Methods for your customers. So you wouldn't be able to pass those on to other systems.

Creating virtual cards would be part of a Stripe Issuing flow:
https://docs.stripe.com/issuing
But I'm not sure you're after some that large.

[glass arrow]

some of our car wash clients have 400k subscribers

and we are building a better app / web experience for them but they all use this really bad POS system called DRB (that has an API)

but DRB itself only allows 1 card # on file at a time

can a virtual card be created, stored on DRB, but then on Stripe's end like 3 forms of payment me tied to that 1 virtual cc

so we 3x the chances of succesful monthly transactions per subscriber?

when 1 method fails?

[merry vortex]

I'm skimming because Issuing isn't something I'm as familiar with, but it doesn't look like it comes with prebuilt flows for collecting funds to offset payments made with those cards.

I believe you would need to plumb all of that.

[glass arrow]

ok, and to be clear (and thank you for your help)

Im wondering if I can create 1 virtual card id:browse but tie multiple forms of payment to it

in case 1 fails

[merry vortex]

Also if you start handling raw card details on behalf of your customers, you'll want to make sure your flow and systems are PCI compliant. (Also something I don't know much about other than knowing it's a concern when handling raw card details).

[glass arrow]

right, well we would only ingest them via stripe

not store raw cc data

ok, I guess I'll read the issuing docs

[merry vortex]

I believe you could build that logic. Allow your customers to pay you multiple ways, and then allow them to make payments with the card that you issued them.