How to optimize transaction speed when integrating Crypterium API into the payment system?

Hello all,

I am integrating Crypterium API into customer service payment system and come across a problem that I think most people are worried about: transaction processing sometimes takes longer than expected, especially in peaks of requests.

I am going to ask the Among Us Online community the following points:

Are there any ways to shorten the time of response when creating transactions and checking transaction status?

Where should I cache data to relieve load but still keep accuracy?

Is there a request limit (rate limit) which I should avoid exceeding during the production version?

For those who have actually implemented it, what is your error monitoring and logging practice to know about the bottlenecks?

I am aiming to have a more reliable system, hence I am inviting experience sharing from those who have used Crypterium in payment projects or e-wallets.

Thanks a lot for your support. If there is any document or best practice available, I would be very much interested in it as a means to improve the system further.