Hosted Checkout Overview
End-to-end hosted checkout — payment links, card, Mada, and Apple Pay.
Hosted Checkout
The Hosted Checkout integration is the recommended way to accept online payments with DigetPay. Your application creates a payment session, redirects the customer to the DigetPay hosted payment page, and verifies the payment result after checkout.
With Hosted Checkout, sensitive payment data never passes through your application, helping reduce PCI DSS scope while providing a secure and optimized payment experience.
New to DigetPay? Complete the Quick Start guide first, then return here for the complete Hosted Checkout workflow.
Recommended integration: Hosted Checkout provides the fastest implementation with the lowest PCI compliance requirements.
Why choose Hosted Checkout?
Card data is securely collected and processed by DigetPay. Your servers never receive PAN, CVV, or Apple Pay tokens.
Create a payment session, redirect the customer, and verify the payment status using only a few API calls.
Support cards, Mada, Apple Pay, and additional payment methods without implementing each payment flow yourself.
Includes 3D Secure authentication, payment status tracking, refunds, and webhook notifications.
Payment Flow
End-to-end payment lifecycle
sequenceDiagram
autonumber
participant Merchant as Your Server
participant API as DigetPay API
participant Customer
participant Checkout as Hosted Checkout
participant Gateway
Merchant->>API: Create Payment Link
API-->>Merchant: redirectUrl
Merchant->>Customer: Redirect customer
Customer->>Checkout: Complete payment
Checkout->>Gateway: Process transaction
Gateway-->>Checkout: APPROVED / DECLINED
Checkout-->>Customer: successUrl / failureUrl
API->>Merchant: Webhook (recommended)
Merchant->>API: Query Transaction Status
opt Refund
Merchant->>API: Process Refund
end
Integration Steps
1. Create a payment session
Your server creates a Hosted Checkout session and receives a redirect URL for the customer.
2. Redirect the customer
Redirect the customer to the DigetPay hosted payment page where they complete the payment securely.
3. Verify the payment
After checkout completes, verify the payment using the Transaction Status API or a webhook notification before fulfilling the order.
Never rely only on the browser redirect to determine payment success.
4. Process refunds (Optional)
Use the Refund API whenever a full or partial refund is required.
Best Practices
- Always verify payments using the Status API or Webhooks.
- Store the gateway transaction ID for future operations such as refunds.
- Include
customerPhonewhen creating payment links to support Apple Pay and other payment methods. - Never fulfill orders directly from the
successUrl. - Use Fin Staging before moving to production.
API Reference
Related Guides
For production deployment, complete the Go-Live Checklist and verify your webhook endpoint before processing live transactions.
Updated 14 days ago
