Skip to content
Holidario Documentation

Legal and compliance

Known product boundary This page explicitly documents something Holidario does not currently support. Do not treat it as an available procedure.

Prepare the Sede Registradores connection

Understand the required credentials and why certificate activation or replacement needs guided assistance.

For
  • I own or administer an agency
Available on
  • Agency

The initial Sede Registradores connection and any certificate replacement currently require guided assistance. This integration can retrieve presentations, authenticate with the certificate, and expose formal actions on notifications; it must not be activated as an informal test.

The screen calls this credential Mercantile Registry Data, although the operational dashboard also shows presentations linked to property registries. Confirm with the organization and its advisers which account and representation apply to its circumstances.

Who must be involved#

Assisted Registry configuration
  1. Agency Confirm authority Name the administrator, certificate custodian, notification owner, and operations/NRA scope.
  2. Secure channel Transfer the certificate The file and password are never sent by ordinary email, chat, or support ticket.
  3. Holidario Configure and verify Prepare credentials, record the test, and verify one known filing without accepting or paying anything.
  4. Agency Review the result Check last synchronization, operation, reference, and who will handle pending acceptances.
  5. Custody Plan renewal Record holder, expiry, and coordination if the certificate is also used by another service.
Configured does not mean externally validated Saved state does not prove an active account, validity, representation, valid NRA, or acceptance of a notice.
Responsive visual summary; the complete content is also explained in the text.
  • a team administrator;
  • the authorized holder or custodian of the certificate;
  • the person responsible for reviewing registry communications;
  • Holidario support during activation;
  • an adviser or registry contact when scope or representation must be decided.

The integration does not make a Holidario user an authorized representative or decide who may accept a notification.

Information to prepare#

  1. Confirmation that the required external account is active.
  2. A digital certificate with its private key, normally in .p12 or .pfx format.
  3. The exact certificate password.
  4. The holder's identity and internal authorization to use it.
  5. The expiry date and person responsible for renewal.
  6. An initial list of operations and NRAs expected to appear.
  7. A designated person for pending notifications.

Do not attach the certificate or password to a normal support ticket. The file contains an operational identity and must be transferred through the secure onboarding channel agreed for the implementation.

Separate or reused certificate#

Holidario displays an option to copy the certificate already configured for SES Hospedajes when Sede Registradores does not yet have one. The presence of that option does not prove that both services should use the same holder or certificate.

It may be reused only when the responsible person has expressly confirmed that:

  • it is the same file and authorized holder;
  • the external account recognizes it;
  • using it for both services is appropriate;
  • future rotation will be coordinated across both workflows.

The public documentation does not provide steps to copy or replace these credentials. The operation changes sensitive material shared across the team.

What the configured state proves#

The configured state proves that Holidario holds a password and keys extracted from the file. On its own, it does not prove:

  • that the external account is active;
  • that the certificate remains valid;
  • that its holder can access every expected presentation;
  • that a notification was received or accepted;
  • that an NRA is valid.

Guided activation should record a successful connection check, its date, the responsible person, and the operations that were checked.

Safe post-setup check#

After implementation:

  1. open Integrations > Sede Registradores;
  2. confirm the missing-credentials warning is gone;
  3. review the last synchronization date;
  4. compare a known presentation by reference, property, and registry;
  5. confirm that the designated person recognizes Pending acceptance, without accepting anything as part of the test.

Do not use Accept, Mark as paid, or SEPA generation to test the connection. They are later actions with different effects.

If the connection is not ready#

Record the team, time, visible state, and error message. State whether this is initial setup, renewal, or a holder change. Do not include the password, keys, cookies, downloaded documents, or personal data.

Current boundary#

Until the product provides fully guided credential verification and rotation with permissions and recovery, self-service configuration is not a supported journey. Subsequent review is covered by Review Sede Registradores presentations and notifications.

Browse all documentation Press ⌘K or Ctrl+K from any page.

Preparing search…