6 posts tagged with "GoCardless"

Features​

Changed​

• Post Processing Setting: Added validation of custom parameters, it will now show an error when trying to save post processing job settings with invalid custom parameters.

Fixed​

• Customer Profiles: Use the network token (dPAN) instead of the fPAN when a customer profile was created or updated from a network token registration.

Adapters​

Changed​

• Valitor (VALIT): Added support for mapping Acquirer Reference Numbers (ARNs) in settlement processing.
• Worldpay (WOR-EP1): Added support for account funding transactions (AFT).

Fixed​

• GoCardless (GOC): Fixed an issue in settlement processing where missing links.payment or links.refund in a refund object would previously cause an error and stop transaction retrieval.
• Klarna (KLW): Fixed Klarna settlement configuration to allow longer passwords via the KlarnaApiPassword field in the provider settlement data fetcher configuration. If no KlarnaApiPassword is set, the connector configuration password will still be used.
• Nexi Group (NETS): Fixes a problem with the test-mode configuration setting which prevented retrieving settlements.
• PayPal Complete Payments - PPCP (PPCP-EP1-PPE): Removed null values from the setup token call to prevent issues with the prepare-register call when shipping details are not provided.
• PXP (PXP-EP1-INST):
  • Added missing adapter specific documentation.
  • Send initiatePaymentFromReferenceRequest.merchantTransactionId to the PSP to correctly link follow-up transactions with their initial transaction.
  • Fixed handling of responses of capture, refund, and void transactions.
• Worldpay (WOR-EP5): Fixed the settlement amount calculation for refunds during settlement processing.

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​

• Provisioning API: Added the field eventNotificationUrl to merchant entities.
• Transaction API: Added field transactionSubType to the status API calls and to transaction callback bodys.

Features​

Changed​

• BIN Lookup: Updated the BIN data source.
• Pay-by-Link: Introduced a new pay-by-link-enabled permission to allow control over which API users can trigger pay-by-link transaction., The permission defaults to enabled for existing API users who have previously used pay-by-link, and disabled for all others.
• Transaction Processing: Enabled sending transaction descriptions to upstream PSPs for void and capture transaction types.

Added​

• Account Updater (Network Tokenization): Added a notification service that sends callbacks to shared merchants —those sharing a customer profile container— whenever a transaction is updated through the account updater or NTS Updates.

• Fee Management: Added a new field Transaction Subtype to Fee Constraints, including it in fee calculations; subtypes can be Chargeback Resolved, Chargeback Reversal Resolved, or - any - for no specific preference. Fee items will now be grouped by transaction type and subtype (if present).

• Job Configuration: Introduced transaction subtype filtering to the following Collecting Post Processing Job steps:

  • Collect Transactions from Related Batch
  • Collect All Transactions within a Period
  • Collect Transactions from Provider Settlements (created/settled within a period)
  • Collect Transactions by Settlement State

  Introduced transaction subtype filtering and grouping to the following Processing Post Processing Job steps:

  • Aggregate Transaction Fees to Job Line Items
  • Aggregate Transaction Values to Job Line Items
  • Calculate Rolling Reserve for Merchant
  • Count Transaction Value to Job Line Items.

• Post Processing Jobs: Added support for filtering via the transaction subtype in the transaction view for Post Processing Jobs.

• Post Processing Jobs: Added transaction subType column as possible export value for the following Post Processing Job steps

  • Export Transactions to CSV
  • Export Transactions to XLSX
  • Export Transactions to XLSX (Version 2)
  • Write customized Settlement CSV.

• Provider Settlements and Reconciliation: Added support for filtering via the transaction subtype in the Transactions in Batch and Conflicted Transactions views for Provider Settlements.

• Transaction Details & Post Processing Jobs & Provider Settlements and Reconciliation: Added subtype to the transaction Details view.

• Transaction Processing: Added a subtype field to transactions for rapid dispute resolution, with available subtypes "chargeback resolved" and "chargeback-reversal resolved".

Fixed​

• Post Processing Setting: Set a default transaction type when creating transactions derived from settlements without a transaction type.
• Transaction Details: Fixed an issue where displaying Risk Data on the Transaction Detail page could cause an error in certain cases.
• Virtual terminal: Fixed the virtual terminal view for merchant users.

Adapters​

Changed​

• Amazon Payment Services (AMAZO-EP1): Added clear error messages for transactions when errors are triggered by incoming postbacks.
• MultiSafepay (MUL-EP1): Added Content-Type: application/json to requests sent to the PSP to ensure the PSP can look-up the requests in their logs.
• Valitor (VALIT): Added support for RDR.

Added​

• Bangkok Bank (BB): Added the Bangkok Bank post processing adapter with support for settlement handling.

Fixed​

• Global Payments (GBP): Resolved a bug in the parsing of Global Payments settlements.
• GoCardless (GOC-EP1): Removed mandate callback handling for cases where the initial registration was already successful.

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.

API​

Fixed​

• Batch API: Addressed issues with the conversion of files from CSV to JSON, and conflicting UUIDs due to latency between the time when a transaction is submitted and actually processed.
• Transaction API: Fixed an issue where if a failover transaction returns a merchant advice code, this MAC is not returned by the origin transaction. The MAC is now returned by the origin transaction.

Features​

Changed​

• Customer Profile: It is now possible to use the UUID or payment token from a customer profile to request a CVV refresh via payment.js. This makes it possible to ask the customer to enter their CVV for transactions using a stored credit card.
• Post Processing Setting: Postback notifications are now sent when creating an "unknown" transaction.
• UI: Information on the possible impact of daylight savings time is now displayed when editing job schedules.
• User Management: Any changes to merchant users now require additional confirmation, and a message is displayed that these changes may have an effect on live processing.

Fixed​

• Global Connector Settings: Transaction expiry settings are now displayed in the connector's global settings section.
• Post Processing Job Configuration: The calculation of the net settlement amount in the "Write customized Settlement CSV" job step is now the same for refunds and chargebacks.
• Risk Profile: The "Allowlist" and "Blocklist" risk rules no longer list credit card-related options such as the BIN and CC fingerprint for the meta-connector, as the card cannot be evaluated at this stage of processing.

Adapters​

Changed​

• Bitpay (BTP-EP1-CR): BitPay pairing has been moved to the connector's Additional Configuration tab.
• dLocal (DLO-EP1): Support has been added for PuntoXpress and PayCash in Costa Rica.
• HUA NAN COMMERCIAL BANK (HNCB-EP2-HBQR): The key version used for encryption is now a configuration option.
• Paynetics (PNE-EP1-CC): Added API documentation for Paynetics.
• PAYONE (PASIX-EP3-CC): Added API documentation for Payone.
• Worldline (ING-EP2-CC): Fixed an issue where tokens are flagged as single use when they should be flagged as recurring. These tokens can now be reused.

Added​

• Adyen (ADY): Added a new data fetcher for settlements provided by Izyico.
• Zona Virtual SA - Zonapagos (ZONA): Zona Virtual is a Colombian company with 23 years of experience in the e-commerce sector. The ZonaPagos adapter support payments via credit card and Pagos Seguros en Línea.

Fixed​

• checkout.com (CHE): Added support for "Partial Capture" settlement entries.
• GoCardless (GOC): Fixed an issue with register transactions in the new server-to-server flow.
• Nuvei (NUV-EP1-CC): Updated the API documentation to include mapping information.
• Shift4 (CRE-EP1-CC): Fixed an issue with how UUIDs are formatted in failover transactions.
• Sofort (SOF-EP2-SOF): Fixed an issue with refunds that would change the status of the original transaction from success to error.
• Unzer (UNZER-EP1): The orderId in capture requests now uses the additionalId1 in the preauthorize transaction.
• Valitor (VALIT-EP1-CC): Fixed an issue with duplicated preauthorize transactions in settlements.

Misc​

Added​

• API Documentation: Updated the API documentation to include information on the bin_digits parameter.

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​

Fixed​

• Transaction Details: Additional headers for callbacks including Content-Type, Accept and User-Agent are now added to the postback transaction logs in the transaction details view when the postback:send-test-plain-header or postback:send-useragent-header are set in the connector settings.
• Transaction Export: Fixed an issue with the export of transaction data for merchants with mult-merchant access.
• UI Navigation: The Croatian and Slovenian translations have been updated.

Adapters​

Changed​

• Braintree (BRA-EP2-CC): The connector configuration has been updated, see the documentation for more information.
• Braintree (BRA-EP1): The additionalId1 field is now mapped to the descriptor name instead of the descriptor URL.
• Cybersource (CYS-EP1-CC): Updated the description of auxiliary data in the documentation.
• DPO Pay (PAYGA-PYGT): The DPO Pay adapter now supports preauthorize, capture and void transactions for credit cards.
• Worldpay (WOR-EP1-CC): The API documentation has been updated to include information on which parameters are mandatory for the Worldpay WPG PCI adapter.

Fixed​

• ATOM (an NTT DATA Company) (ATOM-EP1-CC): Fixed an error with retrieving the settlement that was introduced in an earlier change.
• Braintree (BRA): The createdAt timestamp supplied in Braintree's postback is now used as the timestamp for PayPal chargebacks.
• DPO Pay (PAYGA): Fixed an issue that prevented settlements from being processed due to an invalid date format.
• EPG Financial Services Limited (EPG-EP01-PAYLA): If the additionalId1 field is not provided as part of the payout request, the alias of the referenced debit transaction is used as a fallback option.
• GoCardless (GOC-EP1): Fixed an issue with the server-to-server flow caused by a missing parameter.
• Valitor (VALIT-EP1-CC): Fixed an issue with settlements caused by duplicate transaction lifecycle IDs.

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.