# Simple, efficient and "never-breaking" solution for handling pledges?

**URL:** <https://www.patreondevelopers.com/t/simple-efficient-and-never-breaking-solution-for-handling-pledges/1341>\
**Category:** Friendly Help\
**Created:** [December 15, 2018, 12:28pm UTC](https://www.patreondevelopers.com/t/simple-efficient-and-never-breaking-solution-for-handling-pledges/1341 "2018-12-15T12:28:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rxsto](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/rxsto/32/695_2.png) [@Rxsto](https://www.patreondevelopers.com/u/Rxsto)\
**Post date:** [December 15, 2018, 12:28pm UTC](https://www.patreondevelopers.com/t/simple-efficient-and-never-breaking-solution-for-handling-pledges/1341/1 "2018-12-15T12:28:11Z")

</div>

Hey guys,

I’m maintaining a relatively big Discord-bot, that offers you the opportunity to get premium features via donating on Patreon.

I’m currently handling that via multiple OAuth2 requests and storing the access- and refresh-tokens in a database. The data is getting refreshed every hour in order to have the correct information about the pledge-status. Now it could happen that the application that handles the data gets disconnected or restarted due to connection issues or server restarts etc which often ends in invalid tokens. Then I need to delete all data and the patrons need to relink their accounts - and that is quite annoying.

Now I’m asking you guys for helping me finding a simple way to handle that!

Thank you so much, Rxsto
