HomeGuidesRecipesAPI ReferenceChangelog
Log In
Changelog
These docs are for v2.1.1. Click to read the latest docs for v2.2.0.
Back to All
improved

SANDBOX - v2.1.9 - 2024-10-09

about 1 month ago by Remi Tuyaerts

We’re excited to announce the sandbox release of version 2.1.9, bringing several important bug fixes and enhancements to our Payments API. This update focuses on improving transaction reliability, expanding blockchain support, and includes changes that may affect your integration. Please review the details below. 🚀

Deployment Timeline 📅

  • Sandbox: October 09, 2024
  • Production: Scheduled for next Wednesday, October 16, 2024
    We reserve the right to adjust the scheduled release date as needed.

Key Changes Affecting API Schema ⚠️

These changes may require you to update your integration.

1. Webhook SubType Correction 🔄

  • What Changed: Webhooks will now correctly send subType: 'PENDING' instead of subType: 'FAILED' when a crypto transfer fails due to missing liquidity.
  • Action Required: Update your webhook handling logic to accommodate the updated subType.

2. Create Ledger Endpoint Update 📝

  • What Changed: The create ledger endpoints now return only the uuid of the ledger, simplifying the response.
  • Affected Endpoints:
    • POST /user/bank-account/unblock
    • POST /corporate/{corporate_uuid}/bank-account/unblock
  • Action Required: Update your integration to handle the new response format.

3. Simulation Endpoint Compatibility 🧪

  • What Changed: The /user/bank-account/unblock/{account_uuid}/simulate endpoint now supports additional Payment Service Providers (PSPs).
  • Action Required: You can now simulate bank account operations with all supported PSPs, expanding your testing capabilities.

4. Input Normalization on Endpoints ✨

  • What Changed: Inputs for certain POST and PATCH endpoints are now normalized to match specific character patterns to enhance data consistency.
  • Affected Endpoints: Various user and corporate account creation and update endpoints.
  • Action Required: Ensure that your input data complies with the new validation rules to prevent errors.

5. API Documentation Updates 📖

  • What Changed: Corrected syntax in API documentation for uppercase IBAN and IFSC codes.
  • Action Required: Review the updated documentation to ensure correct implementation of these fields.

Key Bug Fixes 🛠️

1. Offramp Transaction Reliability 🚦

  • Issue Fixed: Offramps were failing due to incorrect ledger identification.
  • Benefit: Improved stability and success rate of offramp transactions.

2. Plaid Webhook Handling 📲

  • Issue Fixed: Onramps were not triggered from Plaid webhooks in production.
  • Benefit: Ensures seamless initiation of onramps from Plaid, improving the user experience.

3. Ledger Fetching for PKR/INR 🌏

  • Issue Fixed: Offramps to PKR and INR currencies failed due to ledger fetching issues.
  • Benefit: Enables successful transactions in these currencies.

Enhancements & New Features 🌟

1. ERC-1271 Support Verified 🔐

  • What's New: Confirmed support for ERC-1271 in our Sign-In with Ethereum (SIWE) login endpoint.
  • Benefit: Merchants can now authenticate users with smart contract wallets, expanding integration options.

2. Improved Blockchain Transaction Handling ⚙️

  • Enhancement: Implemented robust blockchain transaction handling for Ethereum Virtual Machine (EVM) compatible networks.
  • Benefit: Increased reliability and efficiency of blockchain transactions, especially under high-load conditions.

3. Offramp Simulation Enabled for Additional Blockchains 🚀

  • What's New: Offramp simulation is now available for additional blockchains in sandbox environments.
  • Benefit: Allows developers to test offramps effectively before going live.

General Improvements 🔧

  • Reliability Enhancements: Made several internal improvements to enhance transaction reliability and system performance.
  • Reduced Unnecessary Logs: Updated configurations to minimize excessive logging, improving system efficiency.
  • Disabled Legacy Error Emails: Stopped sending legacy error emails to prevent inbox clutter and streamline notifications.

Action Required 🔧

  • Update Your Integrations:
    • Webhook Handling: Adjust your systems to accommodate the corrected subType in webhook notifications.
    • Ledger Endpoint Responses: Update your code to handle the simplified response from the create ledger endpoints.
    • Input Validation: Ensure that all input data for POST and PATCH endpoints complies with the new validation rules.
  • Review API Documentation: Check the updated API docs for changes regarding IBAN, IFSC codes, and input normalization.
  • Test in Sandbox: We recommend testing these changes in the sandbox environment before the production release to ensure a smooth transition.

Coming Soon: Version 2.2.0 👀

Stay tuned for our next release, which will introduce even more exciting features and enhancements to the Payments API. We're committed to continually improving your experience! 🔥

Thank you for your continued trust in Unblock for your payment processing needs. If you have any questions or need assistance, please don’t hesitate to get in touch. 💬