Hi,
Is there any way to attach some useful identity information to the customer while creating customer of an account ? Like, any particular id of our system.
@Binal_Patel, We don’t currently support metadata or passing in a unique id that can be referenced by your app when creating an API Customer.
This is an extremely useful thing to have and I use it all the time with Stripe apps to ensure my application database is in sync with actions done against Stripe’s API. I don’t need to worry about network timeouts, application servers getting killed mid-request, or more importantly having to heuristically guess how to correlate resources after the fact.
If this feature existed now it would’ve made an issue I’m running into right now with creating customers a non-issue. I hope Dwolla will consider implementing this.
(I see that Transfers have a correlationId - something as simple as that added to other resource types like Customer would be good enough even)
Hi @abe, The API does support passing a correlationId when creating a customer. This was recently added an we just updated the docs to reflect the use of correlationId! Keep in mind that we do enforce uniqueness on this field across all the Customers you create. This field cannot be used as a substitute for email as email is a required field for all Customer record types. Hopefully this would solve for your needs relating to correlating users in your system with records created in Dwolla. Please let us know if you have any questions on usage!
1 Like
That’s awesome and will indeed solve my correlation issues! 
Thanks so much for implementing that.
2 Likes