SecurePay

SecurePay is MeSomb's secure payment service for transactions where the buyer and the seller need extra confidence before money is released.

With SecurePay, the buyer pays through MeSomb, but the money is not released to the merchant immediately. The payment is held securely until the transaction reaches the expected confirmation stage, such as delivery confirmation or dispute resolution.

SecurePay is designed for online commerce, marketplace sales, social commerce, delivery-based sales, and high-value transactions where both parties need more protection.

Why use SecurePay?

In many online transactions, the buyer worries about paying before receiving the product, while the seller worries about delivering before being paid.

SecurePay helps reduce that risk by creating a controlled payment flow.

It helps merchants:

reassure buyers before payment;
reduce failed trust-based transactions;
structure delivery confirmation;
keep a clear record of the transaction;
handle disputes with evidence instead of informal conversations.

It helps buyers:

pay with more confidence;
know that the payment is linked to a specific order;
confirm when the product or service has been received;
open a dispute if there is a serious issue with the transaction.

When SecurePay is useful

SecurePay is useful when:

the buyer does not fully know the seller;
the seller delivers after payment;
the transaction amount is important;
the order requires proof of delivery;
the transaction happens through social media, WhatsApp, marketplace, or a custom website;
both parties want a clearer payment and delivery trail.

Examples:

online product sales;
electronics and phone sales;
furniture sales;
fashion and beauty product deliveries;
marketplace transactions;
service deposits;
pre-orders;
buyer-to-seller transactions requiring trust.

When SecurePay may not be necessary

SecurePay may not be needed for every payment.

For example, a standard direct payment may be enough when:

the buyer and seller already trust each other;
the product is delivered instantly;
the transaction is very low-risk;
the merchant already has an established refund and delivery process.

Merchants can decide when to offer SecurePay depending on their business model and risk level.

Main SecurePay roles

A SecurePay transaction usually involves three parties.

Role	Description
Buyer	The person who pays for the product or service.
Merchant / Seller	The person or business selling the product or service.
MeSomb	The payment platform that holds, tracks, and releases the payment according to the SecurePay flow.

Basic SecurePay flow

flowchart TD A[Buyer pays with SecurePay] --> B[MeSomb holds the funds] B --> C[Merchant prepares and delivers the order] C --> D{Buyer confirms delivery?} D -->|Yes| E[MeSomb releases the funds to the merchant] D -->|No issue reported after delay| F[Automatic release may apply] D -->|Problem reported| G[Dispute opened]

If there is a problem, the buyer may open a dispute before the money is released.

flowchart TD A[Buyer pays with SecurePay] --> B[MeSomb holds the funds] B --> C[Problem reported by buyer] C --> D[Dispute opened] D --> E[Evidence submitted by buyer and merchant] E --> F{Resolution decision} F -->|Release| G[Funds released to merchant] F -->|Refund| H[Buyer refunded] F -->|Partial| I[Partial refund and partial release]

SecurePay transaction statuses

A SecurePay transaction may move through different statuses.

Status	Description
`created`	The SecurePay transaction has been created, but payment may not yet be completed.
`funded`	The buyer has paid and the money is held securely.
`awaiting_delivery`	The merchant is expected to deliver the product or service.
`delivery_confirmed`	The buyer has confirmed delivery or completion.
`disputed`	A dispute has been opened because there is a problem.
`released`	The money has been released to the merchant.
`refunded`	The money has been returned to the buyer.
`cancelled`	The transaction was cancelled before completion.

Important notes

SecurePay does not replace good commercial practices. Merchants should still provide clear product descriptions, delivery conditions, refund policies, and customer support.

Buyers should review the product or service details before paying and should only confirm delivery after receiving what was agreed.

SecurePay helps structure the payment and confirmation process, but the quality of the transaction still depends on clear communication between the buyer and the merchant.