depositCashBalance, so you can show your user the net cost before they confirm. Quote the same funding source, amount and deposit type that you will deposit with: the fee depends on all three.
The estimate is never lower than the fee the deposit is charged. When Fluz can’t tell in advance whether a debit card deposit will route as an account funding transaction (AFT), it quotes the higher of the two possible rates, so the charge can only come in at or below the estimate. Likewise, a GIFT_CARD_BALANCE deposit is charged the merchant category tier it is routed under; the estimate takes no merchant category, so it quotes the highest tier configured for the card’s BIN at that amount.
Arguments
GetDepositFeeEstimateInput!
required
The deposit to estimate: the amount, the deposit type, and exactly one funding source. See
GetDepositFeeEstimateInput.Example
A $30 debit card deposit into a cash balance, made through an application that charges its own 1.95% fee on account funding transactions:feeAmount values of feeBreakdown add up to fee. When no complete breakdown is available for the quote, feeBreakdown is an empty list; that does not mean the fee is zero, so always show fee as the total. Each part is rounded to the cent on its own, so a part can differ from its feePercent applied to the deposit amount by a cent: here 1.95% of $30 is $0.585, charged as $0.59.
Fluz’s part here is priced by the card’s BIN configuration at 1.5%, in place of the 3% standard debit card rate: baseFeePercent and paymentRateId name that standard rate.
When an override replaces a fee definition’s rate for your account or application, that part’s source is FEE_OVERRIDE. Its feePercent and feeAmount are what is charged, and baseFeePercent is the definition’s own rate. With a 1.5% override on the same 1.95% definition, the developer part of the $30 deposit is:
Errors
Returns
DepositFeeEstimate! — Estimated fees and total charge for a deposit, with a breakdown of what makes up the fee.