4 posts tagged with "PayPal"

API​

Changed​

• BI Data Source: BREAKING CHANGE BI Data Source API v1 is deprecated and will be removed in a future release. We strongly recommend migrating to v2 as soon as possible.

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.

Features​

Changed​

• Account Updater: The information on when a customer's card was last updated only displays the date, not date and time. The documentation has been updated accordingly.

• Meta connector (Multi-method connector): A number of changes have been implemented:

  Routing rules view:

  • Disabled and archived connectors are now only displayed if they are used in the routing rule. If such adapters are used, the adapter is displayed with the "(DISABLED)" prefix.
  • If a connector used in a routing rule is disabled or archived, the rule can no longer be saved. A suitable error message is displayed.

  Connector configuration:

  • When a connector is disabled or archived, the system first checks whether the connector is used in any routing rules. If the connector is in use, a warning is displayed that connectors can only be disabled or archived if they are not used by any routing rules. A list of the routing profiles using the connector is also displayed.

  Meta-connector configuration:

  • When unarchiving a meta-connector, its status is automatically set to disabled.
  • When enabling a meta-connector, the system checks whether the meta-connector uses any disabled or archived connectors. A corresponding message is displayed if the meta-connector cannot be enabled due to it referencing disabled/archived connectors.

Fixed​

• Virtual Terminal: The merchant transaction ID is now a mandatory field in the virtual terminal.

Adapters​

Changed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Added post-processing logs.
• Braintree (BRA-EP2-CC): Added support for chargeback and chargeback reversals for disbursement and fee settlements.
• Redsys (RED):
  • Updated the documentation to include information on the new configuration and parameter mapping.
  • Added a merchant descriptor configuration to DS_MERCHANT_MERCHANTDESCRIPTOR
  • Mapped the description to DS_MERCHANT_MERCHANTDESCRIPTOR.
• Silverflow, Stripe (SIL-SEP-VIS, STRV2-EP1-VIS): Updated the documentation with information that final captures are supported by the adapter.
• Worldline (ING-EP1-CC): Increased the timeout to 60 seconds when retrieving settlement files.

Added​

• CMI (CMI): The payment acquirer CMI has been a trusted partner of Moroccan merchants since 2004. The CMI adapter supports payment via credit card.

Fixed​

• eMerchantPay (EME-EP3-SEP): Fixed a bug which caused partial refunds to be declined by the gateway, even though this transaction type is supported.
• HypYaad (HYP-EP1-CC): Fixed a bug that caused transactions with an amount higher than 999.99 to be ignored in settlements.
• PayPal (PPA, SHO): Fixed an issue that would occur when configuring a data fetcher for either PayPal or Shopify PayPal without the necessary required parameters. The user name and password in the configuration are now also shown as required.
• Worldline (ING-EP5): Updated the way transactions are voided to include additional information on the payment amount and currency. The status handling was also reworked to improve error handling and the accuracy of 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.

API​

Fixed​

• Provisioning API: The frontend.dashboard.show permission, used to grant access to dashboards, has been added to the Provisioning API.

Features​

Added​

• Blocklist: Extended the blocklist to include the ability to define automatic blocklist rules. These can be used to add credit cards to the blocklist based on the merchant advice code ("Do not retry") or error code.

Fixed​

• User Management: Fixed an issue with sending account recovery emails that would cause an error if the email failed to send.

Adapters​

Changed​

• 2C2P (2C2P): Improved the error displayed when no transaction method is defined to better indicate the cause of the error.
• 2C2P (2C2P-EP1): Refunds in 2C2P settlements are now handled.
• PayPal (PPA-EP1-PPE): Added support for the Pay Later method to the Braintree adapter.
• Sampath Bank (SAMPA-SVNP1): Added support for credit card payments via redirect.
• Valitor (VALIT): Updated the adapter to automatically create a second chargeback if included in the settlements received from Valitor.
• Worldline (ING-EP2): Improved the mapping of error codes based on the specific error, rather than just the HTTP status code.
• Worldpay (WOR): Chargeback reversals for credit cards are now handled in settlements and included as line items.

Fixed​

• Adyen (ADY-EP3): Fixed an issue that could result in long request processing times caused by transactions being locked when multiple postbacks are received simultaneously.
• Nexi Group (NETS-EP2): Fixed the incorrect mapping of adapter error messages.

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.

Features​

Added​

• Post Processing Jobs: Added a new configuration option in the job configuration Processing Step: Copy Line Items from related batch - Do not aggregate line items with the same name that allows two line items with the same name.
• Provider Settlements and Reconciliation: Added a new Provider Setting - Reconciliation: Create Provider Settlement with Conflict Log to handle settlements provided via reconciliation (e.g. PayPal) in cases where the transaction is missing or unknown.
• UI Navigation: The Customer Profiles and Account Updater have been moved to the Tokenization menu.

Adapters​

Changed​

• checkout.com (CHE-EP1): Aggregated payout information is now represented as line items in settlements. This includes interchange fees, scheme and network fees, provider fees, gateway fees and chargeback fees.
• DPO Pay (PAYGA-PYGT-PMR): Updated the parser to handle the updated structure in newer settlement files.
• eMerchantPay (EME-EP3): Removed the check that data has been entered in mandatory fields in EMPGenesis, as these mandatory fields can be disabled for the merchant by the PSP.

Added​

• Braintree (BRA-EP1-PPE): Added support for additional data (STC, AID, BN) required by Braintree for airlines and travel merchants when using PayPal as the payment method.
• Braintree (BRA-EP1-PPE): Added support for tenant-specific BN code which are included with pre-authorization and debit transactions.
• Braintree (BRA-EP2-CC): Added support for level 2/3 data for Visa and Mastercard transactions via Braintree.
• Mashreq (MASH-EP01-CCRD): Added a new adapter for Mashreq. Mashreq a leading financial institutions in the UAE that provides banking and financial services. The adapter supports credit card transactions and settlements.
• MultiSafepay (MUL-EP1): Added support for reconciliation and settlements for the Multisafepay adapter.
• PayPal (PPA-EP1-PPE): Wallet data (first name and last name) is now exposed under Additional Info for payouts and debits.
• Worldpay (ING-EP2): Added the option to configure an SFTP host and SFTP private key with optional SFTP passphrase instead of an SFTP password.

Fixed​

• BDO (BDO-EP1-GCASH): Risk check are now correctly applied to the BDO adapter.
• DPO Pay (PAYGA-PYGT-CC): Added a check for a mandatory description in refunds.
• PayPal (PPA-EP1-PPE): Fixed an issue handling the refund amount in partial refunds received via postback.
• PayU (PAU-E01-CC): Implemented a method for tokenizing cards using debit and refund transaction for Colombia, as authorization and register transactions are not supported.
• Redsys (RED-EP1-CC): Fixed an issue with the key length in the paramsKey extraData parameter.
• Volt (VOL-EP1): Fixed error handling during Volt settlement notification handling.
• Volt (VOL-EP1): By default the full list of banks is now retrieved for Volt. A subset of banks can be retrieved using parameters.page and parameters.limit.
• Worldline (ING-EP3-CC): Fixed Worldline Ogone TWINT settlement refund fee handling.

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.