#ruul_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/1243547309116227696
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Yeah that email you screenshotted links official, recommended integrations
Like this one for example: https://docs.stripe.com/payments/accept-a-payment
You don't have to use checkout
Click custom flow at the top
There's multiple options
under which section I can see it
Click custom flow at the top
yeah
I'm not sure if it's going to work out for us
we save payment details then use it to switch between different plans
doesn't payment intent work for a single time ?
Yeah but you can also pass setup_future_usage to save the payment method so you can use it again
If you don't need to charge the card when collecting it, you can use setupintent instead: https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=elements
using card details on api we create payment methods & save it on customer
Yep that's not allowed unless you get it enabled on your account and prove you're pci compliant
You don't need to pass raw card details to do that though...
See the link i shared above
* Creates a PaymentMethod
* @param card card details
* @returns PaymentMethod object
*/
public async createPaymentMethod(
card: Stripe.PaymentMethodCreateParams.Card1,
metadata?: Stripe.MetadataParam
): Promise<Stripe.PaymentMethod> {
return this.stripe.paymentMethods.create({
type: "card",
card,
...(metadata && { metadata }),
});
}
so this is not allowed?
The issue is you're passing a raw card number to us via the api, which isn't allowed, per that email you received
I'm trying to see if we can solve it from api side
but doesn't seem like it'll work out that way
right?