#ReneRich

1 messages ยท Page 1 of 1 (latest)

chrome widgetBOT
lusty socket
#

Hello ๐Ÿ‘‹
Can you share the example subscription ID?

outer relic
#

This is one of the sample stripe subscriptions being created: sub_1NIBngC0mpF9SEQY5hoVpyyz

#

๐Ÿ‘‹ Hello

vagrant summit
#

HI ๐Ÿ‘‹

#

Sorry for the delay

outer relic
#

Hmm, the email address of the stripe customer does not match the email address of our platform user; might this cause this issue? My test customer has changed his/her email address. however the stripe customer has not yet been updated.

vagrant summit
#

That would cause an issue if the Customer ID does not match the Customer to whom the Payment Method has been assigned.

outer relic
#

I can update the user's email address and try again; see if that changes things.

#

This is a subscription ID that I created, with the correct email address; It still does not automatically complete the payment intent: sub_1NIDEJC0mpF9SEQYXGz7fIx1

vagrant summit
#

The payment was successful

outer relic
#

Yes, because my frontend is confirming the payment intent at the moment. I can set it up that it no longer does that.

vagrant summit
#

The Susbcription enters a status of Incomplete

#

Since the payment method requires confirmation. Can you share the request where you create the Payment Method?

outer relic
#

I am not sure what you mean. I create a setupIntent, and then use the client secret to confirm the ideal setup. which of these payloads would you like ?

vagrant summit
#

The request when you create the setup intent.

outer relic
#

This is the payload I send through the stripe php api:

    "payment_method_types": [
        "ideal"
    ],
    "customer": "cus_NcCYxiXkbuVR7Z",
    "usage": "off_session",
    "metadata": {
        "user_id": 3,
        "payment_method_type": "ideal"
    }
}  
vagrant summit
#

Right but when you confirm the request the Setup Intent is still in a status of requires_action

outer relic
#

o...

vagrant summit
#

This needs another authentication step to be performed before it can be used

outer relic
#

Oke, thought i was done. so that would be handleCardAction then?

vagrant summit
#

Yes

outer relic
#

When I click on confirm in the stripe setup; it does succeed through the webhook asynchronously; this is not in the log however

vagrant summit
outer relic
#

Yes, thats the one

vagrant summit
#

Can you try not passing the usage parameter and see how it behaves?

outer relic
#

This is the subscription created with the payment method created with setupintent payload:

  "customer": "cus_NcCYxiXkbuVR7Z",
  "metadata": {
    "user_id": "3",
    "payment_method_type": "ideal"
  },
  "payment_method_types": {
    "0": "ideal"
  }
}

The subscription ID that was created:
sub_1NIDpnC0mpF9SEQY99jJmNTd

vagrant summit
#

That link doesn't help me since it's your dashboard, not mine

outer relic
#

I have just created a new customer, in a private browser and followed the same steps;
Created a subscription sub_1NIDwqC0mpF9SEQYckzIPDLg with an initially failed payment intent.

#

I do create a subscription that only lasts until september; does backdating perhaps cause confirmation requirements?

{
  "description": "Samui Super Moto",
  "cancel_at_period_end": "false",
  "metadata": {
    "auto_renew": "true",
    "subscription_id": "38",
    "user_id": "20",
    "facility_id": "1"
  },
  "default_payment_method": "pm_***",
  "items": {
    "0": {
      "quantity": "1",
      "price": "price_***"
    }
  },
  "collection_method": "charge_automatically",
  "application_fee_percent": "5",
  "backdate_start_date": "1661990400",
  "transfer_data": {
    "destination": "acct_***"
  },
  "customer": "cus_***",
  "off_session": "true",
  "proration_behavior": "create_prorations",
  "billing_cycle_anchor": "1693526400",
  "on_behalf_of": "acct_***",
  "expand": {
    "0": "latest_invoice.payment_intent"
  }
}

Im not sure if i can safely post any test* object id's here..

vagrant summit
#

Object IDs are only useful to yourself and Stripe staff.

#

Once againt the invoice is in a state of requires confirmation

outer relic
#

Yes, sorry; my initial question was related to this initial charge not automatically being charged to the customer.
I expected the setup intent confirmation allowing me to charge the customer without requiring the customer to confirm the payment intent. However that fails.

#

I am not sure where to continue with this. Does it usually happen that sepa_debit requires confirmation after just been setup?

vagrant summit
#

I am confused as well. Can you write in to Support https://support.stripe.com/?contact=true with some example objects and request IDs. That way we can try to reproduce the error you are seeing and provide advice on how to avoid it. This is looking more complex than something I can easily debug here.

outer relic
#

Oke, I will do that. Thanks so much for your time trying to debug this issue.
I will try again tomorrow with a simpeler use-case.

chrome widgetBOT
vagrant summit
#

Okay happy to help. Sometimes we just need to spend time reproducing the error exactly then figuring out how to fix it. That takes some focused work so a live chat server isn't the best place to get that kind of help

outer relic
#

๐Ÿ™‚

#

I love the 1-on-1 though. Thanks again.
Should i do anything to close this thread?

vagrant summit
#

Just let us know when you write in to Support so we can check for the message

outer relic
#

Oke I will report the follow-up

vagrant summit
#

Wait a sec

outer relic
#

im still here

vagrant summit
#

Looking at the PM creation. This was not done with on_behalf_of

#

So the mandate is assigned to the wrong merchant

outer relic
#

hmm

vagrant summit
#

Can you try creating the Setup Intent with on_behalf_of?

outer relic
#

let me try that

#

Thats it!

#

sub_1NIEatC0mpF9SEQYs2x8Kh4t Created with automated payment

plucky leaf
#

snufkin had to head out, but I'm glad you got it working!

outer relic
#

Great! Im happy for the last-minute save ๐Ÿ™‚

outer relic
#

Alright. well. Im happy. Bye I guess?

plucky leaf
#

๐Ÿ™‚ if anything else comes up just let us know ๐Ÿ‘