Integration Planning
Choose the DigetPay integration that best fits your business and technical requirements before you start development. Selecting the appropriate integration method early helps reduce implementation effort, simplifies testing, and ensures your project meets security and compliance requirements.
Quick Decision
Compare the available integration options and choose the one that best matches your use case.
| If you need... | Choose | PCI Scope | Complexity |
|---|---|---|---|
| Fastest go-live with the lowest PCI scope | Hosted Checkout | Low | Low |
| A fully customized checkout experience | Embedded Integration | High | High |
| Marketplace split payouts | Hosted Redirect API | Medium | Medium |
| Phone-based Tap-to-Pay | SoftPOS | Low | Medium |
| Fixed retail payment terminals | SmartPOS | Low | Low |
Recommended First Integration
For most merchants, Hosted Checkout is the recommended starting point.
Why choose Hosted Checkout?
- Lowest PCI burden — card data is processed securely by DigetPay.
- Faster implementation with minimal development effort.
- Built-in support for Apple Pay and Mada.
- Same API experience across staging and production environments.
- Reduced compliance requirements.
- Faster time to market.
Team Roles & Responsibilities
| Role | Responsibility |
|---|---|
| Business Owner | KYC verification, go-live approval, compliance sign-off |
| Backend Developer | Payment API integration, webhooks, refund processing |
| Frontend Developer | Checkout launch, success and failure pages |
| DevOps Engineer | API key management, TLS configuration, webhook security |
| QA Engineer | End-to-end testing, staging validation, edge-case testing |
Planning Checklist
Before development begins, confirm the following items.
Integration Selection
- Chosen integration method documented
- Business requirements reviewed
- PCI compliance requirements identified
API Credentials
- Staging API key received
- Production access request planned
- API key storage and rotation strategy defined
Technical Configuration
- Webhook URL prepared
- Success URL confirmed
- Failure URL confirmed
merchantOrderIduniqueness strategy defined- Retry and timeout policies documented
Business Rules
- Refund policy confirmed
- Refund period defined
- Partial refund requirements reviewed
- Chargeback process documented
Security & Compliance
- TLS 1.2 or later enabled
- API keys stored securely
- Webhook validation implemented
- Data retention policy reviewed
Environment Plan
| Phase | Environment | API Base URL | Purpose |
|---|---|---|---|
| Development | Fin Staging | https://fin-api.digetpay.com/v1 | Feature development and initial integration |
| User Acceptance Testing | Fin Staging | https://fin-api.digetpay.com/v1 | Functional and business validation |
| Production | Live | https://api.digetpay.com/v1 | Live payment processing |
Environment Differences
Fin Staging
- Test cards supported
- No real transactions
- Safe for development and testing
Production
- Live customer payments
- Real fund settlement
- Production API credentials required
Next Steps
Once you've selected your integration path:
- Review the documentation for your chosen integration method.
- Obtain your Fin Staging API credentials.
- Configure your development environment.
- Complete end-to-end testing using the Fin Staging environment.
- Validate your integration before requesting production access.
Updated 20 days ago
Did this page help you?