Last Updated: August 2026
Payments are one of the places where digital convenience and digital risk meet.
We want paying for a service to be simple, but we also want customers to know how to recognise suspicious activity and how we protect the payment process.
This article explains our general approach to payment security and fraud prevention.
1. Use the Official Payment Process
When making a payment to fortheworld OÜ, use the payment method provided through:
An official invoice
An official checkout page
An official payment link
An agreed business or service arrangement
Do not make payments based solely on unexpected payment instructions received through email, messaging applications, or social media.
If someone suddenly tells you that our bank account has changed, verify it before sending money.
2. We Will Not Ask for Your Password
We will not ask you to send us:
Your account password
Your Google password
Your banking password
Your payment-card PIN
Your card security code by ordinary email
Your two-factor authentication code
Your private cryptographic keys
Other authentication credentials
If somebody claiming to represent us asks for this information, treat the request as suspicious.
3. Payment Card Information
Where card payments are available, payment-card information may be entered through the secure payment interface provided by the relevant payment provider.
We generally do not need you to send complete payment-card details to us through email, chat, forms, or other ordinary communication channels.
Do not send card numbers or security codes to a support address simply because someone asks for them.
If a payment requires additional authentication, use the secure authentication process provided by your card issuer or payment provider.
4. Third-Party Payment Providers
Some payments may be processed by third-party payment providers.
These providers may provide infrastructure for:
Card payments
Payment authentication
Fraud detection
Transaction processing
Refunds
Chargebacks
Currency conversion
Other payment-related functions
The payment provider may process information according to its own terms and privacy policy.
The exact provider used may depend on the service and payment method.
5. Fraud Detection
Payment providers and financial institutions may use automated systems to identify potentially fraudulent transactions.
These systems can consider signals such as:
Transaction information
Payment method
Device or technical information
Location-related signals
Previous transaction patterns
Authentication results
Other fraud-prevention indicators
A legitimate transaction can occasionally be flagged incorrectly.
If a payment is declined or held for verification, the payment provider or card issuer may need to complete additional checks.
We do not control every fraud-detection decision made by external payment providers.
6. Bank Transfer Security
Bank transfers require particular care because payments can sometimes be difficult or impossible to reverse once sent.
Before making a bank transfer, verify:
Recipient name
Bank account details
Amount
Currency
Invoice number
Payment reference
Use the information shown on the official invoice or other trusted payment documentation.
If you receive a request to use different bank details from those previously provided, verify the change through an independent trusted communication channel before paying.
7. Unexpected Payment Requests
Be particularly careful if you receive a message that:
Creates unusual urgency
Claims your service will immediately be terminated
Requests payment to a new bank account
Requests cryptocurrency payment unexpectedly
Asks for login credentials
Requests authentication codes
Contains an unusual payment link
Asks you to bypass the normal payment process
Urgency is not proof of legitimacy.
Neither is a familiar-looking logo.
When money is involved, verify the request.
8. Suspicious Emails & Messages
If you receive a suspicious message appearing to come from us, don't click links or open attachments until you have verified the message.
Check:
Sender address
Domain spelling
Destination of links
Requested payment details
Tone and urgency
Whether the request matches an actual invoice or service
A message can look professional and still be fraudulent.
Attackers are unfortunately very good at making things look official.
9. What To Do If You Suspect Fraud
If you believe a payment request may be fraudulent:
Stop the payment if you still can.
Then contact us through a trusted contact method.
Provide:
The message you received
Sender address
Invoice number, if any
Payment details requested
Relevant screenshots or evidence
Any other information that may help us investigate
If you have already made a suspicious payment, contact your bank or payment provider immediately.
They may have options available to attempt to stop, recall, or investigate the transaction.
10. If You Paid the Wrong Account
If you accidentally sent a bank transfer to an incorrect account, contact your bank immediately.
Also contact us if the payment was intended for fortheworld OÜ.
We will provide whatever transaction information we legitimately have available to help clarify the situation.
However, banks ultimately control the recovery or recall process for bank transfers.
We cannot guarantee that an incorrectly sent payment can be recovered.
11. Chargebacks & Payment Disputes
If you believe a payment was incorrect, duplicated, unauthorised, or otherwise problematic, please contact us where practical.
We will investigate legitimate billing disputes.
This can include:
Duplicate charges
Incorrect amounts
Payments made after cancellation
Unrecognised transactions
Incorrect service charges
Other billing errors
You may also have rights through your bank, card issuer, or payment provider.
Nothing in this policy prevents you from exercising those rights.
12. Account Security
Payment security is also connected to account security.
You should:
Use a unique password
Enable multi-factor authentication where available
Keep your email account secure
Avoid sharing login credentials
Review unexpected account activity
Log out of shared devices
Keep your devices and browsers updated
If you believe your account has been compromised, contact us as soon as possible.
13. Protecting Your Own Information
We can protect our infrastructure, but we cannot protect information that you voluntarily give to a fraudster outside our systems.
Never send sensitive information simply because someone appears to know your:
Name
Company
Invoice number
Email address
Previous payment
Service details
Attackers may obtain legitimate information from many different sources and use it to make a fraudulent request look convincing.
Information being correct does not automatically make the request legitimate.
14. We May Verify Payment Requests
For certain transactions or changes to payment instructions, we may need to verify information before proceeding.
For example, we may confirm:
Customer identity
Invoice information
Payment status
Bank-account changes
Refund requests
Changes to billing contacts
These checks are designed to protect both the customer and fortheworld OÜ.
A legitimate verification request should never require you to disclose your password or authentication credentials.
15. Refund Fraud
Refunds can also be targeted by fraudsters.
We may therefore verify a refund request before processing it.
Depending on the payment method, refunds may normally be returned to the original payment method where technically and legally possible.
We will not ask you to provide sensitive authentication credentials simply to process a legitimate refund.
16. Payment Information & Privacy
Payment-related information is personal or business information and may be protected by applicable data-protection laws.
We may process information necessary to:
Process payments
Confirm transactions
Prevent fraud
Investigate disputes
Issue invoices
Provide refunds
Meet accounting and tax obligations
Meet legal requirements
For more information, see our Privacy Policy.
17. Security Incidents
Despite reasonable safeguards, no online payment environment can be guaranteed to be completely risk-free.
If we become aware of a security incident affecting payment-related information, we will assess and respond according to the circumstances and applicable legal requirements.
This may include:
Investigating the incident
Containing the issue
Working with relevant providers
Taking corrective measures
Notifying affected parties where required
Notifying authorities where legally required
18. Our General Security Approach
We aim to use appropriate technical and organisational measures for the services we operate.
Depending on the payment and service architecture, this may include:
Access controls
Authentication
Encryption in transit
Secure payment interfaces
Monitoring
Fraud-prevention mechanisms
Permission management
Security updates
Operational controls
The exact security architecture varies between services and providers.
We avoid making absolute claims such as “100% secure” because no responsible technology company should promise something the internet itself cannot guarantee.
19. Changes to Payment Security
Payment technology and fraud patterns change constantly.
We may therefore update our payment-security processes as new risks, providers, technologies, and requirements emerge.
This article may be updated accordingly.
When we make material changes to this policy, we will update the Last Updated date.
The Short Version
Use official payment channels.
Verify unexpected bank-account changes.
Never send passwords or authentication codes.
Don't send card details through ordinary email.
If something looks suspicious, stop and verify it.
If you've already sent money to a suspected fraudster, contact your bank immediately.
And remember:
Professional-looking doesn't necessarily mean legitimate.
When money is involved:
Stop. Check. Then pay.
Build better. Connect smarter. Scale sustainably.
#ForPeopleForPlanet