#thinkle1_connect-apple-pay

1 messages ¡ Page 1 of 1 (latest)

muted rootBOT
#

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

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

shy spireBOT
feral snow
#

Hello! Perhaps, but it'll depend on your Connect setup and which payment UIs/APIs you're using. Can you give me an outline?

muted rootBOT
#

thinkle1_connect-apple-pay

teal basalt
#

I'm creating PaymentIntent on the BE side with specifying the connected account. Then FE confirms the created intent via client secret on UI

feral snow
#

Can you share an example Payment Intent you've created?

teal basalt
# 
{
  "object": {
    "id": "pi_3P3GE2FotBnGWKfX0MrrPo8W",
    "object": "payment_intent",
    "amount": 1000,
    "amount_capturable": 0,
    "amount_details": {
      "tip": {
      }
    },
    "amount_received": 1000,
    "application": "ca_P0Qj6a5mVaqvY3zbVkQBfBRACJg0qT91",
    "application_fee_amount": 38,
    "automatic_payment_methods": {
      "allow_redirects": "always",
      "enabled": true
    },
    "canceled_at": null,
    "cancellation_reason": null,
    "capture_method": "automatic",
    "client_secret": "pi_3P3GE2FotBnGWKfX0MrrPo8W_secret_1sJOxC0TBpg7NsqqWPhmIcX4p",
    "confirmation_method": "automatic",
    "created": 1712575138,
    "currency": "usd",
    "customer": null,
    "description": null,
    "invoice": null,
    "last_payment_error": null,
    "latest_charge": "ch_3P3GE2FotBnGWKfX0hMpFKzk",
    "livemode": false,
    "metadata": {
    },
    "next_action": null,
    "on_behalf_of": null,
    "payment_method": "pm_1P3GE1FotBnGWKfXxyShdTeD",
    "payment_method_configuration_details": {
      "id": "pmc_1Op6FfFotBnGWKfXPEaKylsD",
      "parent": "pmc_1Op69pFk0feHy2l0gV8ShITV"
    },
    "payment_method_options": {
      "card": {
        "installments": null,
        "mandate_options": null,
        "network": null,
        "request_three_d_secure": "automatic"
      },
      "link": {
        "persistent_token": null
      }
    },
    "payment_method_types": [
      "card",
      "link"
    ],
    "processing": null,
    "receipt_email": null,
    "review": null,
    "setup_future_usage": null,
    "shipping": null,
    "source": null,
    "statement_descriptor": null,
    "statement_descriptor_suffix": null,
    "status": "succeeded",
    "transfer_data": null,
    "transfer_group": null
  }
}
#

this is not Apple Pay, regular card

feral snow
teal basalt
#

If I have multiple connected accounts - should I register for every account?

feral snow
#

Yes, you'll need to

shy spireBOT
teal basalt
#

@feral snow ok, ty. So I basically could do that via API using docs you've sent me right after I create NPO with connected account on the backend side. Right?

jovial adder
#

sure, usually I would say to include registering your intended payment domains on new connected accounts as part of the process you run when creating/connecting the account.

teal basalt
#

I'd like to confirm that no UI efforts should be made on Stripe Connected Account side. Everything could be done programmatically. Is that correct?

jovial adder
#

correct