|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Card on File (CoF) (ranked 3778 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/pXiXq19_ETFnUa0DT7Rop_card_on_file__cof__json.jsonGENERAL INFORMATION
API documentation for Card on File (CoF) integration with Visa CoF for the following use case: A client is at an online page and needs to checkout in order to buy a product. For that, instead of giving away sensitive data such as PAN, expiration date and the CVV of the credit card, tokenized data will be used, including a Dynamic CVV for each transaction. This tokenized data is requested through the Visa Card On File solution (CoF). For authentication it's required to provide authentication credentials (system account ID and password) passed in the HTTPS Basic Authorization header. Also, a SSL/TLS X.509 Visa-approved Client Certificate linked to the identity supplied in the Authorization header. That data should be provided by CoF customer for each environment.
Contact
- Name: ogaravito@yellowpepper.com
SECURITY 5/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP: We didn't find any OWASP vulnerability.
PERFORMANCE 0/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 5,000 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 2/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 2.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!