Integration Planning

Select your integration path

Use Choose Integration Path to compare Hosted Checkout, Embedded Integration, Hosted Redirect API, SoftPOS, SmartPOS, and CMS plugins. That guide is the source of truth for product selection, PCI scope, checkout ownership, and Apple Pay behavior.

Return here after you select a path to plan ownership, credentials, security controls, and staging validation.

---

Recommended First Integration

For most merchants, Hosted Checkout is the recommended starting point. Review the comparison and decision tree in Choose Integration Path before making a final selection.

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

---

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
• merchantOrderId uniqueness 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

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

---