Guiddini PayWhat is an Application?
Learn how applications are used to manage payment integrations.
Each application represents a ready-to-use payment integration for your client’s website, mobile app, or any other digital platform.
Applications act as containers for credentials, configuration, and transaction data that enable merchants to securely process payments via Guiddini Pay.
Key Concepts
1. Linked to a Client
An application is always associated with a specific client. It defines where and how payments will be accepted on their behalf.
2. One License per Application
To process real payments, each application must be assigned a SATIM license. This license allows activation of the payment flow.
3. API Credentials
Each application has its own set of:
- App Key
- Secret Key These credentials are used to authenticate your API requests.
4. Webhook & Callback URLs
You can configure:
- Return URLs: where users are redirected after payment
- Callback URLs: to receive backend notifications about payment status
Use Cases
- A business has multiple websites and wants to separate payment integrations per domain.
- A reseller is managing several clients and creates an application for each one.
- A company has both a mobile app and a website, so two applications are created to isolate configurations.
Note
Each application is independently managed, allowing flexibility in branding, credentials, and environment (sandbox/live).
For managing applications as a partner, see the Partner documentation.