Payment Verification Policy

1. Purpose

These rules help a client verify who is authorized to provide payment instructions for MalixCode projects. Scope, price, timing, milestones, and refund terms are agreed separately in the project proposal, agreement, or correspondence.

2. Authorized communications

• Managers may discuss a project and name an available payment method, but they do not accept money and do not provide or confirm recipient details.
• Only the MalixCode owner provides and confirms the intended recipient and exact payment instructions after a request is submitted through malixcode.com.
• MalixCode does not ask a client to send payment to a manager's personal account.

3. Verification before payment

• After the project is agreed, submit a payment-details request through the form on malixcode.com.
• Wait for the owner's personal response and compare the recipient and every payment detail immediately before sending money.
• Do not send money if the recipient, account, email, phone number, tag, or other payment detail differs from the owner's confirmation.
• If new, changed, or unexpected instructions arrive after confirmation, stop and verify them again through the website or MalixCode's official email.

4. Form data

The payment-details request form collects only contact information, the agreed package, and consent confirmation. It is not intended for bank-account, card, digital-wallet, or payment-account credentials. See the Privacy Policy for more information.

5. Suspected fraud

• Do not send money while verification remains unresolved.
• Keep the conversation, sender address, payment instructions, and transfer confirmation if money has already been sent.

Report a suspicious request to team@malixcode.com.

6. Relationship to project terms

These rules supplement, but do not replace, the agreed project terms, proposal, agreement, or invoice. They do not limit rights or remedies available under applicable law.