Frequently asked questions about SecurePay

SecurePay is MeSomb's secure payment service that can hold funds until delivery, confirmation, or dispute resolution. It helps buyers and merchants complete transactions with more confidence.

No. With a normal payment, the merchant may receive the money immediately or according to the standard settlement process. With SecurePay, the money can be held until the transaction reaches the required confirmation or release condition.

SecurePay can be used by eligible merchants, platforms, sellers, and buyers depending on the MeSomb services available in their market and account configuration.

The SecurePay fee depends on the merchant or platform configuration. It may be paid by the buyer, the merchant, both parties, or the platform. The fee should be visible or explained before the buyer completes payment.

The merchant is paid when the SecurePay transaction is released. This may happen after the buyer confirms delivery, the confirmation period expires without dispute, a dispute is resolved in favor of the merchant, or a manual release is approved according to the transaction rules.

Cancellation depends on the transaction status and SecurePay rules. If the merchant has not delivered yet, cancellation or refund may be possible. If the transaction is already delivered or released, different rules may apply.

Depending on the transaction configuration, SecurePay may support automatic release after a defined period if no dispute is opened.

The buyer should contact support or the merchant immediately. However, once delivery is confirmed, funds may be released to the merchant. Buyers should only confirm delivery after verifying the product or service.

The buyer may open a dispute before the funds are released. The buyer should provide evidence such as communication records, expected delivery date, and transaction details.

The merchant can provide proof of delivery during the dispute process. The proof may be used to decide whether the funds should be released, refunded, or partially resolved.

Yes, if the service has clear completion criteria. Examples include delivery service, repair service, professional service deposit, event or booking service, or project milestone payment. For services, the merchant should clearly define what counts as completion.

Yes, if the delivery and access conditions are clear. For example: access link delivered, account activated, file delivered, or license or code provided. The merchant should keep proof that the digital product was delivered.

Once a SecurePay transaction is released, reversal may be limited. Buyers should open a dispute before confirming delivery or before the release deadline expires.

Not necessarily. SecurePay availability may depend on merchant eligibility, country, payment method, transaction type, platform configuration, and risk controls.

No payment system can eliminate all fraud. SecurePay reduces risk by holding funds, recording transaction steps, and supporting disputes, but buyers and merchants should still follow safe transaction practices.

Merchants should configure their SecurePay settings, understand the fee structure, define delivery and confirmation rules, prepare clear product or service descriptions, and train their team on delivery proof and dispute handling.

Buyers should verify the transaction details, understand what they are buying, check the amount and currency, keep communication records, and pay only through the official SecurePay link or checkout page.