P4AZ-TRADE Organisation

Your identity. Your signature.

A clear identity.
A trusted starting point.

Prepare your organisation’s details, sign the documents with your certificate provider, then check and publish the files.

  1. 01 Prepare
  2. 02 Sign externally
  3. 03 Assembly
  4. 04 Publish

Process directory

Work directly in one local directory. Active files stay in work; requested changes are prepared in work/new.

Organisation or Person

Each section generates only its own requested files. Sign them externally, then use Assembly to apply signed changes.

Name is a display label. Check the identifier in the official register separately.

Signed additional organisation data

Signed bank-account proof

Signed digital euro account proof (DEAN)

Bind a digital euro account to this subject using the same external qualified signature or seal. Currency: EUR.

Solana stablecoin wallet owner addresses

Saved payment proofs without matching working payloads

These files remain saved. Restore their payloads to edit or verify their detached signatures.

Sign outside P4AZ

Sign exact JSON bytes from work/new using detached XAdES and SHA-256. Keep the subject prefix. Replace only .json with .xml and save the signature next to its payload. The application never accepts a private key. 


      

      

        
Review and apply prepared changes

        

          
        

        
        

        
Prepared changes

        

        
No prepared changes.

        

          Unsigned drafts and unchanged documents stay in place. Assembly does
          not create default.json or server access files.
        

        

          
        

        
      

      

        
Domain default

        

          Select signed proofs to publish their UID references. Account and
          address disclosure is optional; without it, the payer enters the
          destination.
        

        
        
        
        
        

          
        

        
      

      

        
Server access file — shared configuration

        

          Create or validate separately. Assembly does not change this file.
        

        

          
        

        
      

      

        
Local diagnostics

        

          Optional local diagnostics
          

            
          

        

        

      

      

        
Publish and verify HTTPS files

        

          Copy the generated P4AZ directory to the
          signed HTTPS host. Do not upload work or workspace-archives. Remove
          deleted files from the server separately. HTTPS verification does not
          require local publication files.
        

        
        

          
        

        
        

        

        

          Open displayed links from another computer and network. Revocation and
          trusted timestamps are not checked.