devparry

[left thicket]

Hi @terse iris could you please help me to fix this

[terse iris]

Taking a look at this!

[left thicket]

thanks

[terse iris]

Okay, I think the issue is with the domain registration as well as the kinds of charges you're using with Connect.

You're using Express connected accounts, but not the recommended destination charges: https://stripe.com/docs/connect/destination-charges

Is there a specific reason for that?

[left thicket]

we are using connect and all the payment will goes under connect account

[terse iris]

Right, we recommend using destination charges with Express accounts. It looks like your team is using direct charges instead.

[left thicket]

same code we use for google pay its working fine and all the payment goes under each and every connect account

[terse iris]

It's a bit different for Apple Pay since the charge flow for your integration determines how your domain should be registered on Stripe.

[left thicket]

before initializing the Stripe Button module in React we first created the payment intent with stripe connect please have a look at the screen-shot :

[terse iris]

So, for Express accounts, the recommendation is to use destination charges. Once you're using destination charges, your Apple Pay domain should be added to your Express account in live mode

Right, so the code above ends up creating a PaymentIntent using direct charges, not destination charges

Here's a quick rundown of different Connect charge types: https://stripe.com/docs/connect/charges#types

[left thicket]

okay...
ReactJs Code

`pr.canMakePayment().then(result => {

if(result.applePay === true ){
// here i have to call payment Intent API with destination charges and that client_payment_intent_secret we will use in next
}

})`

is this is what i have to do now for Apple Pay ?

[weak lake]

Hi, stepping in as roadrunner is away, catching up here

[left thicket]

one thing more I have to ask :

can i use destination charges for ( **payment_intent **) all Google Pay | Web Checkout Using Stripe Elements as well,
instead of the ( direct-charges ) as attached screenshot

This is what I already used to create payment Intent Right now.

[weak lake]

Yes, you can create a destination charge when you create the Payment Intent, https://stripe.com/docs/connect/destination-charges instead. This document talks about how to achieve what you're looking for. Next, you'd want to register the Apple Pay domain on that Express account.

[left thicket]

okay

that can be done from dashboard right ?

[weak lake]

Yes

[left thicket]

for this i have to paid extra or this is free ?

[weak lake]

I do not understand the question here, are you asking if adding Apple Pay incurs additional cost?

[left thicket]

I mean if i use destination-charges instead of direct charges ?

[weak lake]

You'd want to read this section of the document, https://stripe.com/docs/connect/destination-charges#:~:text=Your platform pays the Stripe,is transferred to your account. With destination charges, the Platform pays for Stripe fee and you can set your application_fee_amount on these charges.

[left thicket]

okay thanks for your help @weak lake

let me check this

[left thicket]

Hi @weak lake

Now i am getting this error after creating payment intent using destination-charges under google Pay as well

[weak lake]

You'd want to make sure that you're using the correct API key, are you using the Platform's API key on this request?

[left thicket]

This is what i do in my code

[south loom]

Hi there 👋 taking over for @weak lake

Usually you get the error "no such payment_intent" when you mix up requests sent on behalf of the connect account and requests sent by the platform. Do you know which one the Payment Intent was created on?

Judging by the first screenshot in this thread, it looks like you're probably creating the Payment Intent on behalf of the Connect account. If you want to use Destination charges, then the Payment Intent needs to be created on the Platform's account instead

[left thicket]

I guess on the client end i need to do changes based on Destination charges as well could you please confirm what new param i have to add under this ?

[south loom]

What actions are you performing client-side? For destination charges, you shouldn't need to pass the connect account's API key at all

You should just be able to specify the platform's API key

[left thicket]

platform's API key means ? sorry not getting this

you mean like this ?

const stripePromise = loadStripe(LaptureConstance.STRIPE_KEYS.PUBLIC_KEY );

[south loom]

That looks correct. You shouldn't need to specify an account in this case. Does removing the stripeAccount line work?

[left thicket]

not able to test as I am getting errors not while getting recent payment Intent which the user already create and has not completed yet

[south loom]

What error?

[left thicket]

this one

{
"code":400,
"status":"error",
"message":"Unrecognized request URL (POST: /v1/payment_intents/). If you are trying to list objects, remove the trailing slash. If you are trying to retrieve an object, make sure you passed a valid (non-empty) identifier in your code. Please see https://stripe.com/docs or we can help at https://support.stripe.com/."
}

any idea ?

[south loom]

Do you have a Request ID for that request?

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

[left thicket]

This is the one but it show success no error

[left thicket]

dnt know then why this respose retun by my payment-intent API

do you need request id ?