Document signing

The Document signing page connects Requiply with an electronic document-flow (EDO) provider, so the PDFs you generate from a booking can be sent for a qualified electronic signature without leaving Requiply.

You can find this page under Settings → Integrations → Document signing.

Why this matters

Requiply already turns a booking into paperwork — the invoice and any custom export template you designed. Until now those PDFs were downloads: staff exported the rental agreement, emailed it, and chased a signed scan back.

With a signing provider connected, the loop closes inside Requiply:

1. Save the generated PDF to the booking (Booking documents).
2. Send it to the provider for signing, addressed to the client's company.
3. Watch the status on the booking — Awaiting your signature, Awaiting client, Signed, Rejected.

Supported providers

Each provider is a card showing its logo, tags, a Tutorial link that opens Requiply's step-by-step setup guide in a new tab (in your interface language), and Set up (or its configured state once connected).

Setting up Vchasno

Click Set up on the Vchasno card. The dialog asks for one credential:

The dialog carries the setup note:

Create an API token in your Vchasno.EDO cabinet (an active Integration plan is required). Documents you send will appear in your Vchasno cabinet and be routed to the client's company for signing with a qualified electronic signature.

When you click Save, Requiply verifies the token with Vchasno before storing it. Only a verified token is encrypted and saved, and the card then shows the integration as configured.

If your Vchasno plan is missing

Vchasno's API requires the Integration plan. If your token is valid but the company behind it has no such plan, the dialog does not fail — it shows an amber panel:

Your token is valid, but your Vchasno company does not have the Integration plan required for API access. You can activate a free 30-day trial — Vchasno offers it once per company, and the 30 days start immediately.

Click Activate free 30-day trial and Requiply asks Vchasno to switch the company onto the trial, then saves the integration automatically.

Managing connected accounts

Reopening the dialog for a connected provider shows what is connected. The stored token is never returned to the browser.

With one account, the dialog looks like the setup form: the token is masked (••••••••••••) with a Replace button. Below it are Disconnect and Add another account.

With two or more accounts, the dialog lists them. Each row shows the account name and when it was connected:

Several Vchasno accounts

An organization that signs as more than one legal entity (for example a company and a sole proprietor) can connect one Vchasno account per entity:

1. Open the Vchasno dialog and click Add another account.
2. Enter a Name that tells the accounts apart, such as the company name, and the API token of that Vchasno company.
3. Click Connect. The token is verified the same way as the first one, including the trial offer when the plan is missing.

The first account keeps the provider's name (Vchasno) until you rename it. The same token cannot be added twice.

Disconnecting an account

Disconnect removes the account from this list and from the send dialog right away. If it was the default, the oldest remaining account becomes the default.

Documents already sent from that account and still waiting for a signature keep updating: Requiply holds on to the token until each of them is signed or rejected, then deletes it. The confirmation dialog says how many such documents there are.

What the integration unlocks

Once a provider is active, a signing button appears next to every saved document on a booking's Documents card. Sending asks for two things about the counterparty:

Requiply uploads the PDF with first_sign_by: owner, so your organization signs first in the Vchasno cabinet, and the document then moves to the client. The full flow, statuses, and status refresh are documented in Booking documents.

Statuses

The chip on each document maps the provider's status onto one of:

How this connects to the rest of Requiply

Common scenarios

Getting a rental agreement signed

1. Connect Vchasno here.
2. Open the booking, use Export → Save to store the rental agreement on the booking.
3. On the Documents card, click the Vchasno button next to it, enter the client's EDRPOU and email, and send.
4. Sign it in your Vchasno cabinet, then watch the chip move to Awaiting client and finally Signed.

Rotating a leaked token

Revoke the token in the Vchasno cabinet, generate a new one, then use Replace here (Replace token in the account's ⋯ menu when several accounts are connected). Documents already sent keep their history — the chip and provider link on each document stay valid.

Tips and cautions