rad195/internship-entry-task-2 ? reverse-engineered prompt

Build me a payment service in .NET that works through Docker Compose and stores data in PostgreSQL.

I want a small API where I can create a payment operation, submit it for processing, check its status, and see the full history of status changes. The important part is that it has to be safe with retries and restarts, so the same operation never creates two payments with the provider, and the final status only changes when a receipt comes back from the provider simulator over HTTP.

Please include a health check, a metrics endpoint, and clear JSON responses. The service should come up with the database and provider simulator in compose, run migrations on start, and keep data after the container restarts. Also make sure duplicate operation creation is rejected, repeated submit calls are handled cleanly, and late or repeated receipts do not break the final state.

If you need to check any current .NET or Docker details, look them up online and then wire it all together.