Our expectations regarding partner integrity are all encompassing. What this means is that these guidelines are just that, guidelines as a start. Partners are ultimately expected to be trustworthy, regardless of what the guidelines state or don't state.
We expect our partners to take this obligation seriously. Behaviour contrary to this expectation would jeopardize the relationship.
Partners are expected to treat the privacy of their customers with utmost importance and care. Compromising the privacy of a customer by divulging certificate issuance information to third parties is not only a violation of the Certisfy terms and expectations, it could also have legal and criminal implications.
With the exception of legitimate law enforcement inquiries, you should not disclose any information you may have gleaned from issuing a certificate to a customer.
Verification scenarios are numerous and we currently don't have specific guidelines for how to perform verifications, that might change in the future.
We do however expect our partners to perform fair minded and good faith verifications.
By fair minded we mean certificate issuance decisions based on an unbaised verification process. Discriminatory behaviour such as refusing to perform verification or issue a certificate because of prejudice would violate the fair minded expectation.
By good faith we mean you perform reasonable due diligence before issuing a certificate. Issuing certificates without doing meaningful verification of the information would impact the trustworthiness of the resulting certificate and consequently of the Certisfy service.
As with the verification process, we currently don't prescribe pricing for verification services, that too might change in the future.
We expect partners to price appropriately based on a fixed service fee plus the time commitment of any given verification that is performed.
Pricing also has fair minded considerations, don't price in a way that could be deemed biased or discriminatory. In other words charging different people different prices for verifying the same type of information would violate our fair minded verification expectation.
Over time we might provide a more robust pricing guide.
Expired certificates are not trustworthy so it is important that issued certificates have the appropriate expiration date. This is directly connected to the good faith expectation.
For instance if you're issuing a certificate for information on a driver's license and that license would expire in 6 months, then the certificate should be issued for no longer than 6 months.
Certisfy/Cipheredtrust shares revenue for certificates issued by our partners. The default revenue split is 50/50, ie partner gets 50% of revenue generated from issuing certificates.
The revenue split can change at anytime in either direction at the sole discretion of Certisfy/Cipheredtrust.
At the moment Certisfy doesn't specify what the fee should be for performing verification services, this is left at the discretion of the partner and the partner is expected to price approriately.
In the future Certisfy will provide guidelines for pricing of verification services.
Certisfy expects partners to be trustworthy, after all they are trust anchors. This means while a partner is free to charge as they see fit, partners are trusted to process the full transaction through the Certisfy application so appropriate revenue credit sharing is done. Partners who circumvent this expectation risk severing of the relationship.
Certisfy users can purchase stickers to project trust online. In fact when you issue certificates, it is likely that a lot those certificates will be used to create stickers for use online.
User will also use Certisfy to pay for their certificates.
However before we can accept a credit/debit card card from a user, they have to acquire a certificate for it first. This creates a chicken-and-egg situation, how can a user who doesn't currently have a valid credit/debit card certificate pay for any certificate, including a new credit/debit card certificate?
To solve this problem, for credit/debit card certificates, the fee will always be charged to the same card for which the certificate is being issued if a payment method is not tied to the certificate request already.
In other words, when a customer brings their debit/credit card to get a certificate for it, after you've performed the necessary verification, the service fee you specify in the Certisfy app will be charged to that same card.
Once a credit/debit card certificate has been issued, the user should create a payment method in Certisfy that they'll use to request additional certificates. For those subsequent requests, the service fee would be charged to the associated payment method.