Skip to main content

10 posts tagged with "User Management"

View All Tags

v.24.0

API

Fixed

  • Batch Upload API: Fixed a number of issues with the Batch Upload API:
    • Fixed a bug that generated an incorrect output format when an error occurred.
    • Fixed an issue when querying the status of a batch request that would result in an HTML response being generated when the batch ID referenced a non-existent batch. A JSON response is now generated containing "batch not found".
    • In cases where validation errors (e.g. the merchantTransactionId is already assigned) prevents a transaction from being created, the transaction was not written to the output at all. The output now includes a line with success = false, along with an error message in the output file for every transaction that could not be created.
  • Transaction API: Removed the thousands separator from the amount field in callbacks for transactions with a surcharge fee.

Features

Changed

  • UI: The Tools section in the platform has been overhauled. The entries previously located here have been moved to more relevant parts of the platform - this includes options such as BitPay pairing and Tokenization.

Added

  • Job Configuration: Added a new feature to automatically add comments to potentially fraudulent transactions and send out emails with relevant information.

Fixed

  • Connector Settings: Fixed a minor visual issue that occurred when selecting the same connector setting twice. The setting was then displayed twice. The setting is now only displayed once.
  • Post Processing Setting: Fixed an issue with sending callbacks for transactions created via settlements.
  • Transaction List Filter: Fixed an issue with the filter for transactions created in test mode not being applied correctly.
  • User Management: Fixed an issue where users were unable to add new merchant users unless they had the frontend.users.roles.edit permission.

Adapters

Changed

  • Amazon Payment Services (AMAZO-EP1-CC): Added support for the new JSON settlement format.

Added

  • Alignet (ALI-EP01-CC): Alignet is a leading technology company based in Peru, specializing in solutions for secure electronic transactions. They pioneered the use of 3-D Secure in Latin America and are a key supplier of major banks in the region. The adapter supports credit card transactions.
  • Braintree (BRA-EP1): Added support for the Blik payment method. Blik allows for bank transfers and covers all major Polish banks.
  • PayTabs (PAYT-EP01-VALU): PayTabs is a payment processing solution specializing in seamless online transactions in areas such as the Middle East, North Africa and Southeast Asia. The adapter currently supports payments using the valU BNPL payment method in Egypt.
  • Worldline (ING-EP2): Added a new endpoint as well as the option to switch between old and new endpoints in the configuration.
  • Worldpay, checkout.com (CHE, WOR): Updated the API documentation for checkout.com and WorldPay WPG to include AVS and CVV responses.

Fixed

  • Adyen (ADY-EP3): Fixed an issue with missing notification verification for AdyenCheckout.
  • Adyen (ADY-EP3-RIV):
    • Added support for partial captures for the Riverty payment method using Adyen Checkout.
    • The IP address field is now optional instead of mandatory when using the Riverty payment method with AdyenCheckout.
  • Bitpay (BTP-EP1-CR): Fixed pairing issues with the new Bitpay connector configuration.
  • Braintree (BRA-EP2): Fixed an issue with Braintree's Address Verification Service.
  • checkout.com (CHE):
    • Fixed the handling of settlements for transactions with multiple partial captures.
    • Multiple fees are now supported for a single transaction in the settlement report.
  • Klarna (KLW-EP1-APM): HTTP 400 responses are now mapped correctly.
  • Mashreq (MASH-EP01): Added handling for the status "Awaited", which previously returned an error (due to this status not being documented by CCAvenue). The transaction is now set to pending when this status is received.
  • MultiSafepay (MUL): Fixed an issue with the settlement fetcher that prevented settlements from being retrieved.
  • Nuvei (NUV-EP2): Enabled support for partial captures.
  • Zona Virtual SA - Zonapagos (ZONA-EP1):
    • A unique numeric value is now generated and sent to Zona Virtual as the payment ID Id_pago. This value is stored in the additionalId1 field in IXOPAY as a payment reference that is used if the payment fails.
    • Changes have been made to the mandatory fields. The following fields are no longer mandatory: merchantMetaData, extraData.idType, customer.identification.
    • Fixed the default error mapping.
    • Added mapping for the error when a payment cannot be found.

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.

v.23.22

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.

v.23.16

Features

Changed

  • 3DS: Rolled back changes that removed 3DS postback data for merchants using external MPI.
  • Transaction details: The payment token is now included in the customer profile data in callbacks and API status calls.

Added

  • Post Processing: The filter in the Collect All Transactions (in period) Post Processing collecting step now supports filtering adapter errors and internal errors by the date on which their status changed.
  • Provider settlements and Reconciliation: Added a new tab to the conversion rate system settings that allows deviation tolerances to be defined for currency pairs per tenant. This is then used to verify settlements rather than the tenant's global tolerance or default tolerance (0.02%).
  • Settings: Added a new project setting, Postback: Include Basic Auth header, which allows a header to be sent for basic-auth postback. This setting is also available as a global connector setting.

Fixed

  • Account Updater: Fixed an issue where only one level of sub-tenants were filtered. Fixed an issue that would cause an error when changing the master tenant in the detailed view.
  • Customer profile: Fixed an issue that triggered an error when creating a customer profile via the API's customerProfileData field without setting any customer data in the transaction.
  • Pay-by-Link: Fixed an issue that would result in an empty redirect URL. Fixed an issue with redirects to expired pay-by-link transactions without an error URL that would cause an exception. The correct page is now displayed.
  • Pay-by-Link: Fixed an issue that caused all pay-by-link transactions to be withRegister transactions. It is now possible to choose whether the transaction should be a withRegister transaction or not using the with Register (Store Payment Instrument for Card-on-File payments) checkbox.
  • Post Processing: Fixed an issue that would cause an error for sub-tenants when attempting to select job configuration templates created at the parent provider level if no fee entities were available in the template.
  • Risk Engine: Fixed an issue with the Count of different credit cards of same device risk rule if no customer or browser data is available.

Adapters

Changed

  • checkout.com (CHE-EP1-CC): The AVS and CVV results are now added to the extraData in callbacks if available in the response.
  • DPO Pay (PAYGA-PYGT-PMR): Added support for the USSD payment method.
  • eMerchantPay (EME): Added support for chargeback reasons, which are now forwarded to merchants.
  • Nuvei (NUV): Updated the Westpac settlement handling.
  • Paysafecard (PSC): Added support for payouts.
  • Redsys (RED-EP2-BIZ): Added support for refund transactions.

Added

  • Nuvei (NUV-EP1-CC): Added support for chargeback notifications from Nuvei.

Removed

  • Bank of America (BOFA-EP1-ACH): The Addenda row was removed from the NACHA file when using the WEB format, as it is not required.

Fixed

  • Nuvei (NUV-EP1-CC): Fixed issues with the references to related transactions, which should either contain the Nuvei transaction ID, the transaction ID of the previous 3DS request, or the transaction ID of the authorized payment.
  • Nuvei (NUV): To handle issues with settlements, a new optional configuration setting has been added for the reconciliation data fetcher ID, which checks whether the system needs to wait for the CB report for the same date when retrieving settlements.
  • PPRO (PPR-EP1): Fixed an issue with settlements, that is caused by PPRO sometimes providing multiple files with the initial file only containing volume data, and subsequent files containing the actual transaction settlement data. A new option is now available in the data fetcher configuration, Only retrieve settlements if all fees and volume files are present that checks whether all settlement files are present before retrieving and processing the files.
  • Valitor (VALIT-EP1-CC): Fixed an issue related to duplicate transaction IDs issued by Valitor that would cause refunds to be ignored in settlements due to another transaction having the same ID.
  • Volt (VOL-EP1): Fixed an issue with Volt settlement files caused by the formatting of the CSV data.

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.

v.23.12

Features

Added

  • FAST Editor: Add a new placeholder in the FAST Editor to include the surchargeAmount in the hosted payment pages.
  • Post Processing: Enable clients to create reports of account updates using the post-processing engine.
  • Currency: Add ZWL as available currency.

Fixed

  • Connector Settings: Fix the connector setting to calculate the surcharge fee.
  • User Management: Fix an issue that archived users where still visible for merchants users.

Adapters

Added

  • Adyen Checkout (ADY-EP3-PCQ): Add refund and partial refund support for Payconiq by Bancontact Mobile for Adyen Checkout.
  • Alipay - Ant Group (ANT-EP1-ALIPL): Add Alipay+ shadow link (iMock - mocked responses) support for Alipay+ sandbox accounts.
  • Braintree (BRA-EP2-CC): Add two new file types for the Braintree settlement data fetcher to be configured.
  • Straight2Bank Pay (STRAI-E01-CC): Add refund transaction type for the Straight2Bank adapter.

Fixed

  • DOKU (DOKU-EP01): Make the DOKU settlement retrieval filter for filenames configurable.
  • DOKU (DOKU-EP01): Fix to allow the DOKU settlement currency configuration to be saved.
  • DPO Pay (PAYGA-PYGT-CC): Add mandatory parameter refunddetail for refund transactions.
  • DPO Pay (PAYGA-PYGT-CC): Fix handling of follow-up preauthorize, debit and payout transactions in combination with customer profile tokens.
  • Payabl (P21-EP1): Fix the behavior to set refunds immediately to success.
  • Paypal (PPA-EP1-PPE): Add Wallet data in the transactions additional data for PayPal payout transactions.
  • Straight2Bank Pay (STRAI-E01): Fix the settlement handling for Straight2Bank adapter allowing the second adapter transaction id to be empty.
  • Straight2Bank Pay (STRAI-E01): Fix mapping of newly introduced gstFee to scheme fee and deduct the fee from payout.
  • Volt (Settlement): Add an additional data fetcher configuration parameter extra data: notificationSecret.
  • Worldline (ING-EP2-SEP): Fix the error mapping for errors received via callbacks from the PSPs and set the transactions correctly to declined instead of 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.

v.23.10

Features

Changed

  • Connector Settings: Extend connector setting "Set Customer Identification if empty" with the "Pseudo Random" option, allowing for the generation of a random ID to be assigned as the customer identification when left empty.
  • Multi-method connector: Redirect the customer to the appropriate URL when a redirect payment method is used without a payment template, preventing the "Unexpected redirect to payment page" error.
  • Virtual Terminal: The delayed capture interval can be set in days to add more convenience for virtual terminal users.

Added

  • Fee Management: Add GST fee support in the fee engine. Configure and map the GST (a percentage of the surcharge fee) as a fee entity and include it in a connector's fee set.
  • Post Processing Setting: Enable the "Reconciliation: Use reference merchant tx id for unknown transactions" setting for remote deregister and remote refund transactions.
  • Job Configuration: Introduce the ability to split jobs by cardType.
  • Provider Settlements and Reconciliation: Add the bank reference number as a new column in the "Recent Settlements" and "All Settlements" view, along with a filter option for bank reference number in the "All Settlements" view.
  • User Management: Simplify admin user management by adding a new filter option in the "Tenant User" view to include sub-tenant users in your filter results.

Fixed

  • Alerts: Fix an issue causing resolved alerts to remain visible to users.
  • Job Configuration: Fix job configuration setting "Display a negative total sum of the initial transaction amount plus fees" in order to handle negative net settlement refund amount.
  • Risk Profile: Allow users with the permission riskcheck.riskruleset.edit to edit the score card for a risk profile, resolving the limitation of requiring riskcheck.riskruleset.archive permission.
  • Transaction Details: Hide capture button for pre-authorize transactions that are already fully captured.

Adapters

Changed

  • Adyen (Settlement): Add support for skipped settlement files.
  • Adyen (ADY-EP3): Add metadata merchantTxId and additionalId1 to debit and preauthorize transactions.
  • Bank of America (BOFA-EP1-ACH): Remove the redundant connector setting initialTransactionState.
  • Braintree (BRA-EP2-AMX, BRA-EP2-CUP, BRA-EP2-DIN, BRA-EP2-DIS, BRA-EP2-JCB, BRA-EP2-MAS, and BRA-EP2-VIS): Add support for parsing the new disbursement settlement file format.
  • Six (Settlement): Add configuration options for SFTP host and root directory.
  • Straight2Bank Pay (STRAI-E01): Add a new connector configuration field, pspid, to enable PSP id overwriting for cases where clients receive this parameter from the PSP.
  • Straight2Bank Pay (STRAI-E01): Add new transactional fee types, markup and markup_vat, to the SCB settlement handling.
  • Valitor (VALIT-EP1): Improve handling of Valitor settlements for transactions with non-unique adapter transaction IDs or lifecycle transaction IDs.
  • WorldPay (WOR-EP1-CAB): Add support for CB (Carte Bleu and Carte Bancaire).
  • Worldline (ING-EP6): Improve settlement data handling by implementing the configuration option "Customized REGEX Pattern" in the Settlement Data Fetcher for better distinction.
  • eMerchantPay (EME-EP3): Add the orgTerminal parameter received by postback to transactions for cases of missing responses due to time-outs.

Added

  • Adyen (ADY-EP3-AMX, ADY-EP3-CAB, ADY-EP3-CAR, ADY-EP3-CUP, ADY-EP3-DIN, ADY-EP3-DIS, ADY-EP3-ELO, ADY-EP3-HIC, ADY-EP3-JCB, ADY-EP3-MAS, ADY-EP3-TRO, and ADY-EP3-VIS): Add support for the incremental authorization transaction type in the Adyen Checkout service platform.
  • PayU (PAU-E01): Added PayU Colombia.

Fixed

  • ATOM (ATOM-EP1-AMX, ATOM-EP1-DIN, ATOM-EP1-JCB, ATOM-EP1-MAS, ATOM-EP1-RUPAY, and ATOM-EP1-VIS): Fix settlement fee mapping to correct the net settlement amount calculation.
  • First Atlantic Commerce (FAC-EP1-MAS and FAC-EP1-VIS): Refine adapter integration in combination with customer profiles to support follow-up transactions.
  • Nuvei (NUV-EP1-AMX, NUV-EP1-CUP, NUV-EP1-DIN, NUV-EP1-MAS, and NUV-EP1-VIS): Fix issue causing follow-up void transactions to fail when the initial transactions experienced timeouts, that were later marked successful.
  • PPRO (PPR-EP1): Ensure accurate handling of separate settlement files by eliminating unexpected NULL value for netSettlementAmount when only submitting a fee for a transaction without a net settlement amount.
  • Worldline (ING-EP2-BTR): Fix failed refunds by adding the missing accountHolderName parameter.
  • Worldline (ING-EP2): Improve refund processing by adding the iban parameter to the refund payload and enabling refund notifications.

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.