Simulate charging session

Authentication: The signature attribute on the DID document is used to authenticate the validity of the fetched DID from the blockchain node. The public key of the authority who signed the document must be used to authenticate if the document was truly authorized by the authority.

Verification: The provider (charge.xyz) has to be verified before service is requested by the consumer (Mobile application). This is done by the consumer sending plain hex data to the P2P Server. The plain data payload is signed by the P2P Server using the provider's private key and returns the signature to the consumer. The consumer verifies the returned signature using the provider’s public key. Transactions can only proceed after a successful verification of the provider.

Payment: Service delivered transactions containing the payment details are created on the blockchain node after a successfully completed charging session. Two multisig transactions are also created for the consumer (Mobile Application) to approve. Upon approval, funds are moved from the multisig wallet to the respective beneficiary account. Refunds are also made if the amount spent is less than the amount deposited on the multisig wallet.