Libraries tagged by php form validator

Min class for valid formm in PHP 7.0.0 ou superior

Go to Download

Do validation on fields and args for graphql queries and mutations, and dynamically generate user error types

Go to Download

This documentations describes what the GeoAPI is and how to use it properly. **What is GeoAPI** The GeoAPI allows DPD customers to manage (CRUD) their shipments and shipment related data. The main purpose of the API is to provide the customer the means for: - Creating and managing new shipments - Ordering pickups for parcels - Printing parcel labels - Listing all available shipping services - Validating shipping routes It also provides methods for listing your pickup addresses and the details of individual parcels. Each user is assigned a user account under which he is able to track multiple customer DSWs (customer numbers). You as a customer can use a single GeoAPI account to send shipments under multiple DPD customer numbers.

Go to Download

Spikkl API client wrapper for Laravel

Go to Download

Client for SMS.CX API

Go to Download

A pure PHP SQL (non validating) parser w/ focus on MySQL dialect of SQL - Modernized for use with composer practices and Laravel 5+

Go to Download

Create whitelist and blacklist for the url route.

Go to Download

A brief overview of the API versions: v0: This version is solely for testing and does not interact with the database, nor does it involve any validation. It simply serves mock data. v1: This is the official version of the LtiSaas API, intended for production use. Please be informed that when testing version v0, the HTTP Access-Token header should be set with the value 'dummy'. Also, please note that the API has a limit of 2500 results per response. Additionally, all webservices support both POST and GET requests. However, the POST method is required when uploading files.

Go to Download

Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs. Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability for tokenised payments. ## Compliance and Security Overview Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is designed with stringent security measures and compliance protocols to safeguard sensitive information and meet the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. ### Key Compliance and Security Measures * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats. ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations. For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application. Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution.

Go to Download

A library for determining if an email or set of emails is valid and has an actual mailbox.

Go to Download

A very simple, light weight PHP client for validating any EU VAT number against the official europa.eu API

Go to Download

Simple and fluent input validation for PHP >= 5.3.

Go to Download

ioValidate data validation for PHP and JavaScript

Go to Download

A PHP library for whitelisting, validating, and canonicalizing HTTP request data against a JSON Schema

Go to Download

A simple validation library for PHP 5.4+

Go to Download