Seller verification is the identity-verification step for an organization. There is no separate identity check and no seller PayPal onboarding: customer payments use the deployment’s central PayPal Business account. The same form also stores the bank account that may receive seller earnings after a payout rail is implemented. Today, submitting the form does not connect to the bank, verify ownership through a banking network, or move any money.
Payout execution is currently disabled. Bank details are collected as a future destination only.

Complete seller verification

Open Finance → Account, find Seller verification, and select Start or Update. OurPay currently supports Indian sellers and Indian bank accounts only.

Individual seller

Provide:
  • Legal name exactly as shown on the PAN
  • PAN
  • Date of birth for an adult seller
  • Indian residential or registered address, including state and six-digit postal code
  • GSTIN, when applicable
  • Bank account holder name, account number, IFSC, and account type (savings or current)

Company seller

Provide:
  • Company legal name, PAN, and registration number
  • Indian registered address, including state and six-digit postal code
  • GSTIN, when applicable
  • Authorized representative’s name, PAN, and date of birth
  • Bank account holder name, account number, IFSC, and account type
The account holder name should match the seller or the legal entity entitled to receive its earnings. OurPay validates field formats, but format validation is not proof of identity or bank ownership.

Submit and review

Save a draft, review every value, accept the consent statement, and submit it to OurPay. Statuses have these meanings: Changing identity or bank details returns the profile to draft. Changing bank fields also returns the bank status to unverified.
The current workflow is an OurPay review of the information submitted. It is not a PayPal KYC redirect and it does not claim real-time validation against a government or banking database.

How sensitive fields are stored

PANs, GSTINs, representative PANs, and bank account numbers are accepted only over authenticated dashboard requests. Sensitive values are encrypted using the deployment’s configured envelope encryption key. The API and dashboard return presence indicators and last four characters rather than the full stored values. Seller verification is unavailable if secure key management is not configured; OurPay returns a service-unavailable error instead of storing those fields without encryption.

Invoice issuer is separate

Seller verification establishes who owns the organization and records a future payout destination. The legal name and address printed on customer invoices are configured separately under Settings → Payment providers → Invoice issuer. A complete invoice-issuer profile is required before live PayPal payments can be enabled or charged. Keeping these records separate is deliberate: changing a bank destination must not silently change the seller identity printed on historical customer documents.

PayPal collection

Enabling PayPal for an organization authorizes its checkouts to use the one deployment-managed PayPal Business account. It does not create a PayPal account for the seller, link the bank account to PayPal, or make the seller a PayPal sub-merchant. See Payment providers for the complete collection model.