almo | Desktop version of alm | Runtime Evironment library

If you aren't using the Stripe iOS SDK, try passing the PKPayment's properties to the /v1/tokens endpoint on Stripe in the parameters shown here: https://github.com/stripe/stripe-ios/blob/master/Stripe/STPAPIClient%2BApplePay.m#L121-L150 and

That gives you back a Token object. Create a PaymentMethod object using that Token object (as Tokens are legacy) with the /v1/payment_methods endpoint and passing card: {token: tok_visa }, which gets you back a PaymentMethod object: https://stripe.com/docs/api/payment_methods/create#create_payment_method-card

Now you can attach the PaymentMethod to a PaymentIntent and confirm it server-side.

If the date is part of the filename, append it (whereever it's added by logrotate):

Well, apparently in your implementation values like 210 and 199 do not fit into the range of type char. So, the conversion is narrowing. {} initializers do not allow narrowing conversions.

This suggests that your implementation apparently uses signed char type.

You can forcefully convert the values to char by using explicit casts inside the {}. You can stop using {} initializers. You can force your implementation to use unsigned char. There are many "solutions" for this problem, but there's no way to chose one without more context.

If the code was originally written for the same "family" of implementations you are compiling it on now, then most likely it was simply written for an older version of the language, which performed that narrowing conversion implicitly. In that case to reproduce the old behavior you'll need explicit casts

Put your query in a try/catch block, and show the MessageBox in the catch. Something like, e.g.: