SecurePay for merchants

SecurePay helps merchants receive payments while giving buyers more confidence in the transaction.

It is especially useful for merchants selling online, through social media, by delivery, or in situations where the buyer wants assurance before the merchant receives the final payout.

Activating SecurePay

A merchant can activate SecurePay when creating a payment link or checkout session, depending on the features enabled on the merchant account.

A SecurePay-enabled payment should clearly define:

what the buyer is paying for;
the total amount;
the currency;
delivery conditions;
confirmation rules;
refund or dispute expectations.

Merchant flow

flowchart TD A[Create SecurePay payment] --> B[Share payment link with buyer] B --> C[Buyer pays] C --> D[Transaction becomes funded] D --> E[Prepare and deliver order] E --> F[Buyer confirms delivery] F --> G[Funds are released]

What the merchant sees

For each SecurePay transaction, the merchant should be able to see:

transaction ID;
order reference;
buyer information where available;
amount;
currency;
SecurePay status;
payment status;
delivery status;
dispute status if applicable;
fee amount;
net amount;
important timestamps.

Example 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.

Delivery and fulfillment

Once a SecurePay transaction is funded, the merchant should deliver according to the agreed terms.

Recommended delivery information to store:

delivery method;
delivery address or pickup location if applicable;
delivery person or logistics provider;
tracking number;
delivery date;
recipient name;
proof of delivery.

The more structured the delivery evidence is, the easier it is to resolve a dispute if one occurs.

Fees

SecurePay may include a service fee.

Depending on your MeSomb configuration, the SecurePay fee may be paid by:

the buyer;
the merchant;
both parties;
a platform or marketplace.

A transaction should clearly show:

gross amount;
SecurePay fee;
other payment fees where applicable;
net amount to be released to the merchant.

Example:

<span><span style="color: undefined">Amount paid by buyer: 15,000 XAF</span></span>
<span><span style="color: undefined">SecurePay fee: 300 XAF</span></span>
<span><span style="color: undefined">Net amount released to merchant: 14,700 XAF</span></span>
<span><span style="color: undefined"></span></span>

The exact fee configuration depends on your account settings.

Auto-release

Some SecurePay transactions may support automatic release after a confirmation period.

Example:

<span><span style="color: undefined">Buyer has 48 hours after delivery to confirm or open a dispute.</span></span>
<span><span style="color: undefined">If no dispute is opened during that period, funds may be released automatically.</span></span>
<span><span style="color: undefined"></span></span>

Auto-release helps avoid situations where a buyer receives the product but never confirms the transaction.

The auto-release delay depends on the rules configured for the transaction.

Disputes

A buyer may open a dispute if there is a serious issue with the transaction.

When a dispute is opened:

funds remain on hold;
the transaction status becomes disputed;
the merchant may be asked to provide evidence;
the dispute is reviewed according to the applicable process;
the final decision may release, refund, or partially split the funds.

Merchant evidence may include:

delivery proof;
tracking number;
product photos;
chat history;
invoice;
pickup confirmation;
service completion proof.

Merchant best practices

To reduce disputes:

use accurate product descriptions;
show real product photos where possible;
communicate delivery timelines clearly;
avoid ambiguous order terms;
keep proof of delivery;
respond quickly to buyer questions;
do not mark an order as delivered before it is actually delivered;
do not pressure buyers to confirm before receiving the product or service.

When not to use SecurePay

SecurePay may not be appropriate for:

illegal or prohibited products;
unclear services with no defined completion criteria;
transactions where the seller cannot provide delivery evidence;
situations where both parties do not agree to SecurePay conditions.

Merchant checklist before sending a SecurePay link

Before sharing a SecurePay payment link, verify that:

[ ] the amount is correct;
[ ] the product or service is clearly described;
[ ] the delivery method is agreed;
[ ] the buyer knows how confirmation works;
[ ] the refund/dispute process is clear;
[ ] the transaction reference is correct;
[ ] your contact information is up to date.