6 posts tagged with "KCP PC"

Gateway Features​

Changed​

• Connector Settings: Add bracket notation for the connector setting Field Expression Operation for the target field extraData to allow dashes in the key name.
• Network Tokenization: Add an additional network token configuration to the existing setting to allow creating network tokens when processing subsequent transactions.

Fixed​

• Network Tokenization: Fix an issue where disabling network token processing also disabled network token creation.
• Transaction Details: Fix a bug where transaction logs are not properly formatted.
• Transaction Processing: Fix automatic capture to also work for failover transactions.
• UI: Fix the customer profile list view showing a wrong total number.
• Virtual Terminal: Add missing translation in the Pay-By-Link UI.

Gateway Adapters​

Changed​

• Adyen (ADY): Add handling of Merchant Advice Code from callback notifications.
• Braintree (BRA-EP1-SWI): Add support for Swish, a Swedish mobile payment method that allows customers to make real-time payments using their phone number and banking app.
• checkout.com (CHE-EP2-BIZ): Add the payment ID in the callback notification as psp:bizumPaymentId.
• dLocal (DLO-EP1): Add a new optional configuration setting which allows sending a custom X-Dlocal-Payment-Source header.
• eMerchantPay (EME-EP3-CC): Add support to automatically migrate existing recurring card subscriptions from the legacy platform to the Genesis platform without requiring cardholders to re-register.

Added​

• NaverPay (NAV-EP1): NaverPay is a South Korean digital wallet and online payment platform by Naver Corporation. It enables users to make seamless payments across e-commerce sites, apps, and offline merchants. The platform offers secure transactions, loyalty rewards, and easy integration for businesses.

Fixed​

• KCP PC (KCPPC): Add a temporary configuration setting which should fix issues with refunds.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Fix an issue with the wallet reference handling.
• Redsys (RED-EP2-BIAPI): Fix an issue where the authCode is not included in the callback notification.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway Features​

Changed​

• Meta connector: Remove the option to change the type of an existing meta-connector (routing / multi-method) to prevent unexpected behavior and ensure consistent functionality.

Added​

• Connector Settings: Add a new connector setting Add Hard Decline Error Codes which allows specifying additional error codes that prevent failover transactions.

Fixed​

• Connector Settings: The connector setting Accept postbacks from other connectors will now properly ignore meta-connectors if provided in the list.
• Provider Settlements and Reconciliation: Fix an issue where a transaction was not settled correctly if a fee-only settlement in a different currency was received before the actual transaction settlement.
• Transaction Processing: Transactions with an expired or non-existent transaction token will no longer be retried.
• User Management: Fix a minor display inconsistency in the permissions list when configuring roles.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4-CC): Add additional data mappings and documentation.
• Amazon Payment Services (AMAZO): Add settlement handling.
• Amazon Payment Services (AMAZO-EP1-NAP,AMAZO-EP2-NAP): Add support for the new payment method NAPS. NAPS is Qatar's national debit card network which offers a convenient, card-independent local payment method, enabling seamless, real-time transactions between businesses and Qatari shoppers across participating Qatari banks.
• Bangkok Bank (BB): Adjust settlement handling to support a new VAT format with VAT provided once per file instead of per transaction.
• Nuvei (NUV-EP1-PSE): Add support for the new payment method PSE. PSE (Pagos Seguros en Línea) is a popular real-time online bank transfer payment method in Colombia that allows users to pay directly from their bank accounts.
• Worldpay (WOR-EP1-KLAPN): Use a default Order Line Item if none is provided, to meet mandatory requirements by Worldpay for Klarna.

Added​

• Digit Secure (DS-EP1-T2P): New push adapter with payment method Tap2Pay.

Fixed​

• Cybersource (CYS): Fix parameter typo from extraData.reconciliationId to extraData.reconciliationID (captialize D in ID).
• KakaoPay (KAKAO-EP1-KAKAO): Fix incorrect mapping of error responses.
• KCP Mobile (KCPMO): Fix issue with settlement handling for refund transactions.
• KCP PC (KCPPC): Fix issue with settlement handling for refund transactions.
• Simulator: Fix issue where payment.js did not work with the Simulator adapter.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

Gateway Features​

Fixed​

• Job Configuration: Fix a bug in the post-processing job configuration where endpoint URL validation in the Send document to endpoint exporting configuration incorrectly restricted URL paths to lowercase only.

Gateway Adapters​

Changed​

• KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Add extra data to callback and API response, including card acquirer code (extraData.acqu_cd), card issuer code (extraData.card_cd), payment method (extraData.pay_method), truncated PAN (extraData.card_no), and bank code (extraData.bank_code).
• PayPal Complete Payments - PPCP (PPCP-EP1): Add chargeback protection details to API response, including seller protection status (extraData.seller_protection_status), dispute categories (extraData.seller_protection_dispute_categories), and PayPal account status (extraData.paypal_account_status).
• Stripe (STRV2): Add support for account funding transactions (AFT).
• Worldpay (WOR-EP1-CC): Add documentation about the extraData.refundAuthorisationReference parameter returned in callbacks.

Fixed​

• PXP (PXP-EP1-INST): Fix a typo in an error message.
• Worldline (ING-EP1, ING-EP2, ING-EP3, ING-EP4, ING-EP7): Fix chargeback handling in the settlement and reconciliation parser.

API v2​

Added​

• APIv2’s NetworkToken endpoints now return an error if multiple Network Tokens exist for a single token, requiring the new tokenReferenceId parameter to specify which one to use.

Payment Services v2​

Added​

• Add Merchant Advice and Brand Auth Response code mappings to AdyenDirect, FirstDataIPG, and Orbital gateways for additional insights on how to handle failed transactions.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

API​

Added​

• Push API: Add transactionSubType to the /chargeback endpoint.

Features​

Changed​

• Risk Profile: Add parameters to Count Chargebacks Risk Engine Strategy to include or exclude RDR transactions.

Added​

• Account Updater: Add connector setting Account Updater: Snooze Updates for Status Contact-Cardholder to skip future account updater runs for the response status Contact-Cardholder for up to 36 months.
• BI Data Source: Add field subType to the BI Data Source enabling better transaction distinction and filtering of RDR transactions.
• Dashboard: Add a filter for subType to Trend: Compare Chargeback Rate dashboard widget.
• Post Processing Jobs: Add Transaction Type and Transaction Subtype columns to the exported email of the Send Reports to Merchants post-processing job strategy.
• Risk Profile: Add Is Credit Card Prepaid and Is Credit Card Reloadable risk rules.
• Transaction List: Add field subType to the Advanced Filter enabling better transaction distinction and filtering of RDR transactions.

Fixed​

• Transaction Details: Fix Load More button for transaction logs exceeding 100 entries.

Adapters​

Changed​

• Bangkok Bank (BB): Add optional PGPPrivateKey and PGPKeyPassPhrase fields to the data fetcher's Extra Data, to support PGP-encrypted settlement file decryption.
• checkout.com (CHE): Remove the requirement to send customer.bic or customer.extraData.bic fields and the requirement to perform a separate /options getIssuers call.
• CMI (CMI): Add support for settlement handling.
• Nuvei (NUV-EP1): Remove the requirement to send customer.email, this is now an optional field.
• PayTabs (PAYT-EP01): Add connector config Enable iframe mode to support checkout via iFrame.
• PPRO (PPR-EP1): Add a configuration option for alternative PPRO return mode.
• Worldpay (WOR-EP1): Add support for chargeback notifications.

Added​

• Fiuu (FIUU-EP1): Add the Fiuu (formerly Razer Merchant Services) adapter with support for debit and refund transactions. Fiuu is Southeast Asia's leading payment gateway, enabling seamless payments for businesses and individuals.
• JPMorganChase (CHA-EP2): Add the J.P.Morgan Commerce Platform adapter with support for debit, preauthorize, (partial) capture, (partial) refund, and recurring transactions. J.P. Morgan is a leader in financial services, offering solutions to clients in more than 100 countries with one of the most comprehensive global product platforms available.

Fixed​

• KakaoPay (KAKAO-EP1): Add extraData.paymentMethodType field with possible values MONEY or CARD.
• KCP Mobile, KCP PC (KCPMO-EP1, KCPPC-EP01): Fix live endpoint.
• PayPal Complete Payments - PPCP (PPCP-EP1):
  • Fix missing prepareCallEndpoint for the multi-method payment connector.
  • Ensure PPCP payment method availability in the multi-method payment connector.
• SIA (SIA-E01): Fix setting transaction status to error on failed 3DS authentication, enabling follow-up THREEDSAUTHORIZATION2 call.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.

API​

Changed​

• Status API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.
• Transaction API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.

Fixed​

• Transaction API: Fix an issue where missing wallet data fields (walletOwner, walletReferenceId, walletOwnerFirstName, walletOwnerLastName, walletOwnerCountryCode) could cause an error. These fields are now treated as not provided.
• Transaction API: Implement stricter currency format validation, requiring merchants to send amounts with the correct number of decimal places for each currency (e.g., EUR: 9.99 or 9.9, JPY: 5 or 5.00). If the correct format can't be provided by merchants, the tenant can be configured to round amounts commercially according to our currency definition. These settings are inherited by sub-tenants. For assistance in configuring this setting, please contact your customer success manager.

Features​

Added​

• BI Data Source: Add a new data field, sub_type, for transaction subtypes related to rapid dispute resolution (RDR) in the BI data source.
• Login: Store redirect data in the URL to ensure that after multi-tab logout and login, each tab returns to the originally requested page instead of the landing page.
• Token Count Aggregation: Add filters to the post-processing step Calculate Token Count, allowing users to:
  1. Exclude Merchants having this Job Types scheduled
  2. Exclude Connectors having this Job Types scheduled
  3. Only Methods.

Fixed​

• Connector Configuration: Fix a bug in the transaction expiration process to ensure the Ignore Global Setting connector setting is respected whenExpire Pending Transactions or Expire Transactions is enabled.
• Connector Configuration: Fix an issue where a valid value of 0 for the connector setting Postback Queue: Set maximum number of retries was incorrectly treated as missing or invalid. The system now properly accepts 0 as a valid input.
• Documentation: Fixes the API authentication examples by removing the newline character that was incorrectly included in the base64-encoded concatenation of the username and password.

Adapters​

Changed​

• 2C2P (2C2P-EP1-2C2PB): Update the payment channels by removing Thanachart Bank and adding the new TMBThanachart Bank following the merger with TMB Bank.
• KCP Mobile, KCP PC (KCPMO, KCPPC): Add support for settlement handling.
• Mercado Pago (MERPA-PROD): Adds a new header to the payment request containing the DeviceData. This allows the collection of the DeviceID when redirecting the user to the Hosted Payment Page (HPP).
• PXP (PXP-EP1-CC): Map the field ProviderExternalID to acquirer reference number (ARN).
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC (extends STRV2-EP1-CC)): Add the ability to pass requestExtendedAuthorization as extra data to Stripe to request an authorization to be extended for up to 30 days.
• Worldpay (WOR-EP1): Update AFT documentation.

Added​

• KakaoPay (KAKAO): Add the KakaoPay adapter with support for debit, refund and partial refund transactions. KakaoPpay is a South Korean fintech company specializing in digital payments, money transfers, and financial services.

Fixed​

• KCP Mobile (KCPMO-EP1):
  • Use Code as fallback response code if res_cd isn't available.
  • Fix an issue where the wrong value (payment method ID instead of payment method name) was sent for the pay_method field.
• Nuvei (NUV-EP1-CC): Fixes the fail-over transaction to Nuvei by ensuring that the firstPaymentDoTransactionId is only set if the related transaction was created through Nuvei; otherwise, it is omitted to prevent rejected transactions.
• PXP (PXP-EP1-INST): Fix wrong format of expiryMonth and expiryYear in adapter result.
• Zona Virtual SA - Zonapagos (ZONA-EP1): Fix status retrieval handling to consider only the latest status, as recommended by the PSP.

Please note that some of the features mentioned in the release notes may initially be available only within our sandbox environment for testing purposes. These features will be made available in the production environment upon successful testing and approval.