Skip to main content
BoxNear← Back to app

Payment Processing Policy

Version 1.1Effective: July 14, 2026Last updated: July 14, 2026

BoxNear does not itself process card payments. This policy explains who does, in what currency, and what happens during the flow.

1. Processor

2. Currency and geography

All transactions are denominated in US dollars (USD). BoxNear currently operates in the United States. Payment methods offered are those enabled by Stripe for US merchants and buyers, including major credit and debit cards and any wallets Stripe enables automatically for the checkout.

3. What Stripe collects

Card details, billing ZIP, and fraud-detection signals are collected directly by Stripe inside its hosted payment fields. BoxNear does not receive or store your full card number. BoxNear receives the payment intent ID, charge ID, status, currency, amount, and processor fee.

4. Authorization and capture

When you submit a paid reservation, BoxNear creates a pending reservation and asks Stripe to create a PaymentIntent for the amount of the order (unit price × quantity, or the lot price for lot listings). If the payment fails or is not confirmed, the reservation is cancelled and the held quantity is released.

5. Confirmation and pickup code

On successful payment, Stripe sends a payment_intent.succeeded webhook. BoxNear then marks the payment captured, confirms the reservation, generates a six-digit pickup code, and notifies both parties. See Reservation & Pickup Policy.

6. Fees

  • BoxNear deducts a 30% platform fee from the gross of each paid order — see Platform Fee Policy.
  • Stripe charges its own processing fees. Those fees are separate from BoxNear's platform fee and are governed by Stripe's agreement with the platform account.

7. Refunds and disputes

Refunds are executed through Stripe's refund API and proportionally reverse the platform fee and the transfer. Cardholder chargebacks are handled through Stripe's dispute pipeline. See Refund Policy and Dispute Resolution.

8. Security

Card capture uses Stripe's hosted elements, so card data does not touch BoxNear's servers. Webhook events are signature-verified using Stripe's signing secret before any state change.