December 11, 2024
cancel
Showing results for 
Search instead for 
Did you mean: 
Help

Which response should we save to identify when a clear request was called?

jc_paymentsdev
New Contributor II

When the same original transaction token is used for multiple settle/clear requests, all responses have the same user_transaction_time. However, created_time is different. Which one do you recommend for saving in our system to identify when a clear request was called?

3 ACCEPTED SOLUTIONS

albertot
New Contributor II

Great Question. You can use created_time.

View solution in original post

Arvind
New Contributor III

Hey @jc_paymentsdev ,

I guess you are talking about multiple webhook payloads in case of partial clearings, In such scenarios, you can use the latest webhook's created time.
If you mean only for one webhook call,  then you can use `created_time` as suggested by @albertot .

View solution in original post

cchang
Marqeta Staff
Marqeta Staff

Added clarification in docs, specifically in Transaction field descriptions on the Transactions Core API Reference page.

Thanks, all! 

View solution in original post

8 REPLIES 8

albertot
New Contributor II

Great Question. You can use created_time.

Thanks @albertot!

Arvind
New Contributor III

Hey @jc_paymentsdev ,

I guess you are talking about multiple webhook payloads in case of partial clearings, In such scenarios, you can use the latest webhook's created time.
If you mean only for one webhook call,  then you can use `created_time` as suggested by @albertot .

Hey @Arvind - thanks for the tip! Where did you find this answer in the docs?

Bradburn
Marqeta Staff
Marqeta Staff

Hi @Arvind  and @jc_paymentsdev , we'll add the clarification in docs, thanks! 

cchang
Marqeta Staff
Marqeta Staff

Added clarification in docs, specifically in Transaction field descriptions on the Transactions Core API Reference page.

Thanks, all! 

rosegpsec
New Contributor II

Here is some code I've been working on for this:

fmt.Println("Hello World!")

rosegpsec
New Contributor II

Wow, cool