You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.
When we're matching a returned ACH file we should filter based on the CompanyIdentification field of the batch.
This value is used for a multi-tenant PayGate install and would help to mark entries as unique.
There could be situations where this changes, but Moov is running PayGate in a mode where this value never changes.
Also, in the long-term Moov views the file config value as a non-changing option as we will override this in file construction based on request information.
PayGate Version:
v0.9.0-dev
What were you trying to do?
When we're matching a returned ACH file we should filter based on the CompanyIdentification field of the batch.
This value is used for a multi-tenant PayGate install and would help to mark entries as unique.
There could be situations where this changes, but Moov is running PayGate in a mode where this value never changes.
Also, in the long-term Moov views the file config value as a non-changing option as we will override this in file construction based on request information.
paygate/pkg/config/odfi.go
Lines 223 to 225 in 54cb3da
The transfers repository would have to change to accept this value. I see this as acceptable as other implementations may ignore this value.
paygate/pkg/transfers/inbound/returns.go
Line 90 in 54cb3da
What did you expect to see?
Returned ACH files should always match to their respective
Transfer
object.The text was updated successfully, but these errors were encountered: