Loading GetPhoto…
Loading GetPhoto…
Home / Product
Payment ProtectionPayments are held securely to protect both customers and photographers. Funds move only when the agreed service journey reaches its release point.
GetPhoto uses escrow-style payment holding — inspired by how trusted financial products protect both parties in a transaction. The customer’s payment is not released immediately to the photographer.
Instead, funds are held while the booking progresses through documented milestones. Release follows platform rules after delivery and the review window — protecting customers from non-delivery and photographers from non-payment after completed work.
This is marketplace infrastructure, not a brochure promise. Payment state is tied to booking state.
Customer completes payment after the partner accepts the booking.
Funds are secured in escrow — not transferred directly to the partner wallet.
Service milestones and delivery evidence progress on the booking timeline.
Customer review window opens. Remedies exist if delivery does not match scope.
Funds release to the partner per platform rules when the window closes cleanly.
Booking payment status shows funds secured — not yet released.
Customer protected pre-delivery; partner protected post-delivery.
Structured period before automatic release — time to verify delivery.
After delivery milestones are met and the post-delivery review window completes without a blocking dispute, per platform payment rules.
Cancellation policies apply based on booking status and timing. Refund outcomes follow Commerce domain rules tied to the booking record.
The mental model is similar — funds are set aside for a purpose and released only when conditions are met. GetPhoto applies this pattern to marketplace bookings.
GetPhoto discourages off-platform payment. Pre-booking contact details are not exposed to keep transactions inside protected flows.