OurPay reviews an organization before enabling normal payment acceptance. The review checks what the seller offers, whether the integration is ready, and whether the submitted information is consistent with the Acceptable Use Policy. All lawful product and service categories are eligible. A category label, high price, custom quote, or human fulfillment does not itself trigger rejection. Physical delivery and service performance are valid fulfillment methods. Review requests address the actual transaction, provider requirement, or evidence under review. Seller verification is also the organization’s identity-verification step. There is no separate Stripe Identity or PayPal seller-onboarding flow.

​
Before submitting

Complete the review checklist in Finance → Account:
  1. Create at least one valid product and price.
  2. Configure a checkout link or API integration.
  3. Describe what you sell and select the relevant selling categories and pricing model.
  4. Add a working product website.
  5. Add a support email.
  6. Configure the central PayPal payment provider and the legal invoice issuer.
  7. Complete and submit seller verification and bank details.
Social links can provide useful review context but are not a required activation gate. A seller verification that has been submitted may appear as pending while the organization review proceeds; that does not mean the identity or bank account has already been verified.
Build and test the complete customer journey before submitting. A working product URL, checkout, fulfillment path, and support contact make the intended use much easier to evaluate.

​
One seller-verification form

The form accepts either an individual or company profile and currently supports India only. It collects PAN and identity details, an Indian registered address, and the future payout bank destination. Company profiles also require registration and authorized-representative details. This is the seller-verification step shown in the checklist. Completing a second identity flow is not required. The current implementation validates data formats and submits the profile for OurPay review. It does not redirect to a third-party KYC session and does not claim that PAN or bank ownership was verified in real time. See Account setup for the exact fields and status meanings.

​
Organization review outcome

After submission, OurPay evaluates the organization and records a pass or fail decision. Payment activation also requires the non-review setup gates to remain complete, including an active direct PayPal processor record and a submitted seller-verification profile. If more information is requested, update the organization or seller details and resubmit. A denied organization can use the appeal path exposed by the dashboard when one is available. Do not create another organization to bypass a review decision. OurPay does not publish a guaranteed review completion time. The dashboard is the source of truth for the current status and required action.

​
Ongoing safety reviews

OurPay may review an active organization again when its products, risk profile, or transaction history changes. During a review, payment capability follows the organization’s server-side status; the checkout UI must not be treated as proof that an organization is approved. Evidence of fraud, non-delivery, transaction-level legal or provider violations, misleading descriptions, or unresolved buyer harm can require additional information or payment suspension. A category label alone is not grounds for suspension. A payout requested while an organization is under review remains held; if the organization is approved, the ledger reservation is released to the configured payout rail. PayPal execution still depends on the deployment’s payout feature flag and provider approval.

​
Testing

Use the sandbox environment with a PayPal sandbox buyer. Do not use a real PayPal account to manufacture purchases from yourself. For a production smoke test, use the smallest legitimate product amount and verify the PayPal capture, OurPay order, invoice, receipt, and seller-payable entries before accepting normal traffic.

​
Data handling

Sensitive seller and bank values are encrypted at rest and are returned only as presence flags and last-four hints. If secure key management is unavailable, seller verification fails closed with a service-unavailable response. Access to these records should be limited to people performing the review. A dashboard “submitted” or “verified” label does not replace any legal, tax, sanctions, or payment-provider diligence the deployment operator is required to perform.