I'm creating a profile and payment profile id when creating a transaction and have used both the create profile from transaction api call and the createprofile=true on a create transaction API call. Both methods don't actually associate that transaction with the payment profile or even the profile. I would have expected it would. Regretfully the system we are integrating with requires a transaction be associated with a payment profile. Sigh. So, is my only recourse here creating a profile and payment profile first and then using them in a transaction? I read that the creation of a payment profile is async which could cause issues. Is it possible to associate a transaction with a payment profile using the create profile from transaction api call?
08-21-2020 08:16 AM
Yes, create the profiles first and then the transaction.
In the other cases, the transaction comes before the profile is generated, so it is not associated with it.
10-20-2020 03:11 PM