Skip to main content

10 posts tagged with "User Management"

View All Tags

Gateway — v.24.16

API

Added

  • Provisioning API: Added processing:copy-customer-data-from-customer-profile-transaction to the connector settings.

Features

Changed

  • User Management:
    • Removed deprecated ACL abilities connector.WorldlineOgone.PostFinanceCard and connector.WorldlineOgone.PostFinanceEFinance.
    • Migrated existing deprecated ACL abilities to connector.IngenicoDirect.PostFinancePay.

Added

  • Connector Configuration: Add new connector setting Customer Data: Copy from customer profile transaction. If activated the shopper's information is added from the transaction that was used to create a customer profile.

Fixed

  • Job Configuration: Fixed an issue that could occur when saving Global Job Schedules.
  • Post Processing Jobs: Fixed the post-processing filter Transaction is not referenced in any job of this Job Type, ensuring it now correctly picks up transactions already collected by other job types.
  • Post Processing Jobs: Fixed the bug where the default state for newly created job schedules would be scheduled instead of Manual trigger only.
  • Transaction List: Fixed the advanced search to also filter for the meta_connector_guid when searching for transactions of a connector.
  • Transaction List: Fixed handling operators IS_EMPTY and IS_NOT_EMPTY for the advanced search.

Adapters

Changed

  • dLocal (DLO): Added support for settlement handling.
  • Klarna (KLW): Updated and restructured the documentation according to our latest guidelines.
  • PayPal Complete Payments - PPCP (PPCP-EP1-CC): Added support for the PayPal Advanced Credit Cards and Debit Card (ACDC) method.
  • PayTabs (PAYT-EP01-CCRD): Added support for the redirect credit-card payment method.
  • PXP (PXP-EP1-INST): Added support for Discover credit cards.
  • Straight2Bank Pay (STRAI): Added the configuration option daysOffset to delay data fetching a certain number of days.
  • Worldpay (WOR-EP1): Added support for chargeback handling through webhooks.

Fixed

  • Adyen (ADY-EP1, ADY-EP2, ADY-EP3): Fixes handling of second chargebacks for Adyen settlements.
  • Alipay - Ant Group (ANT-EP1-ALI): Limit retries of failed transactions to three attempts.
  • Global Payments (GBP): Fixed specifying the settlement amount.
  • PAYONE (PASIX): Fixed handling of negative fee amounts in settlements for interchange fees of refunded transactions.
  • PXP (PXP-EP1-INST): Fixed incorrectly disabled partial capture, partial void, and incremental authorization.

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

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.

Gateway — v.24.7

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.

Gateway — v.24.2

API

Fixed

  • Transaction API: Fixed an issue where adapter error codes (errors.adapterCode) were sometimes returned as a numeric value instead of as a string.

Features

Changed

  • Connector Configuration: When adding a connector or meta-connector, the public integration key is now prefilled with a random valid value. This value can still be edited and realtime feedback is provided on whether the edited value is valid.
  • Connector Settings: Ensured referenceUuid is present in all cases when the connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response is enabled.
  • Virtual Terminal: The virtual terminal has been reworked, including the Transaction, Customer, Credit Card and Payment details sections. New permissions have been introduced to handle the new streamlined form. Some of the business logic has been reworked or extended and GST calculations are now included in the Transaction section. The type of transactions available in the virtual terminal can now also be restricted using a new tenant/connector setting. For more information, refer to the User Manual.

Added

  • Connector Settings: Added a new connector setting Postback/Status: Include captureId for debit transactions in postback request and status response if available to enable sending captureId in callback requests and status responses.

Fixed

  • BI Data Source: Fixed the recurring status for chargeback and chargeback reversal transactions in the BI data source.
  • Post Processing Jobs: Fixed an issue that would cause an error if the ID for a post processing job schedule was incorrect.
  • Post Processing Jobs: It is now possible to add static values to aggregated lines in CSV exports by defining a default value for the static column field.
  • Provider Settlements and Reconciliation: Settlements can now be resolved using all available IDs.
  • Provider Settlements and Reconciliation: When assigning a connector to a provider, it is now possible to view and select the connectors for these merchants assigned to sub-tenants.
  • User Management: Fixed an issue that could result in an error when a user attempts to change their password. In such cases, users are now redirected to the login page instead.

Adapters

Changed

  • Adyen (ADY-EP1-CC, ADY-EP3-CC): Added support for network tokenization.
  • dLocal (DLO-EP1): Added an option to omit the callback_url parameter, as this removes the back button on the dLocal payment page.
  • Stripe (STRV2-EP1-CC): 3DS result data from Stripe is now included in callbacks.
  • Worldpay (WOR-EP1): Added a new setting, Debit waits for webhook, to postpone marking a debit transaction as successful. This setting waits for the capture event webhook notification instead of relying solely on the authorization webhook.

Added

  • Worldline (ING-EP2-MUB): Added support for the Multibanco payment method (bank transfer). Multibanco is the largest interbank network in Portugal.

Fixed

  • Adyen (ADY-EP3): Updated the API documentation to include the merchantOrderReference parameter.
  • Braintree (BRA): Added support for settling chargeback reversals.
  • DPO Pay (PAYGA-PYGT-CC): Updated the adapter documentation to cover new capabilities (PreAuth, Void, Capture).
  • E-Comprocessing, eMerchantPay (ECP-EP1, EME-EP3-CC): Added API documentation for eMerchantPay and E-Comprocessing.
  • MultiSafepay (MUL-EP1): Fixed a typo in the status used by callback handling for chargebacks.
  • Nuvei (NUV-EP1): Updated the API documentation to include information on mandatory fields.
  • Nuvei (NUV-EP1-CC): Fixed an issue that caused the transaction ID to be incorrectly set to IXOPAY's internal UUID until the callback 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.

Gateway — v.24.1

Features

Changed

  • Job Configuration: Strengthened TLS verification for the target host when utilizing the Send document to endpoint post-processing step.

Added

  • Connector Settings:
    • Added a new connector setting Postback/Status: include original adapter reference id in postback request and status response to enable sending extraData["originalAdapterReferenceId"] in callback requests and status responses for all transaction types.
    • Added a new connector setting Postback/Status: include reference uuid for all subsequent transactions in postback request and status response to enable sending referenceUuid in callback requests and status responses for all transaction types. This includes transactions referenced directly via the referenceUuid field, as well as related transactions in the customerProfileData.customerProfileGuid field of the customer profile, provided the customer profile belongs to the affected merchant.

Fixed

  • Customer Profiles: Fixed an issue where manually detaching a payment instrument without deleting it from a customer profile caused unwanted behavior.
  • Provider Settlements and Reconciliation: The callback URL for chargebacks initiated through settlement processing is determined automatically. If the related transaction lacks a callback URL, the transaction tree is searched for an appropriate destination.
  • User Management: Extended the Include Sub-Tenants filter to include sub-tenants of sub-tenants, not just direct sub-tenants.

Adapters

Changed

  • Adyen (ADY-EP3-MBWAY): Added support for the MB Way payment method to Adyen Checkout. MB WAY, provided by MULTIBANCO, serves as a mobile wallet within Portugal's interbank payment network.
  • checkout.com (CHE-EP2-IDE): Added support for the iDEAL payment method using the checkout.com NAS platform. iDEAL is an online payment method that enables consumers to pay online through their own bank. Payments are made via bank app or online banking.
  • Klarna (KLW-EP1):
    • Added documentation on required parameters.
    • Added fallback logic to populate essential customer fields when shipping data is missing.
  • Worldline (ING-EP2): Added support for the Sofort payment method. Sofort is the predominant online banking method in countries such as Germany, Austria, Switzerland and Belgium and continues to expand its global reach.

Fixed

  • 2C2P (2C2P-EP1): Improved the handling of empty HTTP responses received from 2C2P.
  • Alignet (ALI-EP01-CC):
    • Updated documentation to clarify that customer shipping address first and last name parameters are optional.
    • Included extraData from referenced transactions in follow-up transactions.
  • Bitpay (BTP-EP1): Fixed cancelUrl forwarding to Bitpay and introduced logging for Bitpay invoice adapter calls.
  • Braintree (BRA): Skip loading transaction data when receiving Braintree callbacks without a paymentId.
  • checkout.com (CHE):
    • Fixed an issue where settlement processing failed if a previous data fetcher returned no data.
    • Updated documentation with more detailed information about extraData fields relevant to the recipient of account funding transactions.
  • Sepa Express (SEP): Improved UTF-8 handling in the account holder field to handle invalid characters more effectively.
  • Unzer (UNZER-EP1): Fixed an issue with handling empty responses from the PSP.
  • Volt (VOL-EP1): Enhanced callback processing to immediately mark transactions as successful upon receiving a COMPLETED status callback and the successOnSettle connector setting is enabled.
  • Worldline (ING-EP2): Fixed an issue with follow-up debit transactions that reference transactions based on imported IBAN tokens.

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.