# Invalid access token while using Dwolla card.js

**URL:** https://discuss.dwolla.com/t/invalid-access-token-while-using-dwolla-card-js/7293
**Category:** General
**Created:** [July 28, 2021, 11:55am UTC](https://discuss.dwolla.com/t/invalid-access-token-while-using-dwolla-card-js/7293 "2021-07-28T11:55:42Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)
#### Post date: [August 19, 2021, 4:53pm UTC](https://discuss.dwolla.com/t/invalid-access-token-while-using-dwolla-card-js/7293/11 "2021-08-19T16:53:54Z")

</div>

Hey @sud – would you be able to check if you are using **idempotency-key** header with your requests to generate a token?

I’m wondering if that’s what’s causing the same card token to be returned in the response, like in this other thread.

> [@Error when adding card funding source using Dwolla-card.js](https://discuss.dwolla.com/t/error-when-adding-card-funding-source-using-dwolla-card-js/7355/9):
>
> Hi @MayuriAdhikar – are you perhaps using an idempotency-key header with your POST request to create a new card-funding-sources-token? If so, the requests are treated as duplicates and you’ll get the original response in the return. Try removing that header, or update the value to a new unique string in order to get a fresh unique Cards token. Let us know if that’s not the case!

---

_[View the full topic](https://discuss.dwolla.com/t/invalid-access-token-while-using-dwolla-card-js/7293)._