News & Updates

We’re always looking for ways to make working with ConnectPay simpler for your team. Additionally, we’re happy to introduce the ConnectPay BaaS dashboard. Dashboard overview You can track every customer you refer to ConnectPay in one place. From the first ID check to a live client, all data is visible. Additionally, this dashboard offers a

On October 20, 2026, two critical remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) were disclosed in PHP, a component utilized in our Developer Portal infrastructure. Rated as critical (CVSS 9.2), these vulnerabilities could theoretically allow an unauthenticated attacker to execute code remotely. As a preventive measure to guarantee the absolute security of our developer ecosystem,

Upcoming changes and enhancements to the ConnectPay BaaS APIs. Please review these updates carefully, as they include both soft changes and breaking changes. 1. Soft Change: Expansion of the idvDeclineReason Enum Target environment dates: To provide you and your customer support teams with more precise reasons for Identity Verification (IDV) declines, we are significantly expanding

We’re excited to share some updates on our API collection. Driver license is now supported during onboarding Driver license as acceptable ID document type is introduced to BaaS APIs. Your clients can now submit a driver’s license as a valid identity document across our onboarding flows. To be accepted, the driver’s license must meet the

We’re excited to share some updates on our API collection. Please note that these changes are not breaking changes to your system. BaaS Clients API collection These changes are in stage environment from February 17, 2026 Production release for this change is planned for February 24, 2026 Get BaaS clients API Non-breaking change Optional pagination available: if

What has changed Previously, only CA-issued certificates from approved certificate authorities were accepted for mTLS authentication. Effective immediately: Please note: This does not affect the Accept Payments (Merchant) API flow, which continues to use the Request Signature mechanism rather than mTLS. Also, the PSD2 API flow will require a certificate issued by a certified authority.

We would like to inform you about an upcoming update to our API security standards designed to enhance your data protection and maintain compliance with industry best practices. Please review the details below and take the necessary actions.  What’s changing?  api.connectpay.com: api2.connectpay.com: You can test your integration on our staging servers, where TLS 1.1 was

We’re excited to share some updates on our API collection. Please note that these changes might be breaking changes to your system.  

We’re excited to share some updates on our API collection.

RELEASED TO PRODUCTION: BaaS Merchant payments and providers API collection Initiate Google Pay top up New endpoint for baas partner to allow their clients topping up IBAN account by Google Pay digital wallet Get Google Pay gateway credentials API New endpoint for baas partner to receive Google Pay credentials for top up feature Create BaaS