8 posts tagged with "PayPal"

Gateway API​

Changed​

• Transaction API: Add adapter name and brand to tracing data (includeTracing).

Added​

• Batch-upload API: Introduce Batch Upload API V2.
  • Support for deregister transactions.
  • A new lenient processing mode that skips invalid rows instead of aborting the batch.
  • A structured JSON result file.
  • Dedicated endpoints for status polling, result download, and batch listing.

Fixed​

• Push API: Fix an issue where the provider was not assigned to transactions.

Gateway Features​

Added​

• Customer Profiles: Add the ability to exclude specific stored payment instruments on the payment selection page.
• Meta connector: Add a new routing rule which allows routing to specific card networks.

Fixed​

• BI Data Source: Fix an issue where network token status changes were not reflected in the BI Data Source.
• Post Processing Jobs: Fix an issue where the transaction count in the Transactions tab of a post-processing job could be lower than the actual number of transactions.

Gateway Adapters​

Changed​

• Adyen (ADY-EP3-CC): Update response mapping documentation for AVS and CVV.
• Autopay (AUTO): Add rolling reserve line items to settlements, distinguishing between deducted reserve amounts and payout amounts.
• checkout.com (CHE-EP1-CC,CHE-EP2-CC): Add support for unreferenced refunds.
• dLocal (DLO-EP1-CC): Add a configuration setting to set a default transaction indicator for register transactions.
• dLocal (DLO-EP1-NETIN): Add support for the new payment method NetBanking. NetBanking is a popular bank transfer method in India that supports recurring payments, allowing customers to securely authorize a mandate for future subsequent transactions.
• Klarna (KLW): Add a sendReferenceInCaptures configuration setting to include the transaction UUID in capture requests for reconciliation purposes.
• PayPal (PPA): Add support for retrieving settlement reports from the sandbox environment when the connector is in test mode.
• PPRO (PPR-EP1-EPS): Add support for reversal handling.
• PPRO (PPR-EP1-IDE): Add support for reversal handling.
• PPRO (PPR-EP1-TWI): Add support for the new payment method TWINT. TWINT is the leading mobile payment method in Switzerland, allowing users to complete transactions instantly either directly in the smartphone app or by scanning a QR code.

Fixed​

• Autopay (AUTO-EP1): Fix register requests in migration flows to inherit the transaction indicator from the original transaction.
• HUA NAN COMMERCIAL BANK (HNCB-EP1-CCRD): Fix transactions failing due to a transaction reference exceeding the maximum field length.
• Redsys (RED-EP2-BIZ): Fix an issue where payment cancellations were routed to the error URL instead of the cancel URL.

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​

• Audit Log: Improve audit logs sorting.
• Risk Profile: Resolve edge-case race condition causing incorrect risk check data calculation.
• Risk Profile: Update Forter risk engine to use Orders API V3 (v10.1) and Order Status API V2 (v10.1).

Added​

• Post Processing Jobs: Add new job settings page to manage job status, steps, and conflict states. A new permission, postprocessing.job.update-settings, has been added to enable this.

Gateway Adapters​

Changed​

• ACI PAYON (PON-EP1-CC): Update provider 3-D Secure flow to support method fingerprinting.
• Adyen (ADY):
  • Add new data fetcher setting to map Tax Charge to either Service Fee or VAT.
  • Store Auth Code and Scheme Transaction Identifier from postbacks for reuse in subsequent transactions.
• Adyen (ADY-EP3-VIPPS): Enable partial capture for the Vipps payment method.
• PayU (PAU-E01-PAE): Add support for the new payment method PagoEfectivo. PagoEfectivo is a Peruvian cash-based online payment service that lets customers generate a payment voucher and settle it in cash at participating banks or retail locations.
• PayU (PAU-E01-YAPE): Add support for the new payment method Yape. Yape is a Peruvian mobile wallet that lets customers pay merchants or transfer money using their phone number or by scanning a QR code.
• Simulator: Tweak simulated 3-D Secure challenge page.

Fixed​

• dLocal (DLO): Fix settlement handling to correct amount formatting, ensure fees are deducted from the payout sum, and store fees to their respective transactions.
• PayPal (PPA): Prevent duplicate fees when receiving multiple callbacks for the same transaction.
• PXP (PXP): Fix status mapping of state 13 (AuthorisedByProvider) to a successful transaction.

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 API​

Changed​

• Transaction API: Modify the tracingData.transactions[].status field to use an enum with predefined status values instead of a string.

Added​

• Transaction API: Add returnData.binSegment and returnData.binRawData for returnData._TYPE of cardData in the Transaction API response.

Fixed​

• Transaction API: Fix an issue where the returnData.merchantAdviceCode (MAC) was not returned when its value was zero.

Gateway Features​

Changed​

• Account Updater: Improve account updater batch processing.
• Performance: Improve performance when using a large number of routing rules.
• Transaction Details: Enable Apply Extra Data from initial transaction and Apply new Extra Data by default for manual refunds.

Added​

• BI Data Source: Add result_extra_data.googleCryptogramPresent to reflect 3DS authentication for Google Pay transactions.
• Transaction Processing: Introduce the extraData.googlePayCryptogramPresent field in the Transaction API response to indicate 3DS authentication for Google Pay transactions.

Fixed​

• Network Tokenization: Fix an issue where network tokens were not deleted after failed transactions.
• Post Processing: Fix an issue that prevented manual file uploads of MIME type application/x-ndjason.
• Transaction Processing: Fix an issue that prevented schedules from being created in certain scenarios.

Gateway Adapters​

Changed​

• Redsys (RED-EP2): Support Register transactions and add recurring functionalities for the BizumAPI payment method.

Fixed​

• PayPal (PPA): Improved settlement handling for edge cases during reconciliation.
• PXP (PXP-EP1): Fix error mapping for specific error codes.

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 API​

Changed​

• Transaction API: Extend the callbackUrl length for refund requests (Refund) from 255 to 4096 characters.

Added​

• Customer profiles API: Add the fields associatedTokenType and networkTokenStatus to the /api/v3/customerProfiles/:apiKey/getProfile response for payment instruments of type card.

Gateway Features​

Added​

• Transaction Details: Add an Associated Tokens column (Network Token with Status, Google Pay Token, and Apple Pay Token) to the Customer Profile credit card payment instruments in the admin and merchant views.
• User Management: Add a new acl.roles.show permission for a read-only view of roles.

Fixed​

• Transaction List: Fix the advanced transaction list filter for Retrieval Reference Number (RRN).

Gateway Adapters​

Changed​

• EPG Financial Services Limited (EPG-EP01): Allow passing the extraData.ext_client_id parameter for Premium Partner solution participants to link Paylado accounts with player accounts.
• JPMorganChase (CHA): Add support for settlement handling.
• JPMorganChase (CHA-EP2-CC): Adds extraData["card.cardVerificationResult"], extraData["card.cardVerificationResultCode"], and extraData["card.paymentAccountReference"] to the response and callback payloads.
• KakaoPay (KAKAO): Updated default behavior to fetch settlement files from yesterday instead of looking back 30 days on the first fetch.
• PayPal (PPA): Map actual-net-settlement-amount settlement line item for reconciliation.
• Redsys (RED-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a service promoted by Spanish banks that connects customers' current bank accounts by linking them to their cell phone number.
• Worldpay (WOR): Change the chargeback creation date from the webhook receipt date to the date_post provided in the postback request.
• Worldpay (WOR-EP1-CC): Add a recommendation to the adapter documentation to enable the connector setting Postback: Send After Each Notification for online refund notifications.

Added​

• Paymob (PMO-EP2-CCRD): Add the Paymob adapter with support for redirect credit card payments. Paymob (formerly known as WeAccept) is a payment service provider and payment aggregator that empowers businesses to get paid wherever their customers are.

Fixed​

• KCP Mobile (KCPMO-EP1): Fix encoding issue on the Hosted Payment Page.
• Mashreq (MASH): Fixed an issue with postback sharing where transactions were not processed correctly when postback sharing was enabled via the setting Accept postbacks from other connectors (list GUIDs comma-separated).
• PXP (PXP-EP1-INST): Add mapping for payment state 15 to “Transaction Declined” error.

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​

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