Blockchain.info Receive payments API V2, xpub keys, and gap limit woes.

[Rmcdermott927]

So, I am wondering if anyone has faced this issue before or if anyone can think of a solution or alternative as I am slightly stumped.

I am using the blockchain.info receive payments API V2 for a script of mine.   It uses a BIP32 xpub key to generate receiving addresses.   However, it seems like blockchain.info uses the standard gap limit of 20.   There are a lot of addresses generated for the site that uses the xpub key, so having 20 addresses in a row where there is no payments, is not all that uncommon.   Once that magic number of 20 passes, addresses are still generated but they are no longer monitored for payments. 

Currently, I work my way back and send a small amount of BTC to an earlier address to get it to "see" payments to later generated addresses.

Other than programatically sending dust when there have been x number of receiving addresses without payments, is there any other way to make this more manageable?

[Quickseller]

https://docs.google.com/document/d/1-2l6xOqcbjs9QWEqSh72RD1d8EEdvG_hQuEXw_f_o6w/edit

^^I received this from a zendesk representative when I was attempting to retrieve my xpriv key of my HD blockchain.info wallet. 

[Rmcdermott927]

https://docs.google.com/document/d/1-2l6xOqcbjs9QWEqSh72RD1d8EEdvG_hQuEXw_f_o6w/edit

^^I received this from a zendesk representative when I was attempting to retrieve my xpriv key of my HD blockchain.info wallet. 

Do you know of any programs that allow adjusting of the gap limit so that I can continue using this method?   Id like to not have to recode the payments receiving function in the script.   The v1 API was fine.   I didn't even mind paying the Tx fee.