Update billing and fixed issues

[laken11]

Pull Request Title

Description

Summary

Provide a concise summary of the changes made in this PR.

Motivation

Explain the reason for these changes. Why is it needed? What problem does it solve?

Related Issue(s)

• Issue(s): Link any related issues here (e.g., closes #123, fixes #456).

Detailed Changes

• New Features/Enhancements: List the new features or enhancements introduced.
• Bug Fixes: List any bugs that were fixed, including their severity.
• Refactor: Describe any code refactoring done to improve the structure without altering functionality.
• Documentation: Mention if there are any updates to documentation.

Checklist

Code Quality

• Correctness: Ensure the code is correct and fulfills the intended purpose.
• Code Simplicity: Verify that the code is simple and avoids unnecessary complexity.
• Style: Confirm that the code adheres to the project's coding standards and guidelines.
• Naming: Ensure variable and function names are descriptive and meaningful.
• Comments: Verify that all non-obvious code is well-commented.

Testing

• Unit Tests: Ensure unit tests are present and cover the new code adequately.
• Test Accuracy: Verify that tests are accurate and verify the correct behavior of the code.
• Test Coverage: Check that the tests cover all edge cases and potential failure points.
• CI/CD: Ensure that the PR passes all continuous integration and continuous deployment checks.

<< Provide screenshots that show the test coverage after your PR >>

Security

• Security Concerns: Review for any potential security vulnerabilities.
• Data Handling: Verify that sensitive data is properly handled (e.g., no hardcoded credentials).
• Input Validation: Ensure all user inputs are validated and sanitized.

Documentation

• Documentation Updated: Ensure any new features or changes are well-documented.
• ReadMe/Changelog: Update the ReadMe or Changelog if necessary.

Dependencies

• Dependency Updates: List any updates to external dependencies and the reasons for these updates.
• Backward Compatibility: Confirm that changes are backward-compatible or provide migration steps.

Deployment

• Deployment Considerations: Identify any special considerations for deploying these changes (e.g., database migrations).

Reviewer Selection

• Assign the team lead on the project for review.
• Assign a team member who is familiar with the codebase for a second review.
• Merge the PR only after receiving an approval. Deployment-triggering PRs should be merged by the team lead.

Branch Deletion

• Branch Deleted: After the PR is merged, delete the branch if it is no longer needed.

Reviewer Notes

General Review

• Understanding: Confirm that you understand the changes made in this PR.
• Ask Questions: Leave comments or ask questions if any part of the PR is unclear.
• Review Thoroughly: Review the code thoroughly to catch any potential issues.

Final Approval

• Approve: If all checks are satisfactory, approve the PR.
• Request Changes: If there are issues, request changes and detail what needs to be addressed.