LOCK2PAY / FAQ
Frequently asked questions
Direct answers about escrow, payments, inspection, disputes and withdrawals.
The LOCK2PAY approach
Start with the question closest to the stage of your transaction.
LOCK2PAY is designed around a visible transaction lifecycle: parties agree on terms, payment is recorded against the escrow, delivery and inspection milestones are visible, and the next step remains clear.
Feature pages use the same terminology and controls as the authenticated application so users can move from learning to action without changing mental models.
Answers
What is LOCK2PAY?
LOCK2PAY is an escrow workflow that records transaction terms and keeps funds protected while delivery and inspection occur.
How does a buyer pay?
The seller creates an escrow and shares its payment reference. Payment handling is connected to the escrow record, not a buyer browser claim.
When does a seller receive funds?
After the required workflow reaches release or completion. The current seller platform records the protected stages and wallet movements.
What is the inspection period?
Each escrow defines an inspection period. The current seller creation workflow defaults to four hours and stores the value on the escrow.
What happens if there is a problem?
The transaction can move into a dispute workflow, where the parties can review case status and evidence.
What are the fees?
The configured LOCK2PAY platform fee is 1.5%. Any payment-provider fees are separate where applicable.