Choose Integration Path

Choose the integration that matches your PCI scope, checkout UX, and product type. You can start with hosted checkout and add embedded integration or in-store products later.

---

Decision tree

flowchart TD
  start[What are you building?]
  start --> online[Online payments]
  start --> instore[In-store / terminal]
  online --> pci{Can you handle card data PCI?}
  pci -->|No or prefer low scope| hosted[Hosted Checkout]
  pci -->|Yes SAQ D approved| s2s[Embedded Integration]
  online --> market[Marketplace split payouts]
  market --> redirect[Hosted Redirect API]
  instore --> soft[SoftPOS mobile app]
  instore --> smart[SmartPOS terminal]
  hosted --> phpH[PHP guide: redirect to DigetPay checkout]
  s2s --> phpS[PHP guide: build your own checkout]

---

Comparison

---

WooCommerce, OpenCart & CMS plugins

Flow: Install the DigetPay plugin → configure API key → register webhook → customers pay on DigetPay hosted checkout.

Supported Platforms

• WooCommerce — Install, configure, test, and go live with step-by-step screenshots and troubleshooting guides.
• OpenCart 3 — Extension installation, configuration, and comprehensive troubleshooting documentation.
• OpenCart 4 — Full hosted checkout integration for OpenCart 4.x with modern architecture support.
• All plugins — Compare platforms and access build-your-own plugin guide for custom implementations.

---

Hosted Checkout (recommended)

Flow: Your server creates a payment link → customer pays on DigetPay checkout → you confirm via status API or webhook.

Key Features

• Lowest PCI scope — Card data never touches your servers
• Automatic Apple Pay — DigetPay checkout displays Apple Pay automatically when you send customerPhone during link creation
• Flexible confirmation — Use status API polling or webhook notifications to track payment completion
• Mobile optimized — Responsive design works seamlessly across all devices
• Multiple payment methods — Supports cards, digital wallets, and regional payment options

Implementation Overview

Your server initiates the payment by creating a link with customer details and order information. The customer is redirected to DigetPay's secure checkout page where they enter payment details. Upon completion, DigetPay notifies your system via webhook or you can query the status API to confirm the transaction and update your order.

Language Support

Available integration examples and guides for:

• PHP
• Node.js
• Python
• Java

---

Embedded Integration

Flow: Customer enters card on your website → your server calls DigetPay embedded APIs with a signed hash.

Key Features

• Full customization — Complete control over checkout UI and user experience
• Higher PCI scope — You handle card data (SAQ D compliance required)
• Custom branding — Seamless integration with your site design
• Advanced features — Support for recurring payments, tokenization, and complex workflows
• Apple Pay support — Implement Apple Pay directly on your checkout page

Architecture Overview

Embedded integration requires your server to generate cryptographically signed requests to DigetPay APIs. The customer enters card details on your checkout form, which your frontend securely transmits to your backend. Your backend then calls DigetPay's embedded APIs with proper authentication and validation.

PCI Compliance Requirements

• Must be SAQ D approved
• Implement proper data encryption and transmission security
• Regular security audits and vulnerability assessments
• Secure key management for API credentials

Language Support

Available integration examples and guides for:

• PHP
• Node.js
• Python
• Java

---

In-store: SoftPOS & SmartPOS

SoftPOS (Mobile)

• Device: Android phone or tablet
• Use case: Flexible tap-to-pay payments on mobile devices
• Setup: Uses SDK tokens from merchant dashboard
• Best for: Pop-up shops, delivery services, field sales

SmartPOS (Terminal)

• Device: Dedicated POS terminal
• Use case: Fixed point-of-sale installations
• Setup: Uses SDK tokens from merchant dashboard
• Best for: Retail stores, restaurants, fixed locations

Both solutions use SDK tokens generated from your merchant dashboard for authentication and secure communication.

---

After you choose

Step 1: Business Onboarding

Complete the business onboarding process if not already approved. This includes identity verification, business documentation, and compliance checks.

Step 2: Technical Onboarding

Set up your staging environment with test credentials. Configure API keys, webhooks, and test payment methods for development.

Step 3: Integration

Implement your chosen integration path using available code examples and guides. Test all payment flows and edge cases in staging.

Step 4: Validation & Testing

Validate your implementation using the testing guide with provided test card numbers and scenarios. Verify webhook delivery, error handling, and edge cases.

Step 5: Go-Live

Review the go-live checklist to ensure all requirements are met. Perform final security review and deploy to production with monitoring in place.