payment | Payment 是基于 .NET Core | Chat library

Note that the name field of the Checkout Session is not necessarily your customer’s name, but the name on the Payment Method they are using.

It’s not possible to prefill this name field unless the customer already has a Payment Method attached that can be reused with ​​setup_future_usage.

• For a bancontact Payment Method, this is not possible since it’s for one-time payment only.
• For a card Payment Method, it’s possible. This would prefill the email, name, card details, and billing address as mentioned on the Stripe documentation.

In general I would recommend to let Stripe Checkout collect all the information, and then update your system from that, not the other way around.

Can you try to update the tsconfig.json file like this:

Even if the file is currently ignored, you can force adding it:

I'm not sure what you're using to code, but in order to set it in Android Studio, open the manifest of your project and under the "activity" section, put android:exported="true"(or false if that is what you prefer). I have attached an example.

till Android 10 any app can list ALL apps installed on device. starting Android 11 there are some limitations and by default you can't list all apps, so you are "safe". BUT 3rd-party may request QUERY_ALL_PACKAGES permission and will detect your app as well. note that Google Play Store have special policy for such apps, not every app may be published with it

still your app may be detected when it will use this 3rd-party apps API/Service (depends on way for access) and then it will lock itself

Even though your configured persistent messages on the payments queue, this just means messages will survive a broker restart - once a message has been consumed and acknowledged it would be removed.

If you know you're going to need the payment_analyze queue at some point in the future, is it viable to just create this queue/binding upfront and route messages to both payment_analyze and payments? Messages on the payment_analyze will bank up until you're ready to start consuming them. Note: If you're producing a large number of messages this approach might result in storage issues...

As an alternative, you could write the messages to BLOB storage (or some other data store) as part of your payments queue consumer (or a different queue/consumer altogether) and then when you're ready to introduce the payment_analyze queue, you could write a script to read all the old messages from BLOB storage and send them to the RabbitMQ exchange. With 'topic' exchanges - see here - you can probably be clever with wildcards and routing keys in your queue bindings to ensure both old messages (from BLOB storage) as well as new messages are both routed to the payment_analyze queue, but only new messages are routed to the payments queue (so that your payments queue consumer is not reprocessing old messages).

Another option (assuming you're not overly invested in RabbitMQ) could be to consider Apache Kafka instead which deals with this scenario quite nicely as messages aren't automatically removed from a partition once they've been processed by a subscriber.

Anyways, just a few options to consider...

One way to solve the issue is by parameterizing the ParentDTO Class with its own children.

CTEs can break this down a little easier. In the code below, the payment_streak CTE is the key bit; the start_of_streak field is first marking rows that count as the start of a streak, and then taking the maximum over all previous rows (to find the start of this streak).

The last SELECT is only comparing these two dates, computing how many months are between them (excluding June/July), and then finding the best streak per customer.

Payment args in EGLD are auto-filled from the call value you've already specified in the transaction, so you do not need to pass them as argument.

Therefore, your call data in this case would be myEndpoint@aa, without the payment arg.

As a side note, if this would've been an endpoint accepting another token than EGLD, you would've had to specify the token and amount in the data field, like: ESDTNFTTransfer@TokenIdentifier_in_hex@TokenNonce_in_hex@TokenValue_in_hex@Contract_address_in_hex@myEndpoint_in_hex@aa.

The ESDTNFTTransfer function sends any type of ESDT token, with or without nonce. If the token doesn't have a nonce (fungible), you can either pass 00 as nonce or leave the nonce space empty, like @TokenName_in_hex@@TokenValue_in_hex. Mind the fact that in order to use this function, you would have to compose a transaction with the destination set as yourself. The actual address of the destination would be contained in the data field in place ofContract_address_in_hex, making it a parameter of the ESDTNFTTransfer function.

If the endpoint accepted two tokens for example, then you could've used MultiESDTNFTTransfer@Contract_address_in_hex@02@Token1Identifier_in_hex@Token1Nonce_in_hex@Token1Value_in_hex@Token2Identifier_in_hex@Token2Nonce_in_hex@Token2Value_in_hex@myEndpoint_in_hex.

And yeah, you can always check the Elrond docs on ESDT Tokens / NFT Tokens for more details.