Back
Similar todos
Using Stripe payment link. Users signup with one e-mail and purchase on stripe with another one. Fixing it now calling checkout.session.completed and getting client_reference_id. #fms
save stripe customer id to database #tweetphoto
Before creating a Stripe session, create a Stripe customer and attach user ID as meta #domainwatchman
save stripe_customer_id in users.db for later payments and auto top up #remoteworkers
Pass the customer's email address and Id to the Stripe payment link #domainwatchman
Add email address + user id to existing Stripe Customers #startupjobs
save ?ref= (referrer) and ?via= (affiliate) in remarketing_emails.db to then transport them to users.db to track where paid users come from because Stripe makes it hard to track that metadata with the Stripe Pricing Table (Rewardful already uses client-reference-id and there is no space more to send metadata) #photoai
save stripe account ID to charges #startupjobs
add stripe customer/subscription ids for existing customers #tweetphoto
Handle existing user Stripe customers and don't create new customer id unless necessary #brandtools
programmatically create stripe customer id in partner account
save stripe account id with charge #wip
#sheet2site connect stripe to customer
signup listener that creates stripe customer #shipr
put job post ID in Session object as client_reference_id so it’s returned on webhook to match job id in case of a race condition where customers click Pay, and then different checkout_session_id sessions are created, and they pay one of them #remoteok