Comunidad

Soporte

Github

Plumaa ID

Avanzado

Referencia de API

Webapp

Agenda una demo

A certificate is a digitally signed statement from one entity (the issuer) that
another entity (the subject) has a given identity. The issuer is a
Certificate Authority certified by Banxico, and the subject is typically a
person or organization ("persona física o moral" in Spanish).

AWS S3 URI path to the certificate's PEM data.

A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.

SHA256 message digest of the issuer's certificate.

A field whose value conforms with the standard mongodb object ID as described here: https://docs.mongodb.com/manual/reference/method/ObjectId/#ObjectId. Example: 5e5677d71bdc2ae76344968c

The certificate's issuer. This is the entity that issued the certificate, and
is a Certificate Authority certified by Banxico.

The latest date at which the certificate is valid.

The earliest date at which the certificate is valid.

The certificate's public key. This is the public key that identifies messages
signed by its corresponding private key.

Whether the certificate has been revoked by the issuer.

The certificate's serial number, as a hexadecimal string. This is a unique
identifier for the certificate, and is assigned by the issuer.

The certificate's subject. This is the entity that the certificate is
attesting to, and is typically a person or organization ("persona física o
moral" in spanish).

The version of the X.509 standard that the certificate conforms to.

Information required to claim a document in the Endorser contract.

The address that signed the authorization to claim the document.
Needs to have privileges within Plumaa ID's AccessManager contract.

The chain ID where the claim is authorized.

Authorization signature. It's an EIP-712 signature of the hash of the claim and the initial claiming address.
* Domain Separator: `EIP712Domain(string name,string version,uint256 chainId,address verifyingContract)`
* EIP-712 Type: `MintRequest(bytes32 leaf,address to)`

The organization that the subject is a member of.

The subject that is a member of the organization.

The `BigInt` scalar type represents non-fractional signed whole numeric values.

IOU content is a string that represents an IOU.

Latitude coordinates where the IOU is created.

Longitude coordinates where the IOU is created.

An Issuer is a Certificate Authority certified by Banxico to
issue digital signature certificates to Mexican citizens.

AWS S3 URI path to the issuer certificate's PEM data.

Name of the organization or company.
"Razón Social" in Spanish.

Name of the unit within the organization.
"Unidad Organizacional" in Spanish.

The issuer's certificate public key. This is the public key that identifies messages the issuer has signed
a certificate for a subject.

JSON content is a JSON object that can be signed.

Combined merkleized conservation strategy.

Algorithm for hashing the internal nodes. The document hash is also re hashed using this algorithm to avoid
second pre-image attacks. See https://en.wikipedia.org/wiki/Merkle_tree#Second_preimage_attack

The proof that the root existed at the time of the transaction.

A field whose value is a hexadecimal: https://en.wikipedia.org/wiki/Hexadecimal.

Merkle root included in the transaction. It should be the same as the one
computed from the merkle proof and the leaf hash.

The NOM 151 provider that issued the timestamp for the merkle root.

The transaction hash. Any transaction that includes an operation with this hash is valid.
It could be either a transaction to another service (eg. The Witness contract), but it may be upgraded
in the future.

An Organization represents an tenant in the Plumaa infrastructure. All paid
resources are associated with an Organization. Organizations can have multiple
certificate members.

Email address of the organization. Updates and notifications will be sent to this address, as well as the billing information.

The logo of the Organization. This is the logo that will be displayed to
users when interacting with signature requests from this organization.

The name of the Organization. This is the name that will be displayed to
users when interacting with signature requests from this organization.

PDF content is a PDF document that can be signed.

Policies define the behavior of the resources in the organization.

Defines the policies for signatureRequests.

An RSA public key, as defined in RFC 3447.

The public key's modulus, as a hexadecimal string.

The public key's exponent, as a hexadecimal string.

Quota defines the resource limits for an organization.

The amount of grouped NOM151 certificates available to the organization.

The amount of NOM151 certificates available to the organization.

Raw content is a string that can be signed.

A signature request is an entity that represents a piece of data that needs to be signed by a user.

Key for sharing the sharing the signature request. Can be used to access the signature request without authentication.

Whether the document is a draft or not.
A draft signature request won't allow invites to sign and will skip processing notifications.

Whether the document is finalized or not.
A finalized request won't allow new invites and won't process any new notifications.

The organization requesting the signature.

Amount of invites that have not signed the content.

Amount of invites that have rejected the content.

Date when the signature request was rejected. Only present if rejected.

Amount of invites that have signed the content.

Witness that attest the content using a merkle proof

A signature request invite is an invite to sign a signature request.
It links a signature request to a subject and it stores its corresponding
signature and the link to the certificate that the signature belongs to.

The certificate this invite was signed with.

The OCSP response from checking the certificate against the CA.
ASN1 encoded as a hexadecimal string.

Date at which the signature request invite was rejected. Only present if rejected.

The signature from the certificate as a hexadecimal string.

The signature request this invite is linked to.

Date at which the signature request invite was signed. Only present if signed.

The status of the signature request invite.

Witness that attest the signature using a merkle proof

SignatureRequestPolicies defines the policies for signatureRequests.

Type of conservation strategy to use by default at signature request readiness (ie. when draft is false).

A subject is a person or an organization ("persona física o moral" in Spanish)
identified by a certificate.

EVM address of the subject.

Each account is a smart account that includes a single signer contract deterministically created from a factory deployed through [xdeployer](https://github.com/pcaversaccio/xdeployer)
so that every signer contract has the same address in all EVM networks. This signer contract is an implementation of a custom ERC-1271 interface that allows
the RSA key to sign on-chain. Signers can be deployed trustlessly by anyone since they're controlled by the account owner.

The smart account is created from the [Safe{Wallet}](https://github.com/safe-global/safe-deployments/blob/main/src/assets/v1.4.1) factory and includes a setup call to the RSA signer factory,
deploying the signer contract who'll own the account. The account factory is already deployed on all networks with the same address so that the account can be created deterministically
in all EVM networks too

This setup allows the following properties:

* The signer contract factory can create the same signer contract in all EVM chains for the same RSA key
* The account can be created deterministically in all EVM chains because it depends on the signer contract address and the RSA public key

In this way, the EVM address is completely abstracted from the EVM network, so we just need to keep a single address.

RFC of the subject. It is a unique identifier for persons and organizations in Mexico.

The push notification token associated with the certificate. Used for sending notifications to the user.

CURP of the subject. It is a unique identifier for people in Mexico.

Invite for the subject to sign Plumaa own terms and conditions.

A witness is an entity representing a proof that a document existed at the time.
It is used to comply with the law requirement of data conservation.

The algorithm used for hashing the document.

If the witness has been claimed by the initial owner.

Information required to claim a document in the Endorser contract. It is only present if the witness is processed and restricted
to the initial owner.

Subject designed as the first in the endorsement chain. Only a member of the operating organization can set this field.
Once set, our on-chain relayer will submit a proof of endorsement to the Witness contract so that the corresponding
token can be minted by the user later on the application.

Signature Request the witness is associated with.
May not be present if the witness was via the API.

Earliest date when the hash was witnessed by any strategy. Unspecified if the witness is not processed.

[Witness](https://witness.co/) conservation strategy.

The index of the leaf to be verified in the tree.

The root of the tree the proof is being verified against.

apiKey

OrganizationMember is a join table between Organization and Subject.
It is used to track which users are members of which organizations.

La mejor plataforma de firmado electrónico y tokenización de activos

¡Bienvenido a Plumaa ID!

Comienza a usar Plumaa ID y sacarle el jugo a tu e.firma

Inicio rápido

Aprende cómo firmar documentos con Plumaa ID

Firma documentos

Crea representaciones digitales de tus activos con propiedades de integridad, autenticidad y no repudio

Tokeniza activos

Envía y recibe pagos en dólares digitales de forma inmediata con la seguridad de tu e.firma

Pagos transfronterizos

Aprende cómo puedes conectar tu e.firma con aplicaciones descentralizadas

Interactúa con apps

Descubre cómo trabajar con documentos en Plumaa ID

Gestión de documentos

Descubre cómo verificar la identidad de tus usuarios con Plumaa ID

Verificación de identidad

Descubre cómo Plumaa ID se puede utilizar para autenticar a tus usuarios

Autenticación

Descubre qué es Plumaa ID y cómo puede ayudarte

¿Qué es Plumaa ID?

Respuestas a preguntas frecuentes sobre Plumaa ID

Preguntas frecuentes

Fundamentos

Entiende los términos que utilizamos en Plumaa ID

Terminología

Descubre porqué Plumaa ID existe y cuál es nuestra filosofía para crear valor a través de la identidad digital

Manifiesto

Conceptos avanzados

Organizaciones

Aprende sobre cómo Plumaa ID gestiona documentos

Documentos

Aprende el marco sobre el que se tokenizan activos con Plumaa ID

Tokenización

Aprende cómo funciona la billetera de Plumaa ID

Wallet

Aprende sobre firma electrónica, sus tipos y cómo se compara con una firma autógrafa

¿Qué es una firma electrónica?

Descubre lo que define a una firma electrónica avanzada y cómo se diferencia de otros tipos de firma electrónica

¿Qué es una firma electrónica avanzada?

Aprende sobre los Proveedores de Servicios de Certificación (PSCs)

Proveedores de Servicios de Certificación (PSCs)

Aprende sobre la conservación de mensajes de datos

Conservación de Datos

Aprende sobre el testigo del sistema de información de Plumaa ID

Testigo

Aprende sobre el endosador del sistema de información de Plumaa ID

Endosador

Creates a new OrganizationLink. Only available if the caller bears an access token issued to the certificate of the linking subject.

Deletes an OrganizationLink. Only available if the caller bears an access token issued to the certificate of the linking subject or for members of the organization.

Other

Certificate

Issuer

Organization

SignatureRequestInvite

SignatureRequest

Subject

Witness

Wallet

Endorsable

EndorseEvent

ApiKey

OrganizationLink

OrganizationMember

Post organization member

Authorizations

Query Parameters

Body

Response