3 posts tagged with "PayTabs"

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​

Added​

• Provisioning API: Added processing:copy-customer-data-from-customer-profile-transaction to the connector settings.

Features​

Changed​

• User Management:
  • Removed deprecated ACL abilities connector.WorldlineOgone.PostFinanceCard and connector.WorldlineOgone.PostFinanceEFinance.
  • Migrated existing deprecated ACL abilities to connector.IngenicoDirect.PostFinancePay.

Added​

• Connector Configuration: Add new connector setting Customer Data: Copy from customer profile transaction. If activated the shopper's information is added from the transaction that was used to create a customer profile.

Fixed​

• Job Configuration: Fixed an issue that could occur when saving Global Job Schedules.
• Post Processing Jobs: Fixed the post-processing filter Transaction is not referenced in any job of this Job Type, ensuring it now correctly picks up transactions already collected by other job types.
• Post Processing Jobs: Fixed the bug where the default state for newly created job schedules would be scheduled instead of Manual trigger only.
• Transaction List: Fixed the advanced search to also filter for the meta_connector_guid when searching for transactions of a connector.
• Transaction List: Fixed handling operators IS_EMPTY and IS_NOT_EMPTY for the advanced search.

Adapters​

Changed​

• dLocal (DLO): Added support for settlement handling.
• Klarna (KLW): Updated and restructured the documentation according to our latest guidelines.
• PayPal Complete Payments - PPCP (PPCP-EP1-CC): Added support for the PayPal Advanced Credit Cards and Debit Card (ACDC) method.
• PayTabs (PAYT-EP01-CCRD): Added support for the redirect credit-card payment method.
• PXP (PXP-EP1-INST): Added support for Discover credit cards.
• Straight2Bank Pay (STRAI): Added the configuration option daysOffset to delay data fetching a certain number of days.
• Worldpay (WOR-EP1): Added support for chargeback handling through webhooks.

Fixed​

• Adyen (ADY-EP1, ADY-EP2, ADY-EP3): Fixes handling of second chargebacks for Adyen settlements.
• Alipay - Ant Group (ANT-EP1-ALI): Limit retries of failed transactions to three attempts.
• Global Payments (GBP): Fixed specifying the settlement amount.
• PAYONE (PASIX): Fixed handling of negative fee amounts in settlements for interchange fees of refunded transactions.
• PXP (PXP-EP1-INST): Fixed incorrectly disabled partial capture, partial void, and incremental authorization.

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​

Fixed​

• Batch Upload API: Fixed a number of issues with the Batch Upload API:
  • Fixed a bug that generated an incorrect output format when an error occurred.
  • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
  • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
• Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features​

Changed​

• UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added​

• Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed​

• Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
• Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
• Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
• User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added​

• Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
• Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
• PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
• Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
• Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed​

• Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
• Adyen (ADY-EP3-RIV):
  • Added support for partial captures for the Riverty payment method using Adyen Checkout.
  • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
• Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
• Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
• checkout.com (CHE):
  • Fixed the handling of settlements for transactions with multiple partial captures.
  • Multiple fees are now supported for a single transaction in the settlement report.
• Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
• Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
• MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
• Nuvei (NUV-EP2): Enabled support for partial captures.
• Zona Virtual SA - Zonapagos (ZONA-EP1):
  • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
  • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
  • Fixed the default error mapping.
  • Added mapping for the error when a payment cannot be found.

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.