Merchant-Specific BIN Blocking Rules

Merchants can now configure BIN-based block rules tailored to each account. If a transaction includes a blocked BIN, our system returns a clear, branded decline response indicating it was blocked due to BIN rules. This enhances control and security for merchants.

New Integration: PaymentLync Now Available on the Portal

We’ve added a new “Notification Settings” section to the Portal, now available under the Settings menu. This feature gives users greater control over the types of email notifications they receive.

Key Capabilities:

• Subscribe or unsubscribe from specific notification topics.
• Choose which team members should receive each type of notification.
• Toggle individual topics on or off based on your preferences.

Changes made in the Portal take effect immediately, ensuring your communication preferences are always up to date.

New API Endpoint: Configure JPMorgan (Paymentech) for Merchants

We have introduced a new API endpoint that enables merchants to configure JPMorgan (Paymentech) as a payment processor directly through the API. This addition streamlines the setup process, allowing for efficient integration and management of JPMorgan (Paymentech) within merchant accounts.

Combined Cardholder Name Field

To improve developer experience, our API now supports a combined billingFullName field alongside the existing billingFirstName and billingLastName parameters. Merchants can now choose one of two mutually exclusive formats:

• First/Last Name – using billingFirstName + billingLastName (existing method)
• Full Name – using billingFullName (new alternative)

Exactly one naming format must be provided per request. This update simplifies integration for merchants who collect name data as a single string.