PApayu-com
Marketplace-Verification

Create Marketplace Verification

Initialize the verification process of the seller.

post/api/aml-verification/v1/verification

Request

Headers

Content-Typestring required

Content type

Authorizationstring required

Auth token

Request body

sellerIdstring required

Unique id of seller (submerchant) given by marketplace side. This id must be constant for every verification concerning the same seller (submerchant).

type'PAYOUT_ACCOUNT_DATA' | 'FULL' | 'UPDATE' | 'REVERIFICATION' | 'PERSONAL_ID_TAX_ID_CHANGE' | 'CONVERSION' required

Verification type. Possible values descriptions: <ul> <li><b>PAYOUT_ACCOUNT_DATA</b>- initialized by marketplace side. The verification with this type should contain the data of payout account and seller (submerchant). If this verification initializes seller in PayU then seller data are required. If it is just account update, then only account data are required.</li> <li><b>FULL</b> - verification which requires providing by seller all data for AML4 and payouts, typically initialized by marketplace side.</li> <li><b>UPDATE</b> - verification which requires providing by seller all data for AML4 and payouts, typically initialized by marketplace side.</li> <li><b>REVERIFICATION</b> - verification which requires providing by seller all data for AML4 and payouts, typically initialized by marketplace side.</li> <li><b>PERSONAL_ID_TAX_ID_CHANGE</b>- initialized by marketplace side. This allows to change PERSONAL_ID for private person or TAX_IDs for legal entity. Once the KYC verification process begins, the current account and payouts are blocked until verification is completed. If the process is interrupted (e.g. the company is unable to verify itself), PayU restores the old merchant account, thus unlocking the payouts on it.</li> <li><b>CONVERSION</b>- initialized by marketplace side. This allows to change PERSONAL_ID for private person or TAX_IDs for legal entity. Once the KYC verification process begins, the current account and payouts are blocked until verification is completed. If the process is interrupted (e.g. the company is unable to verify itself), PayU restores the old merchant account, thus unlocking the payouts on it.</li> </ul>

overridePayoutsboolean

Response

SUCCESS

verificationIdstring

Unique id of the verification provided by PayU.

statusstring

Current status of the verification:

  • WAITING_FOR_DATA - status after initialization of the verification, when PayU is waiting for data or after exceeding transaction limits for the occasional transaction flow.
  • WAITING_FOR_VERIFICATION - set when all the data were send to PayU (after complete).
  • REJECTED - set when there are some errors in the provided data. These status is send with error codes.
  • POSITIVE - final status for approved verification.
  • NEGATIVE - final rejection status.
sellerIdstring

Example response

{
  "verificationId": "aZl6Ja",
  "status": "WAITING_FOR_DATA",
  "sellerId": "seller_27"
}

Changes

No recorded changes to this operation across all 1 revision of this API.