3 posts tagged with "Amazon Payment Services"

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

• UI Navigation:
  • If the user only has access to a single connector, it is now automatically selected in the virtual terminal.
  • The last selected connector is stored locally to prevent having to re-select it for future transactions.

Added​

• BI Data Source: Scheme IDs are now available for data exports and post-processing.
• Connector Configuration: Added a new project setting, Manipulation: Field Operation that can be used to manipulate data at the connector level prior to sending the data to the PSP. It is currently possible to truncate the data after a defined number of characters using this option. More operations will be added in the future.
• Fee Management: Added the ability to specify the customer's billing state for fees.
• UI Navigation: Added information on the deployed version to both the gateway and documentation.

Fixed​

• Fee Management: Fixed an issue that would result in an error if no target fee set has been specified and the source fee set is assigned to a sub-tenant.
• UI Navigation: Fixed an issue that prevented archived jobs from being restored when in the table view.
• Virtual Terminal: Fixed an error that could occur when calculating surcharges if no credit card number has been entered.

Adapters​

Changed​

• American Express (AMX-EP1-AMX): Added support for Apple Pay.
• China UMS (UMS-EP1): Added the optional expireTime parameter to the payload. The value of this parameter is taken from the extraData field. If the parameter is not provided there, it is taken from the project settings.
• Cybersource (CYS-EP1-CC): The forwardedAcquirerCode field is now available for postback notifications.
• HypYaad (HYP-EP1-CC): Added support for settlements in CSV format and stored on an SFTP server.
• Klarna (KLW-EP1): The customer.birthDate field has been changed from required to optional.
• PXP (PXP-EP1-CC): The SchemeTransactionIdentifier, SchemeSettlementDate and DinersRetrievalReferenceNumber in callbacks are now stored for use in recurring transactions.
• SIA (SIA-E01): Added support for void and partial captures.

Added​

• Paymee (PAYME-EP1-CCRD): Paymee is a Tunisian payment gateway that accepts credit card payments via a redirect link.
• Sampath Bank (SAMPA-SVNP1-BTR): Sampath is a secure Sri Lankan online payment platform. The adapter supports bank transfers.

Fixed​

• Adyen (ADY):
  • When submitting a transaction using a hosted payment page, clicking on the back button caused the transaction to be resubmitted. This caused two transactions to be sent to the PSP, but IXOPAY only counts this as a single transaction. The duplicate transaction is automatically closed by the PSP, which can overwrite the correct transaction ID of the transaction in IXOPAY.
  • Fixed an issue with settlement notifications that caused settlements to be ignored.
• Amazon Payment Services (AMAZO):
  • A new option has been added that supports SHA-512 alongside the previously supported SHA-256 encryption. This setting should be configured in IXOPAY to match the one configured in the Amazon settings.
  • Fixed an issue generating settlement reports that would only occur when an existing settlement report was re-generated.
• China UMS (UMS): Fixed an issue that prevented the status of pending transactions from being polled correctly.
• China UMS (UMS-EP1): A refund order ID has been added, which now allows multiple refunds.
• Klarna (KLW-EP1): Fixed a number of issues that could occur in cases where the customer's birthdate is missing.
• NMI (NMI-EP1): Fixed an issue where a type error would occur if no related transaction is present and no extra data is set for a credit card connector. The expected data type is an array; if no data is available, an empty array is now used.
• Worldline (ING-EP6): Fixed an issue that could cause successful refunds to remain stuck in a pending state.

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