Apparently some installations require a payment to validate a certificate.
To enable this, we would have to make the URL configurable. The URL would then send the VC URL as an encrypted parameter to an API integration for an external payment gateway. When payment is completed on the gateway, then the payment system could forward the user back to verify the VC.
We should make the URL configurable technically in populate-default-config perhaps with named URL params or perhaps with a redirectURL param, so that technically a microservice could be developed that interrupts the request with a payment gateway and on successful payment, we could redirect the user to the verified certificate.
In this community discussion an interesting question was raised:
Do you embed a payment algorithm in the QR code that gets them to first make payment, the payment is verified then they are issued with certification results ??
Apparently some installations require a payment to validate a certificate.
To enable this, we would have to make the URL configurable. The URL would then send the VC URL as an encrypted parameter to an API integration for an external payment gateway. When payment is completed on the gateway, then the payment system could forward the user back to verify the VC.
We should make the URL configurable technically in populate-default-config perhaps with named URL params or perhaps with a redirectURL param, so that technically a microservice could be developed that interrupts the request with a payment gateway and on successful payment, we could redirect the user to the verified certificate.