Workflow of Regenerative Finance for Operational Sustainability

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 2 Minuten Lesedauer
  • The Regenerative Finance for Operational Sustainability follows a workflow to set up Hedera Guardian users, submit an application, and initiate a new issuance request from the device form.

    The workflow of the Regenerative Finance for Operational Sustainability application is as follows:

    1. Registry synchronizes policies and policy roles with the ServiceNow table.
    2. The registry synchronizes tokens representing renewable energy credits (RECs) and token balances. Token balances are integer numbers representing MWh of green energy generated and tokenized.
    3. The registrant selects the required policy and opts for the registrant role by selecting the Choose Registrant Role button on the policy form.
    4. The registrant fills out the Submit application form for the subscribed policy by selecting the New application button, supplying the registry with the know your customer (KYC) information.
    5. Either the registrant or the registry synchronizes the application form data with Hedera Guardian.
    6. The registry verifies the application request data and either validates or rejects the application by using the Validate or Reject button on the application form.
    7. The registrants associate themselves to the policy-deployed token. A token ID, in the format 0.0.123456, represents Hedera Guardian native tokens and is shown as a related list of the policy. Registrants can open the token balance record of themselves for that policy and associate themselves with the token by selecting the Associate token button.
    8. After the registrant completes the association, the registry must authorize the specific token's KYC for the registrant by selecting the Grant KYC button on the token balance form. Both the steps of associating and granting the KYC permit to the registry or the issuer to mint the token to the registrant's account represented by an account ID in the format 0.0.123456.
    9. After the registrant is validated, they can register their device under the REC policy by selecting the Register device button. All necessary devices and device farms information must be provided.
    10. Either the registrant or the registry synchronizes the device form data with Hedera Guardian.
    11. After the device registration is submitted, the registry can either validate or reject the request, by selecting the Validate or Reject buttons on the device form.
    12. After the device is validated, the registrant can submit an REC issuance request for a specific time period and for a specific amount of KWh generated by a device and farm, attaching all relevant validation information. This submission can be done manually using a form or automatically using a REST API endpoint.
      • Manual issuance request: The registrant can initiate a new issuance request from the device form providing all pertinent information.
      • Automatic issuance request: You can use an API to issue a request. For more information about the API, contact your system administrator.