6 posts tagged with "Stripe"

API​

Changed​

• Status API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.
• Transaction API: Exposes the acquirer reference number (ARN) via the field extraData["arn"] when it is available.

Fixed​

• Transaction API: Fix an issue where missing wallet data fields (walletOwner, walletReferenceId, walletOwnerFirstName, walletOwnerLastName, walletOwnerCountryCode) could cause an error. These fields are now treated as not provided.
• Transaction API: Implement stricter currency format validation, requiring merchants to send amounts with the correct number of decimal places for each currency (e.g., EUR: 9.99 or 9.9, JPY: 5 or 5.00). If the correct format can't be provided by merchants, the tenant can be configured to round amounts commercially according to our currency definition. These settings are inherited by sub-tenants. For assistance in configuring this setting, please contact your customer success manager.

Features​

Added​

• BI Data Source: Add a new data field, sub_type, for transaction subtypes related to rapid dispute resolution (RDR) in the BI data source.
• Login: Store redirect data in the URL to ensure that after multi-tab logout and login, each tab returns to the originally requested page instead of the landing page.
• Token Count Aggregation: Add filters to the post-processing step Calculate Token Count, allowing users to:
  1. Exclude Merchants having this Job Types scheduled
  2. Exclude Connectors having this Job Types scheduled
  3. Only Methods.

Fixed​

• Connector Configuration: Fix a bug in the transaction expiration process to ensure the Ignore Global Setting connector setting is respected whenExpire Pending Transactions or Expire Transactions is enabled.
• Connector Configuration: Fix an issue where a valid value of 0 for the connector setting Postback Queue: Set maximum number of retries was incorrectly treated as missing or invalid. The system now properly accepts 0 as a valid input.
• Documentation: Fixes the API authentication examples by removing the newline character that was incorrectly included in the base64-encoded concatenation of the username and password.

Adapters​

Changed​

• 2C2P (2C2P-EP1-2C2PB): Update the payment channels by removing Thanachart Bank and adding the new TMBThanachart Bank following the merger with TMB Bank.
• KCP Mobile, KCP PC (KCPMO, KCPPC): Add support for settlement handling.
• Mercado Pago (MERPA-PROD): Adds a new header to the payment request containing the DeviceData. This allows the collection of the DeviceID when redirecting the user to the Hosted Payment Page (HPP).
• PXP (PXP-EP1-CC): Map the field ProviderExternalID to acquirer reference number (ARN).
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC (extends STRV2-EP1-CC)): Add the ability to pass requestExtendedAuthorization as extra data to Stripe to request an authorization to be extended for up to 30 days.
• Worldpay (WOR-EP1): Update AFT documentation.

Added​

• KakaoPay (KAKAO): Add the KakaoPay adapter with support for debit, refund and partial refund transactions. KakaoPpay is a South Korean fintech company specializing in digital payments, money transfers, and financial services.

Fixed​

• KCP Mobile (KCPMO-EP1):
  • Use Code as fallback response code if res_cd isn't available.
  • Fix an issue where the wrong value (payment method ID instead of payment method name) was sent for the pay_method field.
• Nuvei (NUV-EP1-CC): Fixes the fail-over transaction to Nuvei by ensuring that the firstPaymentDoTransactionId is only set if the related transaction was created through Nuvei; otherwise, it is omitted to prevent rejected transactions.
• PXP (PXP-EP1-INST): Fix wrong format of expiryMonth and expiryYear in adapter result.
• Zona Virtual SA - Zonapagos (ZONA-EP1): Fix status retrieval handling to consider only the latest status, as recommended by the PSP.

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​

• BI Data Source: As announced, switch the BI Data Source endpoint /query/transactions from ElasticSearch to OpenSearch.

Fixed​

• API Testing: Replace username and password input fields with a user selector to reduce transmission of sensitive data.
• Customer Profile: Prevent the deletion of a customer profile’s payment instrument when deregistering a network token or PAN, even if the other was still present.
• Documentation: Update BI data source sandbox links in documentation to refer to sandboxbds.ixopay.com instead of sandbox.ixopay.com.
• Meta connector: Fix saving a routing rule node with an invalid ID or non-matching meta connector to show a proper error message instead of causing an internal error.
• Virtual Terminal: Fix internal server error in virtual terminal requests by verifying transaction object support before setting surcharge amount.

Adapters​

Changed​

• Alignet (ALI): Add support for settlement handling.
• dLocal (DLO-EP1-VPAY): Added support for the VPay QR payment method, enabling QR payments in Bolivia.
• EBANX (EBA): Add Endpoint connector configuration option to switch between Cross-border Endpoint and Local2Local (Domestic) Endpoint, with cross-border endpoint as the default.
• Nuvei (NUV):
  • Extend settlement handler to parse the new Settlement Summary Report Drill report type, selectable via the fileType field in the settlement data fetcher. Default remains Transaction Report.
  • Add automatic SFTP connection testing to settlement data fetchers.
• Payabl (P21-EP1): Update the testing endpoint to sandbox.payabl.com from sandbox.powercash21.com.
• Stripe (STRV2-EP1-CC, STRV2-EP3-CC): Add support for incremental authorization transactions for the Stripe adapter.
• Worldline (ING-EP2): Add shouldBeFinishedWhenCapturedTrustly connector setting to allow Trustly debit transactions to be marked as successful upon CAPTURED status, enabling customers to treat these transactions as finished.
• Worldline (ING-EP5): Forward transaction UUID as references.merchantReference in refund and capture requests.
• Worldpay (WOR-EP1): Add documentation for Account Funding Transactions (AFT).

Added​

• KCP Mobile (KCPMO-EP1): Add the KCP Mobile adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.
• KCP PC (KCPPC-EP01): Add the KCP PC adapter with support for credit card and bank transfer payment methods. KCP Payment Solutions: Secure payment processing supporting multiple currencies and countries.

Fixed​

• Worldline (ING-EP5): Fix a bug regarding the handling of webhooks.

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​

Added​

• Provisioning API: Two new fields have been added to the merchant response model: ntsEnrollmentStatus and networkTokenizationEnabled.

Features​

Changed​

• Job Configuration: Information on inherited job type templates is now displayed, informing users as to why the template cannot be edited.

Added​

• Network Tokenization:
  • Information on the status of enrollment for network tokenization is now available in the base data for a merchant. A new line, "Network Tokenization" has been added. If the merchant has a TRID assigned, the status is displayed as "enabled" when viewing the data as an admin with the permission "tokenization.networkTokenization.enrollment.show".
  • Merchants can now be filtered by their NTS status in the overview.

Fixed​

• Pay-by-Link: Fixed an issue with the virtual terminal's result page not updating correctly if the initial transaction fails. Instead of displaying transaction data from the most recent (successful) transaction, data from the first (failed) transaction continued to be displayed.
• Provider Settlements and Reconciliation: Fixed an issue that would cause chargeback reversals to be created for the debit transaction, instead of the chargeback transaction.
• Transaction List: Fixed an issue that would cause an error in the advanced search when changing the comparison operator from a range to any other operator.
• Transaction List: Fixed an issue with sorting credit card fields. Note that BIN data cannot be sorted.
• User Management: The frontend.statistics.show permissions now governs access to the pivot table as well.
• Virtual Terminal: Fixed an unhandled exception in the virtual terminal that would occur if the fee set or fee entity was not found. The exception is now handled and an empty surcharge value is returned.

Adapters​

Changed​

• Adyen (ADY): The payment reference for settlements is now saved.
• Amazon Payment Services (AMAZO): It is now possible to filter transactions by the status "Accepted".
• MultiSafepay (MUL): Added the chargeback reason for chargebacks.
• Stripe (STRV2-EP1-MAS): Additional data from the Stripe API response is now included in the postback's extraData.

Added​

• dLocal (DLO-EP1): Added support for the Sinpe payment method. This method supports bank transfers in Costa Rica.
• Worldline (ING-EP2): Added support for payments via Trustly.
• Zona Virtual SA - Zonapagos (ZONA-EP1-ZP): Added a generic payment method that redirects to the Zona Pagos payment page. The consumer can then select the desired payment method on this page to initiate the transaction.

Fixed​

• Adyen (ADY-EP3-BIZ): Fixed an issue that would cause transactions that had been processed successfully to be assigned the status error or pending.
• checkout.com (CHE): Fixed an issue that would cause an error when retrieving the session ID.
• eMerchantPay (EME-EP3-SEP): Fixed an error that would occur if the customer was not an IBAN customer.
• Mashreq (MASH): Fixed an issue when checking 3DS credentials that would cause a type error.
• Mercado Pago (MERPA-PROD): Fixed an issue with register transactions caused by the Amount For Card Verification not being included in the request to retrieve the issuer and payment method ID from the PSP.
• Skrill (SKR-EP1): Fixed an issue related to email addresses not being tied to a Skrill account when requesting a payout. This would cause the payout to fail.
• Volt (VOL): Fixed an issue caused by incorrectly handling errors in a response as a result.

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​

• Post Processing Jobs:
  • The Collect Transactions by Uploaded CSV File post-processing job now allows multiple fields (arn, uuid, and adapterTxid) to be mapped. Previously, only the arn field could be mapped.
  • A new setting has been introduced, Cascading ID Mapping. If this option is activated, IXOPAY attempts to locate related transactions for every mapped identifier (in the same order as the fields are mapped in the post-processing job). If a transaction is found, it is added to the post-processing job, while all other identifiers in the CSV are ignored for that transaction.
• Provider Settlements and Reconciliation: Improved the error message that is displayed when a transaction cannot be found due to a missing reference in the settlement file.
• UI Navigation: New permissions have been added that determine whether users can access the dashboard (dashboard.show and frontend.dashboard.show). Existing users and roles will automatically receive these permissions. A welcome page is now displayed as the start page for users without access to the dashboard.

Fixed​

• Fee Management: Fixed an issue that meant it was possible to save fees even when the mandatory feeStrategyParameters field did not contain a value.
• Fee Management: Fixed an issue where the amount was incorrect in retried transactions, as the amount would include previous surcharges if the surcharge was calculated dynamically.
• Post Processing Jobs: Fixed an issue that prevented more than 1,000 connectors from being assigned to a post-processing job schedule.
• Provider Settlements and Reconciliation: Fixed an issue that caused the delete button to be displayed for canceled transactions. The button is now only displayed if the status of the settlement is "new".
• Provider Settlements and Reconciliation: Fixed an issue with resolving transactions by additionalId.
• Transaction List: Fixed an issue with sorting by card type in the Transaction List.
• Transaction List: Fixed an issue in the Transaction List filters that would cause no results to be returned if a filter was applied to the first 8 digits of the card number.
• UI Navigation: Fixed an issue where the red highlighting of missing reconciliations was not applied when switching pages or applying a filter.
• Virtual Terminal: Fixed an issue with surcharge fee calculations.

Adapters​

Changed​

• GoCardless (GOC-EP1): GoCardless settlements now also include payment references.

Fixed​

• Adyen (ADY): Fixed an issue caused by the Izyco settlement data fetcher configuration parameter missing the regular expression for the file name.
• Braintree (BRA-EP1): Improved the handling of the billing address. If the extra data fields for company, first name or last name are unavailable, the company, first name and last name are taken from the Customer object.
• checkout.com (CHE-EP1-CC, CHE-EP2-CC):
  • Fixed an issue that would cause the status of a transaction to be set to ERROR if a callback is received that is not mapped in IXOPAY.
  • The following callbacks are now handled:
    • authorization_declined
    • card_verification_declined
    • card_verified
    • authentication_started
    • authentication_approved.
  • Added the mandatory provessingChannelId parameter for the NAS platform.
• Nexi Group (NETS): Fixed an issue with settlements caused by a missing configuration.
• PayU (PAU-E01): Fixed an issue that would cause a backend error if the payment_id is missing in the payload during callback processing.
• Stripe (STRV2): Fixed an issue with Stripe settlements where transactions in IXOPAY were not correctly identified.
• Volt (VOL): Fixed an issue with retrieving settlements.

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.