AllSecure recommends its merchants to log authentication.entityID values in their system for all successful payments.
In a typical payment request, merchant provides with the parameter authentication.entityID to receive transaction reference checkoutID. Sample request may be found below:
curl https://test.oppwa.com/v1/checkouts \ -d "authentication.userId=8a8294184f45ce7e014f4b1d16cc12df" \ -d "authentication.password=j3zCJ2ENaD" \ -d "authentication.entityId=8a8294184f45ce7e014f4b1d16bd12db" \ -d "paymentType=DB" \ -d "amount=100.99" \ -d "currency=RSD"There are many different scenarious which makes remembering this authentication.entityID usefull. Imagine the merchatn that may have been allocated with multiple entityID), one for initiall transaction and card registration, and the other for one-click payments with registered card.
Similarly a merchatn may be using one channel for processing transactions with one bank and second channel for processing with other bank. In such scenario, the merchant should remember entityID that was used for specific transaction, so that any future transactions such as REVERSAL or CAPTURE transactions could be sent to the same entityId as the original transaction
So named "back-office" transactions (REVERSAL, CAPTURE, REFUND) all require for the same entityID to be used. This is needed to ensure that funds are applied to the correct merchant accounts and bank account. If you send REVERSAL to a different entityID then you will receive the following error: 700.400.700 - Initial and referencing channel-ids do not match .