Skip to main content

4 posts tagged with "China UMS"

View All Tags

Gateway — v.24.10

API

Added

  • payment.js: In addition to styling the CVV and card number fields on checkout pages, it is now also possible to apply styles to their placeholder text.

Features

Changed

  • Provider Settlements and Reconciliation: Updated the data fetcher to:
    • Validate input data
    • Inform users when the data fetcher is saved with missing or invalid data
    • Allow the data fetcher's interval to be set to 0 (no retrieval). This is now also the default value for new data fetchers.

Added

  • Audit Log: Added the ability to export user management audit logs that includes information on users, such as the date the user was added, modified or deleted, their last login and the tenant the user is assigned to. These export logs can be found under Security Center on the Audit Log Export tab.

Fixed

  • Documentation: Updated the Schedule API documentation to address incorrect information.
  • Documentation: Fixed an issue with the signature testing tool that would cause it to generate an incorrect signature due to a difference in how the URL path is generated compared to the IXOPAY gateway.
  • Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that would result in an error that the chargeback could not be found. This was caused by postback notifications that contain the same reference ID for both capture and preauthorization transactions.
  • Risk Profile: Fixed an issue that would prevent Starter and Growth users from editing the risk ruleset. When attempting to edit the ruleset, an error message was displayed that only one risk profile is allowed.
  • UI Navigation: Fixed an issue with Apple Pay and Google Pay transactions showing the incorrect icon for the token type.

Adapters

Changed

  • PAYONE (PASIX):
    • Fixed an issue with mapping fees for SIX via the E-Link adapter. New mappings have been added for the scheme fees and interchange fees to address this.
    • Updated the handling of settlements to use the current date and time as the fallback value for the payment date and settlement number if this value is not present. This was the case if the refunded amount was larger than the captured amount. Furthermore, if a payment number is available, this is used as the payment reference.

Fixed

  • China UMS (UMS-EP1-H5): Fixed an issue with missing adapter-related data in the postback notification.
  • Paysafecard (PSC-EP1): Fixed an issue that would cause refunds to fail due to the adapter transaction ID being truncated.

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 — v.24.5

Features

Changed

  • UI Navigation:
    • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
    • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added

  • BI Data Source: Scheme IDs are now available for post-processing.
  • Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
  • Fee Management: Added the ability to specify the customer's billing state for fees.
  • UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed

  • Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
  • UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
  • Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters

Changed

  • American Express (AMX-EP1-AMX): Added support for Apple Pay.
  • China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
  • Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
  • HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
  • Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
  • PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
  • SIA (SIA-E01): Added support for void and partial captures.

Added

  • Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
  • Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed

  • Adyen (ADY):
    • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
    • Fixed an issue with settlement notifications that caused settlements to be ignored.
  • Amazon Payment Services (AMAZO):
    • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
    • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
  • China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
  • China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
  • Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
  • NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
  • Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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 — v.24.4

API

Added

  • Transaction API: The "account closed" error for PCI adapters has now been mapped to error code 2001 in IXOPAY and treated as a hard decline.

Features

Changed

  • Alerts: Instead of sending out separate emails for each alert, email notifications are now sent out periodically. These emails will collect all alerts received over a time period in a single email. The default time period is 5 minutes, but can be configured individually for each notification category.

Added

  • Provider Settlements and Reconciliation: Added a new feature to allow dummy settlement files to be created in order to test various post-processing features. The "Test Settlement" option is accessible from the "Provider Settlement" page. This page has been reworked and the UI has changes as a result. A new permission, postprocessing.provider-settlement.create, has been added. This permission must be enabled in order to access the "Create Settlement", "Upload Settlement File" and "Test Settlement" actions. The old permission, postprocessing.provider-settlement.settlement-upload, has been removed. If this permission was previously active, the new permission will be active by default.

Fixed

  • Job Configuration: Fixed an issue where two Save buttons were displayed when editing job configurations.
  • Transaction List: Ignore tenant name in the transaction list if only the "Include Sub-Tenants" checkbox was checked.
  • UI Navigation: Fixed an issue where styling was not applied to conflicted transactions after applying a filter.
  • UI Navigation: Fixed issues with sorting the transaction list by cardholder, first 6-8 digits, last four digits and card type. The table can no longer be sorted by card level, card bank and card country.

Adapters

Changed

  • Neteller (NET-EP1-NET): Added support for payouts.
  • Paynetics (PNE-EP1-CC): A new data fetcher setting, "Split settlements by PayCurrency", is now available. If enabled, settlements are split by currency and the PayCurrency is used as the SettlementCurrency.
  • Skrill (SKR-EP1-SKR): Added support for payouts.

Added

  • JCC Payment Systems (JCC): JCC Payment Systems leads Cyprus' payment-processing sector, supporting merchants and financial institutions for nearly 30 years.

Fixed

  • Adyen (ADY-EP3): Disabled refunds for the Multibanco payment method, as refunds are not supported for this payment method.
  • Braintree (BRA-EP1):
    • Fixed an issue that would result in an error if the customer was empty in a transaction.
    • Fixed an issue that occurred if the public or private key were null values.
  • China UMS (UMS-EP1):
    • Fixed an issue where white space was included in requests when no customer name is provided.
    • Fixed the mapping of callback data in the extraData field.
    • Fixed an issue with integer values in the extraData. Integer values are now converted to strings.
  • Klarna (KLW-EP1): When creating a session, the merchant_reference2 field is now also included. This provides additional information for identifying the transaction.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would occur if the encryption key and payload were missing. The system now checks whether these values are present, and a correspoing error is returned if this is the case.

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 — v.24.3

Features

Added

  • Audit Log: A color-coded diff of the changes to a post-processing job's configuration is now available.

Fixed

  • Multi-method connector: Fixed the status poll for multi-method connectors and added a new connector setting (Delay autoCapture for debits by 5min) that can be used to delay the automatic capture.
  • Network Tokenization: Fixed an issue that displayed disabled merchants in the NTS enrollment and Assign TRID drop-down lists.
  • Post Processing Jobs: Fixed an issue with exporting data that would cause credit card data (e.g. the brand) to be empty in the exported file.
  • Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that prevented them from being processed.
  • UI Navigation: The network token status tab is now hidden if no network token is available.
  • UI Navigation: Fixed an issue with sorting merchants and customer profiles.
  • Virtual Terminal: Fixed an issue with the formatting of surcharge amounts when entered as a percentage instead of an absolute value.

Adapters

Changed

  • Alignet (ALI-EP01-CC): Removed the merchant transaction ID section.
  • checkout.com (CHE-EP1-CC):
    • Added billing post code/ZIP and billing state fields for AFT transactions.
    • When the Postback/Status: Include Auth-Code in postback/response and status response connector setting is enabled, the auth-code sent by Checkout.com is now included in the callback.
  • Cybersource (CYS-EP1-CC):
    • Added support for partial capture
    • Mapped additional fields in API calls
    • Added support for the JapanPaymentOptions parameter for installments.
  • DPO Pay (PAYGA-PYGT): Added support for handling callbacks.
  • Nuvei (NUV): Added the ability to parse line items containing fees in settlement files.
  • PXP (PXP): An SFTP host can now be defined for the settlement data fetcher. If no SFTP host is specified, the default host (sft1.servebase.net) is used instead.
  • Zona Virtual SA - Zonapagos (ZONA-EP1): Added a setting to enable custom URLs for endpoints.

Added

  • China UMS (UMS): China UnionPay Merchant Services (China UMS) is a subsidiary of China UnionPay, a major financial services corporation in China. The adapter supports payments via Alipay and WeChat Pay.

Fixed

  • Adyen (ADY-EP3): Fixed an issue with the handling of the PresentToShopper result codes with the Multibanco payment method. The transaction is now set to pending instead of causing an error. This applies to all initial transaction types (debit, preauthorize and register).
  • Alignet (ALI-EP01-CC): Fixed an issue with ID duplicates caused by simultaneous transactions.
  • Alipay - Ant Group (ANT-EP1-ALIPL): Fixed a rare issue where an empty response would result in an error.
  • American Express (AMX):
    • Transactions in American Express settlements can now also be resolved using the additionalId1 field. The settlement handler first checks the UUID and then the additionalId1 field.
    • Refund amounts are now saved as absolute values.
  • checkout.com (CHE-EP1): Fixed an issue when mapping errors where the error code is empty.
  • checkout.com (CHE-EP1-IDE, CHE-EP2-IDE): Improved the adapter's error handling.
  • Mashreq (MASH): Debit calls include both a preauthorize and capture call. A 5 minute delay has been added to the capture due to recurring issues with instant captures.
  • Mashreq (MASH-EP01): Fixed an issue with parsing the API response that could result in an invalid value, leading to an error.
  • Worldline (ING-EP2): Fixed an issue with the data type used for the mandateDate.

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.