FAQs

Find quick answers to the most common questions about integrating with DigetPay, including account setup, API authentication, payment processing, webhooks, and production readiness. This section helps merchants and developers resolve common issues without needing direct support.

Frequently Asked Questions (FAQ)

How do I get my API credentials?

Complete the Business Onboarding process, then follow the Sandbox Setup guide. Your staging API credentials are available in the Merchant Dashboard under API Credentials.

What's the difference between Staging and Production?

Staging

• API Base URL: https://fin-api.digetpay.com/v1

• Dashboard: https://fin-admin.digetpay.com

Production

• API Base URL: https://api.digetpay.com/v1

• Dashboard: https://admin.digetpay.com

For more details, see the Environments Overview.

Which integration option should I choose?

Choose the integration method that best fits your business:

Hosted Checkout – Redirect customers to a secure DigetPay payment page (recommended for the fastest integration).
Embedded (S2S) – Build a fully customized checkout experience using server-to-server APIs.
CMS Plugins – Integrate quickly using WooCommerce or OpenCart plugins.

See Choose Integration Path for a complete comparison.

Which authentication method should I use?

Payment APIs require the x-api-key header.

Merchant Portal APIs (such as Webhooks, SDK Tokens, and Credential Management) require a Bearer Token generated from the Merchant Dashboard.

Why am I receiving a 401 Unauthorized response?

Common causes include:

Missing or invalid x-api-key.
Using a Production key against the Staging environment (or vice versa).
Using a Bearer Token on payment endpoints.
Using an API key on Merchant Portal endpoints.

Why is customerPhone required when creating a Payment Link?

The customerPhone field is required for customer identification and to support certain payment methods. Requests without this field return 400 Bad Request.

Why is the checkout endpoint spelled 'intiate'?

The current production endpoint is:

POST /payment/checkout/intiate

Although the spelling appears unusual, this is the official DigetPay endpoint and should be used exactly as documented.

Can I rely on the Success Redirect URL to confirm payment?

No.

Customers may close their browser before the redirect occurs.

Always confirm successful payments using either:

Webhook notifications.
Transaction Status API.

How do I test payments in Staging?

Create a payment using the Create Payment Link API.
Open the returned redirectUrl.
Complete the payment using the test cards.
Verify the transaction through Webhooks or the Status API.

Where can I find all API endpoints?

All DigetPay APIs are available in the API Reference, including:

Hosted Checkout
Embedded (S2S)
Transactions
Webhooks
Account & SDK APIs

Where can I manage API keys and Webhooks?

You can manage your integration directly from the Merchant Dashboard, including:

API Credentials
Webhook Configuration
Merchant Settings

What should I complete before going live?

Before switching to Production, make sure you have completed:

Production API credentials.
Live callback URLs.
Webhook configuration.
End-to-end payment testing.
Refund testing.
Support contact verification.

Where can I find the Developer Documentation?

Our documentation includes:

Developer Guides — Step-by-step integration guides.
API Reference — Complete endpoint documentation with request and response examples.

How can I contact DigetPay Support?

For API credentials, production access, or integration assistance, contact us at:

[email protected]