Skip to main content
DocPay integration has six steps: create a product, configure pricing, forms, UI customization, register a webhook and assign it to the product, and optionally register subproducts and generate QR codes. This page describes step 1 (product). Steps 2–6 (pricing, forms, customization, webhooks, subproduct) are on the REST API page.

​
1. Create product

The product represents your service in the Paymove system (parking, ticket, subscription, etc.). It is the root of the model - pricing, forms, customizations, and webhooks are attached to a specific product. Example create product request: 
POST /api/product/pay

{
  "partnerId": "9bd44869-3cab-4ad8-bf97-363778edd9ef",
  "productType": "PAY",
  "name": "PRODUCT NAME",
  "fullName": "FULL PRODUCT NAME" (optional),
  "shortName": "PRODUCT 1",
  "location": "Warsaw, ul. Marszałkowska 1",
  "timezone": "Europe/Warsaw"
}
FieldDescription
partnerIdPartner identifier (assigned by Paymove).
productTypeProduct type - for DocPay: PAY.
fullNameFull product/company name.
nameProduct name
shortNameShort display name.
locationLocation (e.g. address or country code).
timezoneIANA timezone (e.g. Europe/Warsaw).
Update product: 
PATCH /api/product/pay/{productId}
You can send only the fields to change; other relations (pricing, forms, webhooks) remain unchanged.

​
2. Pricing, forms, UI customization, webhooks, subproduct

Steps 2–6 (pricing, forms, UI customization, webhook registration and product assignment, subproduct and QR codes) are described on the REST API page as steps 1–5. You will find endpoints, request bodies, and responses there.

REST API

Full endpoint reference in configuration order: pricing, forms, UI customization, webhooks, subproduct and QR.