Prepare the SES Hospedajes connection

The initial SES Hospedajes connection and certificate replacement currently require guided assistance. Holidario can store a digital certificate and each operation's establishment identifier, but this screen does not provide an independent SES connection test.

For that reason, Configuration complete does not by itself prove that a real submission will be accepted. It means Holidario has the file and extracted keys it needs to attempt authentication.

Who must be involved#

• a team administrator with access to Settings > Channel;
• the person responsible for traveller communications;
• Holidario support for the first activation or a certificate change;
• where appropriate, the authority or the organization's adviser to determine the correct obligations, establishments, and credentials.

Holidario performs the technical communication. It does not determine which accommodation must be reported, which certificate may represent the organization, or which legal deadline applies.

Information to prepare#

Before the setup session, gather:

1. a compatible certificate file containing its private key, normally in .p12 or .pfx format;
2. the exact password for that file;
3. the certificate holder and internal confirmation that it may be used for this communication;
4. the establishment identifier corresponding to each short-term rental operation;
5. one representative operation and reservation for the later check;
6. the certificate expiry date and a person responsible for renewal.

Do not send the certificate or its password by email, chat, or a normal support ticket. Agree on a secure channel during assisted setup.

What Holidario configures#

The configuration has two distinct levels:

• Team: the certificate and its password are managed under Settings > Channel > Reservation Authority Settings.
• Operation: each short-term rental keeps its own State Lodging ID. Do not copy an identifier from another property as an approximation.

A configured certificate without establishment identifiers does not complete the journey. A populated identifier also does not confirm that it remains active or belongs to that operation.

Minimum evidence before using the connection#

The person assisting activation should confirm:

• the form accepts the file without a password, certificate, or private-key error;
• the configured state appears for the team;
• every active operation has its confirmed identifier;
• the team knows who validates the real traveller party before submission;
• the first controlled communication result is reviewed from the reservation and check-in widget.

Do not use the ratio between registered travellers and the guest count selected at booking as an automatic validation. Holidario considers check-in complete from the first registered person; the responsible operator must confirm who actually stayed.

If an error appears#

• Empty or unrecognized file: retain the original file and confirm its format with its issuer.
• Certificate or private key not found: the file does not contain everything this flow requires.
• Certificate processing failed: confirm the password without sharing it in the ticket.
• The screen says configured but submission fails: do not replace the certificate blindly. Record the team, operation, reservation, time, and visible message without traveller personal data.
• The establishment identifier is missing: escalate to administration; front desk staff must not invent it or reuse another one.

Follow Submit guest records to the authority only after assisted setup has confirmed this preparation.

Current boundary#

The public documentation does not provide a self-service procedure for replacing active credentials. That changes the identity used by live submissions. Until the product provides a verifiable connection and rotation test, request guided assistance for initial setup, renewal, or replacement.