Get to know PayGlocal's Identifiers
Identifiers are necessary in transaction based systems to identify, track and reconcile any transaction done at any point of time. At PayGlocal we provide a range of fields using which merchants can identify their transactions. Take a look at our two most important Identifiers: GID & MUID.

1 PayGlocal ID - GID
Each PayGlocal transaction can be identified with the help of a PayGlocal ID called GID which will be returned to the merchant as soon as a transaction is initiated via our system. The GID always starts with gl_ and helps merchants identify that it is a PayGlocal created identifier. This is also a service level identifier for the client to use in follow-on API requests (like a refund) and can also be utilised to track transactions, reconcile transactions and much more!
Furthermore, for API based integrations, each PayGlocal API service also responds back with a GID which should be used by merchants to debug and track HTTP requests processed through PayGlocal systems.

2 Merchant Unique ID - MUID
For API based integrations, the MUID is a unique identifier generated by the client that can be used to track transactions. It is up to the client on how to create unique identifiers. PayGlocal suggests using V4 UUIDs, or another random string with enough entropy to avoid collisions. This identifier needs to be unique across services for particular Merchant ID in PayGlocal’s system.