7 posts tagged with "PAYONE"

Gateway API​

Changed​

• Transaction API: Update API validation for the browserTimezone field in 3DS data to accept values prefixed with a plus sign (e.g., "+0300"), which were previously rejected, and to enforce a maximum string length of 4 characters for this field.

Added​

• Customer profiles API: Add attachPaymentInstrument and detachPaymentInstrument API endpoints to customer profiles, allowing users to attach or detach payment instruments using profile identifiers (GUID or customer identification) and a transaction UUID.

Gateway Features​

Added​

• Connector Settings: Add a new connector setting Disable Refund After Chargeback, which controls whether the refund option is available for transactions that have undergone a chargeback.

Gateway Adapters​

Changed​

• Adyen (ADY-EP4-CC): Add support for preauthorize and capture transactions.
• checkout.com (CHE-EP2-BIZ): Add support for the new payment method Bizum. Bizum is a fast and secure mobile payment method widely used in Spain.
• dLocal (DLO-EP1-SINMO): Add support for the new payment method Sinpe Móvil. SINPE Móvil in Costa Rica facilitates money transfers through SMS, allowing users to send funds to another mobile phone number without needing the recipient’s bank account information.
• PAYONE (PASIX-EP1): Add documentation for the extraData.avsCheck field, which is used to enable Address Verification System (AVS) checks.
• Worldline (ING-EP2-IDE): Add support for the new payment method iDeal. 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.
• Worldpay (WOR-EP1-KLAPN): Update documentation to specify that item.totalAmount is a required field for the payment method Klarna.

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

API​

Fixed​

• Provisioning API: Resolved an error in the Provisioning API by adding null checks when building response objects for meta connectors without a default connector.
• Push API: Fixed handling of request bodies with invalid JSON.

Features​

Changed​

• Customer Profiles: Made the action column in the customer profile payment instruments table non-sortable.
• Transaction List: Increased the number of displayed connectors in the advanced search form from 100 to 700.

Added​

• Post Processing Jobs: Added the ability to export transaction extra data in post-processing export strategies, including "Write customized Settlement CSV", "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV". Also, added "key" and "default" column configurations to "Export Transactions to XLSX (Version 2)", "Export Transactions to XLSX", and "Export Transactions to CSV".

Fixed​

• Account Updater: Improved the account updater to consider BIN lookup results alongside the card type for more accurate processing.
• Account Updater: Fixed an issue in the Account Updater that caused cards to appear as updated twice in the batch for clients.
• Connector Settings: Fixed a bug that caused the connector settings "Transactions: Expire automatically after (x) minutes" and "Expires pending transactions after given minutes" to not work when added as Global Settings.
• Customer Profiles: Use the correct customer profile container for meta connectors.
• Dashboard: Fixed an issue where the pivot table couldn’t resolve the connector list, causing multiple selections to show as ‘n/a’.
• Dashboard: Fixed a dashboard issue where GUIDs were displayed instead of merchant names.
• Hosted Payment Pages: Removed async from Google Pay JS on hosted payment pages to enable synchronous loading, ensuring the Google Pay button displays reliably.
• Transaction List: Updated transaction list links to ensure they work correctly by including a default status, preventing 404 errors.
• Virtual Terminal: Fixed issues in the Virtual Terminal for direct debit transactions by preventing mandate date validation when the field is empty and correcting format validation to display proper error messages instead of "unknown error".

Adapters​

Changed​

• Klarna (KLW-EP1): Added a connector setting "treat the BACK status from klarna as CANCELLED".
• Mashreq (MASH-EP01): Added support for debit auto-capture.
• PAYONE (PASIX): Add new mappings for settlements:
  • Markup fee (condCode 701)
  • Dispute fee (condCode 55).
• PXP (PXP-EP1-INST): Added support for the in-store card deposit payment method.
• Sepa Express (SEP-EP3-SEP): Added support for settlement handling.
• Worldline (ING-EP2): Always store the adapter transaction identifier if present to properly handle subsequent transactions.

Fixed​

• American Express (AMX-EP1-AMX): Fixed system trace audit number (STAN) issue by using a modulus operation on the transaction ID to ensure it fits within base36 encoding limits.
• iyzico (IYZ): Fixed settlement handling for Iyzico to correctly parse the batch number for all settlement objects.
• Spreedly (SPR-EP1-CC): Fixed date parsing to correctly handle microseconds included by the PSP.
• Transbank (TRANS-TSB1): Fixed handling of empty 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​

• payment.js: In addition to styling the CVV and card number fields on checkout pages, it is now also possible to apply styles to their placeholder text.

Features​

Changed​

• Provider Settlements and Reconciliation: Updated the data fetcher to:
  • Validate input data
  • Inform users when the data fetcher is saved with missing or invalid data
  • Allow the data fetcher's interval to be set to 0 (no retrieval). This is now also the default value for new data fetchers.

Added​

• Audit Log: Added the ability to export user management audit logs that includes information on users, such as the date the user was added, modified or deleted, their last login and the tenant the user is assigned to. These export logs can be found under Security Center on the Audit Log Export tab.

Fixed​

• Documentation: Updated the Schedule API documentation to address incorrect information.
• Documentation: Fixed an issue with the signature testing tool that would cause it to generate an incorrect signature due to a difference in how the URL path is generated compared to the IXOPAY gateway.
• Provider Settlements and Reconciliation: Fixed an issue with chargeback reversals that would result in an error that the chargeback could not be found. This was caused by postback notifications that contain the same reference ID for both capture and preauthorization transactions.
• Risk Profile: Fixed an issue that would prevent Starter and Growth users from editing the risk ruleset. When attempting to edit the ruleset, an error message was displayed that only one risk profile is allowed.
• UI Navigation: Fixed an issue with Apple Pay and Google Pay transactions showing the incorrect icon for the token type.

Adapters​

Changed​

• PAYONE (PASIX):
  • Fixed an issue with mapping fees for SIX via the E-Link adapter. New mappings have been added for the scheme fees and interchange fees to address this.
  • Updated the handling of settlements to use the current date and time as the fallback value for the payment date and settlement number if this value is not present. This was the case if the refunded amount was larger than the captured amount. Furthermore, if a payment number is available, this is used as the payment reference.

Fixed​

• China UMS (UMS-EP1-H5): Fixed an issue with missing adapter-related data in the postback notification.
• Paysafecard (PSC-EP1): Fixed an issue that would cause refunds to fail due to the adapter transaction ID being truncated.

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.