Skip to main content

7 posts tagged with "American Express"

View All Tags

Gateway — v.24.15

API​

Fixed​

  • Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
  • Push API: Fixed handling of request bodies with invalid JSON.

Features​

Changed​

  • Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
  • Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added​

  • Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed​

  • Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
  • Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
  • Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
  • Customer Profiles: Use the correct customer profile container for meta connectors.
  • Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
  • Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
  • Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
  • Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
  • Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters​

Changed​

  • Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
  • Mashreq (MASH-EP01): Added support for debit auto-capture.
  • PAYONE (PASIX): Add new mappings for settlements:
    • Markup fee (condCode 701)
    • Dispute fee (condCode 55).
  • PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
  • Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
  • Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed​

  • American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
  • iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
  • Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
  • Transbank (TRANS-TSB1): Fixed handling of empty responses.

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.13

API​

Changed​

Fixed​

  • Pay-by-Link API: Fixed an issue that would prevent a pay-by-link transaction from being canceled if a failover occurred for the transaction.
  • Push API: Fixed an issue that would cause a type error if an empty body request was submitted in a Push API request.
  • Transaction API: Fixed an issue where invalid 3DS values (browserColorDepth, browserTimezone) sent to the API in transaction data would cause an error. These invalid values are now ignored.

Features​

Changed​

  • Connector Settings: The "Postback: Include 3DS Data" connector setting is now also available in the global settings.
  • Post Processing Jobs: Optimized the process of collecting transactions in post-processing jobs.
  • UI Navigation: Improved the parent tenant selection when creating a new tenant. By default, the current tenant is set as the parent tenant and the drop-down is now searchable.
  • UI Navigation: Updated risk logs so that they are loaded asynchronously. This improves the initial load time for the transaction details view. Risk data is now only loaded when expanding the view.

Added​

  • Connector Configuration: Added audit logs for the "Additional Configs" in the connector view.

Fixed​

  • Audit Log: Fixed an issue that would cause an error when accessing the audit log if the corresponding merchant cannot be found when checking access permissions.
  • Fee Management: Fixed an issue that would cause an error when changing the mapping to a different fee entity. The mapping for the old fee entity is now removed, and the mapping is set to the new fee entity.
  • Post Processing Setting: Fixed an issue with the "Create unknown transaction on connector with GUID" option for settlements that prevented unknown transactions in a settlement file from being added to the platform.
  • Provider: Fixed an issue that would occur when saving a connector configuration. Previously configured connectors that were assigned to the same provider were removed when the configuration was saved, with only the new configuration linked to the provider.
  • Provider Settlements and Reconciliation: Fixed an issue that would cause an error when trying to sort missing reconciliation data by merchant.
  • Risk Profile: Fixed an issue where saving a risk rule without entering parameter values would result in a type error.
  • Risk Profile: Fixed an issue that would cause an error when opening risk rules if the risk rule set ID referenced a risk rule set that does not exist. A 404 error is now displayed instead.
  • Transaction Processing: Fixed an issue caused by the platform attempting to collect 3DS information for Apple Pay transactions. The system now checks whether a transaction uses Apple Pay before collecting additional 3DS information.
  • UI Navigation: The loading page displayed for the collectMissing3DSecureData connector configuration was only displayed in English. The page is now displayed in the language of the transaction where available, with English as the fallback language.

Adapters​

Changed​

  • American Express (AMX-EP1-AMX): Added a new gateway connector configuration option, "Force System Generated STAN". This option can be used to force the system trace audit number (stan) to be generated by the IXOPAY platform and stored in the additionalId1 field. The following options are available to determine the format of the STAN:
    • "Yes - Uppercase characters only"
    • "Yes - Upper- and lowercase characters".
  • Banca Intesa (BAI-EP1): If the PSP includes the TRACEID in a transaction response, it is now included in the postback.
  • Braintree (BRA-EP1-BLI): Added support for partial refunds for the Blik non-redirect payment method.
  • Braintree (BRA-EP1-PPE): Added support for line items and a corresponding option, includeLineItems has been added to the connector configuration.
  • dLocal (DLO-EP1-CC): The merchantTransactionId is now passed to the vault, in order to pass it on to the PSP in refund requests.
  • HypYaad (HYP): Removed the mapping of payment references in settlement files, as this could lead to a single settlement file being split into multiple settlements.
  • Mastercard Payment Gateway Services (MPG, BAMI): Added support for the scheme transaction ID.
  • Nexi Group (NETS-EP1): Added support for specifying the language in the checkout payload for transactions. This ensures that the language field is included in the payload if it is included in the transaction's extra data.
  • PayPal (PPA-EP1-PPE): Added the isFinalCapture flag for capture transactions. If set to true, the capture is marked as final on the PayPal side and no further captures are possible.
  • Simulator: Added support for incremental authorization for simulated credit card transactions.

Added​

  • WavePay (WAV): The WavePay push adapter allows cash collection payments to be pushed to the IXOPAY platform to ensure that these transactions are also available within the system.

Fixed​

  • Afterpay (AFT): Fixed an issue with retrieving the minimum/maximum price, caused by a missing interface.
  • American Express (AMX-EP1-AMX): Fixed an issue that would cause an error if settlement files are not formatted correctly.
  • Braintree (BRA): If rows in a settlement file did not include a settlement date, the settlement date was previously taken from the first value found in the "Settlement Date" column of the file. However, this could result in the settlement date being incorrect. The behavior has therefore been changed to set the settlement date to the transaction's disbursement date instead.
  • Braintree (BRA-EP1-PPE): The merchantAccountId is now only passed to Braintree's JavaScript SDK if a value is present.
  • iyzico (IYZ):
    • Fixed an issue with that would cause the batch number to be set to the entire file name of the settlement file, rather than the initial numerical portion of the file name. This was caused by empty rows in the settlement file.
    • Fixed an issue that would cause some settlement files to be parsed incorrectly.
  • Khipu (KHI): Fixed an issue with retrieving the bank list, caused by a missing interface.
  • Klarna (KLW): Fixed an issue that would result in the error "Invalid Response" being returned for transaction without a body. An empty body is now handled correctly, with the HTTP error code being checked prior to parsing the response.
  • Mashreq (MASH-EP01): Fixed an issue where the status of successful transactions was not set correctly due to the status in the response not being formatted as expected.
  • Payabl (P21): Fixed an issue caused by the error code parameter being evaluated incorrectly.
  • Paymee (PAYME-EP1-CCRD): Fixed an issue where refund amounts would be sent with a varying number of decimal places, which could sometimes lead to errors. Refund amounts are now formatted consistently.
  • Trustly (TRU): Fixed an issue that would cause a generic payment error if the private key required to generate the signature was missing. The system now checks for its presence.

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.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.

Gateway — v.23.20

Features​

Added​

  • Job Configuration: To simplify the process of exporting settlement file data for enterprises with multiple merchants, the External ID stored in the provider can now be used to store an identifier for each merchant. This ID can be selected in export jobs, allowing the same export job to be used for each company/merchant in cases where there are otherwise no differences between the exports. Previously, an individual export needed to be configured per company/merchant.

Fixed​

  • Account Updater: Fixed an issue with the Account Updater that would lead to an incorrect Status being displayed for batch updates ("Finished" instead of "Waiting").
  • Account Updater: Fixed an issue with the new merchant overview where clicking on the details would not redirect users to the selected merchant, but to the selected tenant instead.
  • Merchant Interface: Updated some translations and reviewed the Croatian and Slovenian translations.
  • Pay-by-Link: Restricted the ability to cancel transactions to pay-by-link transactions only.
  • Post Processing Setting: Fixed an issue that would prevent settlements from being retrieved if the waitForAllFiles setting is enabled. Incomplete periods are now also handled correctly, with the last period only being updated if settlement files were processed.
  • UI: Fixed the 8-digit BIN display in the transaction details view.
  • UI Navigation: Fixed the broken icon for creating connectors.
  • Virtual Terminal: Removed trailing apostrophes for virtual terminal result URLs.

Adapters​

Changed​

  • American Express (AMX-EP1): Reinstituted a change that was reverted in the last release. A reference number is generated and passed to the vault as part of the capture request using the additionalId1 field. However, this could not be handled using the multi-method connector.
  • ATOM (an NTT DATA Company) (ATOM-EP1-CC): The data fetcher configuration has been updated, allowing additional field mappings for settlement files. The names of the fields selected here need to be added to the key column in the export job.
  • checkout.com (CHE-EP2): Added payout parameters for platform 2.
  • dLocal (DLO-EP1-PUNTO): The Punto Express payment method is now supported by the dLocal adapter.
  • eMerchantPay (EME-EP3-SEP): Added support for deregister transactions.
  • GoCardless (GOC-EP1): An additional configuration option has been added for the connector that provides a choice between redirect and server to server flows.
  • Nuvei (NUV-EP2): Fixed the mapping of Nuvei error codes, with "Service Busy" now being mapped to IXOPAY error code 3003 (temporarily unavailable).
  • Sepa Express (SEP-EP3-BTR): Added a new bank transfer payment method to the adapter. As this payment method uses open banking, some transaction types like register and deregister are unavailable, along with other transaction types not implemented in the original version of the adapter.
  • SoftBank Payment Service (SOB-EP1): The documentation was updated to include information on required fields.
  • Unzer (UNZER): Fixed the title for the Unzer API documentation.
  • Valitor (VALIT-EP1-CC): Fixed an issue that would cause refunds to fail for capture transactions. Instead of requesting a refund, IXOPAY now requests a capture refund, which resolves this issue.

Added​

  • AsiaPay (ASIA): AsiaPay is a leading payment service provider in the APAC region. The adapter supports GCash, ShopeePay and credit card payments.
  • HypYaad (HYP-EP1-CC): Hyp is an Israeli all-in-one payments solution that provides online and in-store payment solutions. The adapter supports credit card payments.
  • Unzer (UNZER-EP1): Unzer is a leading fintech company based in Germany, specializing in providing innovative and secure payment solutions. With a strong focus on e-commerce, Unzer offers a wide range of payment methods and services.

Fixed​

  • American Express (AMX-EP1): Fixed an issue with fees in American Express settlements that would only occur under certain circumstances.
  • AsiaPay (ASIA): The AsiaPay PesoPay logo is now displayed wherever the brand name is used instead of the adapter name.
  • checkout.com (CHE-EP1): Fee reports are now handled in a second process, rather than as part of the settlement. A new data fetcher configuration (gross type) is available for this purpose.
  • Klarna (KLW): Fixed an issue with validation that affected customers in specific locations. The validation now checks that the billingState is set if the country is US or Australia.
  • Nuvei (NUV-EP1): Improved the parsing of the CSV settlement files to be more robust. Under some circumstances, an error could occur when parsing settlement files.
  • Nuvei (NUV-EP1): Before parsing a row in the reconciliation file, the date is checked to ensure it is valid.
  • Straight2Bank Pay (STRAI-E01): Fixed an issue that would cause the retrieval process for settlements to be locked if an invalid response was received.
  • Unzer: Fixed errors caused when postback sharing is not set in the connector.
  • Worldpay (WOR-EP1-CC): The adapter transaction ID is now set when an incoming postback is received.

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.