useManagerFunds enhancement

We have shipped two enhancements to the existing useManagerFunds feature in the payment creation flow.

We added a new parameter useManagerFundsAmount in the Create a new payment endpoint, which allows you to indicate the component or specify the amount which you would like to draw from the Manager Account to fund the payment. This parameter is only accepted when useManagerFunds = true. If there is insufficient balance in either account based on the specified split, no internal transfers will be made and payment will remain in awaiting_funds.

useManagerFundsAmount.component accepts four different type:
- full_amount: The entire required sender amount will be drawn from the Manager Account, and the Managed Account's balance is untouched.
- fixed_fee: The payment's fixed fee will be drawn from the Manager Account, and the remaining amount to be funded with the Managed Account's balance. I
- variable_fee: The payment's variable fee will be drawn from the Manager Account, and the remaining amount to be funded with the Managed Account's balance.
- custom: Specify an amount to be drawn from the Manager Account under component.amount, and the remaining amount to be funded with the Managed Account's balance.
We also made some changes to how refunded payment behaves when useManagerFunds is used. Previously, when a payment is cancelled and refunded, the refunded amount will sit in the Managed Account even if the funds were originally drawn from the Manager Account. Now, we automatically transfer the amount initially drawn from the Manager Account back to the original source. For example, if $500 was drawn from the Manager Account to fund a $700 payment, when the payment is refunded, we will refund $700 to the Managed Account and automatically transfer $500 back to the Manager. This ensures that the funds return to its original source instead of needing additional manual transfers or reconciliation.

Please reach out to us if you have any questions or clarifications on the changes.