Dynamic Output Addresses Now Active Across All Dashboard Linked Requests

We are introducing an important improvement to how BlockBee handles output addresses across multiple request types.

Previously, every generated deposit address had a fixed output address that could not change after creation. This behavior remains the same for API requests that explicitly include an address parameter. When an API request defines the output address, the value is locked in permanently.

For all other cases, output addresses are now dynamic. Any payment request that relies on the dashboard configured address will always use the most up to date address at processing time. This includes:

• API requests that do not set an address parameter
• All Checkout requests
• All Subscription requests
• All Payment Links requests
• All Storefront requests
• All POS app requests

You can update the receiving address for any supported chain in your BlockBee dashboard at any time, and all newly created payment requests in these categories will automatically use your latest configuration.

Important notes:

• This new behavior only applies to payment requests created from now onward. Any request generated before this change will continue to use the fixed output address that was set at the time it was created.
• If you delete your address for a specific chain from the dashboard, BlockBee will fall back to the address that was set at the time the deposit address was originally created, ensuring every payment always has a valid destination.

This upgrade gives you more flexibility, improves operational workflows, and removes the need to recreate payment requests whenever your receiving address changes.

If you have any questions or need help adjusting your configuration, our support team is ready to assist.