payment-request | : money_with_wings : Implementation of Payment Request Api | REST library

The issue was with the nginx header. The dev env did not have this setting & QA had this. Here the payment was marked as () & when I changed it to accept all by adding * it started working.

As far as the Payment Request API is concerned, I think there three primary options:

• Apple Pay
• Google Pay
• basic-card

As you may have seen, basic-card is being deprecated (https://blog.chromium.org/2021/10/sunsetting-basic-card-payment-method-in.html) so you probably want to avoid this option.

Both Apple Pay and Google Pay provide access to billing and shipping address, and can be accessed as payment methods in the Payment Request API, and both provide their own alternate APIs (Apple Pay JS API and Google Pay Online API).

I don't know about Apple Pay, but the advice for Google Pay is to use Google Pay Online API (which makes use of the Payment Request API when available). Google Pay provides a consistent API for browsers that do and don't support the Payment Request API.

Does anyone know if there is a recommended new way to handle this via the API, or if it is advisable to move the collection of the buyer's billing and shipping addresses back to a form on our page even when using the payment request API?

The guidance for Google Pay is to place the Google Pay button above manual entry fields and to collect shipping information from Google Pay so that users can users don't start filling in the form before realizing there was a faster checkout option available.

So prioritize the digital checkout options for users that choose to use it, and make use of billing/shipping information from the digital wallet APIs. Make manual form fields available (suggest that form fields also make correct use of autofill attributes) for users who don't have access to or choose not to use the other payment options.

Demo site available with this in action: https://paydemo.withgoogle.com

FYI, if you're looking to integrate Google Pay into your site and are using a JavaScript framework, consider using the framework specific components from Google Pay for easier integration: https://github.com/google-pay/google-pay-button

It looks like you create this

The ideal way to approach this should be: Get the options list with evaluate method. Using that list create a loop, in that loop select the option and run another evaluate function that returns the variation info :

Are you looking for something like this?:

Since you use use App\Repositories\BankRequests\BankRequestRepository; your repositories/ folder should be placed inside the app/ folder, not the root folder. Also make sure that you're using namespace App\Repositories\BankRequests in your repository file.

After moving your folder (and maybe editing your namespace) run composer dumpautoload for composer to pick up those changes.

The payment request that you make with Stripe.js does not actually process a payment. It simply confirms that the user's browser supports Apple/Google Pay, and displays a payment sheet with the provided payment details. After the user authorizes the payment described on the payment sheet, Stripe will produce a payment method. At this point, if you ended your integration, the user would never be charged - you would simply have a Stripe payment method ID. What you'd need to do at this point is:

1. Save the payment method ID to a Customer: https://stripe.com/docs/api/payment_methods/attach
2. Set the payment method as the default for subscription invoices: https://stripe.com/docs/api/customers/update (by setting invoice_settings.default_payment_method)
3. Subscribe the customer to a recurring Price (e.g., https://stripe.com/docs/billing/subscriptions/fixed-price)

You would trigger all of the above logic as a result of receiving the payment method from the payment request:

Is it recommended then that Elements should go in the Profile component as opposed to being wrapped in App.js?

Yes, it's perfectly fine to wrap only the components that require Stripe.js (via the useElements and useStripe hooks) in the Elements Provider. In other words, any component that uses useElements or useStripe needs to either itself by wrapped by the Elements Provider or have an ancestor somewhere up the component tree that's wrapped by the Elements Provider.

In your example I would personally go with wrapping the Profile component with Elements if that's the only component that uses Stripe. Under the hood the Stripe Elements provider uses the Context API, which you can read more on here:

https://reactjs.org/docs/context.html

@chenz101

Looking my code

Make a class for below formats