#Marco Túlio Rocha

1 messages · Page 1 of 1 (latest)

marsh lake
#

hello! Please put your question here

green mulch
#

I need to create a signature with a credit card, where do I associate the credit card?

marsh lake
#

I'm not exactly sure what specific feature or integration you're talking about -can you give more detail? Are you looking at a specific doc or guide?

green mulch
#

Creating Subscriptions.

#

Where do I add my credit card details?

marsh lake
#

That image isn't loading for me (Discord is still flaky), but what integration are you working with? Checkout? Elements? Something else?

green mulch
#

I'm working with the integration.

I've already created product, price and costumer.

Do I need to create the PaymentMethod and associate the credit card?

my doubt and at this stage, the subscription....

marsh lake
green mulch
#

I don't use stripe elements, I have a custom page

#

where do i enter my credit card details

carmine hearth
#

You're collecting card details without using elements?

marsh lake
carmine hearth
#

Please review the information karbi shared above

#

In order to do this you'll need to reach out to our support team and work with them to validate your PCI compliance documentation

green mulch
#

How would this validation be?

carmine hearth
#

Have you reviewed the documentation shared above?

#

The "API direct" tab currently says:

We strongly discourage passing card information directly to Stripe’s API as it means your integration is directly handling card information. Even if you do not store any payment information, we can only help simplify PCI compliance if you’ve integrated with Checkout, Elements, or our mobile SDKs.

If you continue to send card details directly to our API, you’ll be required to upload your SAQ D annually to prove your business is PCI compliant. SAQ D is the most onerous of all the SAQs, with over 40 pages of requirements you must implement to remain PCI compliant. We highly recommend you migrate to client-side tokenization of card information to substantially reduce the scope of your PCI compliance.

In addition to the significant PCI burden that this method places on you, it is not supported by Radar, our fraud prevention toolset. Radar’s functionality (for example, risk evaluation, rules, and so on) is only available when using any of our methods of client-side tokenization.

#

You'll need to reach out to support to complete the SAQ D documentation to continue with this pattern: https://support.stripe.com/contact

#

It's strongly recommended for you to use Elements to collect card details

green mulch
#

after that, is it possible?

carmine hearth
green mulch
#

after checking the PCI compliance documentation, right?

carmine hearth
#

Yes, that's required to collect payments using a flow like this.

green mulch
#

then to confirm the steps:

  1. stripe.products.create
  2. stripe.customers.create
  3. stripe.paymentMethods.create
  4. stripe.subscriptions.create
  5. ???
carmine hearth
#

You'd need a Price too, somewhere between 1 and 4

#

But yes, that looks like an accurate summary

green mulch
#

yes yes, forgot:

  1. stripe.products.create
  2. stripe.prices.create
  3. stripe.customers.create
  4. stripe.paymentMethods.create
  5. stripe.subscriptions.create
  6. ???
#

would I need a confirmation in step 7?

carmine hearth
green mulch
#

confused, in which case I don't use the stripe.subscriptions.create method anymore ?

carmine hearth
#

This would be in the result of that, if authentication were needed. This is made much easier by Stripe.js/Elements.

green mulch
#

can i call Stripe.js/Elements redirecting the user to a confirmation stripe url?

carmine hearth
#

What do you mean?

green mulch
#

the way I'm doing it, can I redirect the user to a confirmation screen?

carmine hearth
#

What do you mean by confirmation screen, exactly?

#

Do you have an example?

green mulch
#

the screen where the customer confirms the intention to pay, do you think it's necessary?

#

can i do it by the server automatically?

carmine hearth
#

Do you mean specifically for 3ds authentication, or some part of your own payment flow?

green mulch
#

yes

#

I'm seeing it here, I think I can create a subscription with status already active, right?

carmine hearth
#

That was not a yes or no question

#

It was A or B

#

It would be much more helpful for you to work on your integration then share specific examples where you're having trouble for us to help

green mulch
#

part of your own payment flow

carmine hearth
#

I suggest you work on that, go through your implementation and testing first

green mulch
#

I'm doing this

#

I'm seeing it here, I think I can create a subscription with status already active, right?

carmine hearth
#

That depends on how you create subscriptions and what options you use. It's not something you set explicitly. Do you have an example request/subscription we can discuss?

green mulch
#

I'm creating this way

#

step 6:

  1. stripe.products.create
  2. stripe.prices.create
  3. stripe.customers.create
  4. stripe.paymentMethods.create
  5. stripe.subscriptions.create
  6. ???
carmine hearth
#

Right, so that default_incomplete would be what we suggest when authenticating on the client with Stripe.js

#

If you want to do that, you can get the client_secret from the payment intent you expanded, and send that and the payment method id to your client app

#

Then use Stripe.js and confirmCardPayment to finish the payment in a way that supports 3ds:

green mulch
#

I understood

carmine hearth
#
stripe
  .confirmCardPayment('{PAYMENT_INTENT_CLIENT_SECRET}', {
    payment_method: '{PAYMENT_METHOD_ID}',
  })