How SecurePay works

SecurePay adds a secure holding step between payment and final settlement.

Instead of releasing the money to the merchant immediately, MeSomb holds the funds until the transaction reaches the expected release condition.

Step 1: The merchant creates a SecurePay payment

The merchant creates a payment link or checkout session and activates SecurePay for the transaction.

The payment should include clear information such as:

  • amount;
  • currency;
  • order reference;
  • product or service description;
  • buyer information when available;
  • delivery or fulfillment conditions;
  • dispute or confirmation rules.

The buyer receives a SecurePay-enabled payment link or checkout page.

Step 2: The buyer pays

The buyer pays using an available payment method supported by MeSomb.

After successful payment, the SecurePay transaction becomes funded.

At this point:

  • the buyer has paid;
  • the merchant can see that the transaction is funded;
  • the money is held by MeSomb;
  • the merchant should prepare the order or service.

Step 3: The merchant delivers the product or service

After the transaction is funded, the merchant should deliver the product or perform the service according to the agreed terms.

Depending on the transaction type, delivery may mean:

  • physical product delivery;
  • digital product access;
  • completion of a service;
  • pickup confirmation;
  • shipment confirmation.

The merchant should keep proof of delivery where possible.

Examples of useful proof:

  • delivery receipt;
  • signed confirmation;
  • delivery photo;
  • tracking number;
  • customer message confirming receipt;
  • service completion document.

Step 4: The buyer confirms delivery

Once the buyer receives the product or service, the buyer can confirm delivery.

After confirmation, the transaction may move to fulfillment status delivered.

Depending on the merchant settings, MeSomb may then release the funds to the merchant automatically or after a short review or settlement delay.

Step 5: MeSomb releases the money

When the release condition is met, MeSomb releases the funds to the merchant.

The SecurePay transaction status becomes released.

The merchant can then see the released amount, fees, and net amount in their account or transaction history.

What happens if the buyer does not confirm?

Depending on the merchant configuration and SecurePay rules, MeSomb may support an automatic release after a defined confirmation period.

For example:

flowchart TD A[Buyer receives the product] --> B[Buyer does not confirm or open a dispute within the allowed period] B --> C[SecurePay may automatically release the funds to the merchant]

The exact auto-release behavior depends on the SecurePay settings applied to the transaction.

What happens if there is a problem?

If the buyer reports a serious issue before the funds are released, a dispute may be opened.

Examples:

  • product not received;
  • wrong product delivered;
  • damaged product;
  • incomplete service;
  • merchant and buyer disagree about delivery;
  • suspected fraud or abuse.

When a dispute is opened, the transaction becomes disputed, and the funds remain on hold until the dispute is resolved.

SecurePay lifecycle

flowchart TD created[created] --> funded[funded] funded --> awaiting_release[awaiting_release] awaiting_release --> delivery_confirmed[delivery_confirmed] delivery_confirmed --> released[released] awaiting_release --> disputed[disputed] disputed --> dispute_released[released] disputed --> refunded[refunded] disputed --> partially_resolved[partially resolved] created --> cancelled[cancelled] funded --> direct_refunded[refunded] classDef normal fill:#ecfeff,stroke:#00c2a6,color:#0f172a,stroke-width:1.5px; classDef final fill:#f8fafc,stroke:#64748b,color:#0f172a,stroke-width:1.5px; classDef risk fill:#fff7ed,stroke:#f97316,color:#0f172a,stroke-width:1.5px; class created,funded,awaiting_release,delivery_confirmed normal; class released,dispute_released,refunded,direct_refunded,cancelled,partially_resolved final; class disputed risk;

SecurePay release conditions

A SecurePay transaction may be released when one of the following conditions is met:

  • the buyer confirms delivery;
  • the confirmation period expires without dispute;
  • the dispute is resolved in favor of the merchant;
  • MeSomb or the platform administrator manually approves the release according to the applicable rules.

SecurePay refund conditions

A SecurePay transaction may be refunded when:

  • the transaction is cancelled before delivery;
  • the merchant accepts a refund;
  • the buyer wins a dispute;
  • the product or service cannot be delivered;
  • MeSomb or the platform administrator decides that refund is the appropriate resolution.

Good practices

Merchants should:

  • describe the product or service clearly;
  • confirm delivery terms before asking the buyer to pay;
  • keep delivery evidence;
  • respond quickly to buyer messages;
  • avoid using SecurePay for vague or poorly defined transactions.

Buyers should:

  • review the order information before paying;
  • keep communication records;
  • confirm delivery only after receiving what was agreed;
  • open a dispute only when there is a real issue.