DigetPay Portal
Build, test, and launch DigetPay payments with Hosted Checkout, embedded integrations, webhooks, SDKs, and production guidance.
Build, test, and launch a DigetPay payment integration by choosing the product and integration path that match your checkout requirements and PCI scope.
What is DigetPay?
DigetPay provides a set of payment and commerce solutions for accepting, processing, and managing payments. Start by identifying the product you are integrating before choosing your implementation path.
flowchart TB
DP[DigetPay Platform]
DP --> PG[Payment Gateway]
DP --> CP[Card-Present Payments]
DP --> EC[Commerce Plugins]
DP --> DEV[Developer Portal]
PG --> HC[Hosted Checkout]
PG --> S2S[Embedded / S2S]
PG --> AP[Apple Pay]
PG --> MOBILE[Mobile SDKs]
CP --> SP[SoftPOS]
CP --> SMP[SmartPOS]
EC --> WC[WooCommerce]
EC --> OC[OpenCart]
DEV --> MARKET[Marketplace Services]
style DP fill:#ff8a00,color:#ffffff,stroke:#ff8a00
Payment Gateway
Accept online payments using Hosted Checkout, Embedded/S2S integrations, Apple Pay, APIs, and supported mobile SDKs.
Card-Present Payments
Accept payments in person using SoftPOS and SmartPOS solutions.
Commerce Plugins
Connect your e-commerce platform using supported integrations such as WooCommerce and OpenCart.
Developer Portal
Build and manage marketplace services and applications using the DigetPay Developer Portal.
Looking for the Payment Gateway?If you are integrating DigetPay to accept online or in-person payments, start with the Payment Gateway paths below. The Developer Portal is a separate product for marketplace services and applications.
Start with Hosted CheckoutFor most online payment integrations, create a payment link on your server and redirect the customer to DigetPay's hosted checkout page. Your systems do not collect card numbers, CVV, or Apple Pay tokens.
Choose your integration
Select the integration that matches where payment details are collected and how you want to build your checkout experience.
Create a checkout session and redirect the customer to a DigetPay-hosted payment page. Choose this path for the lowest PCI scope.
Build payment collection into your own checkout. Use this path only when your compliance and security requirements support server-to-server card handling.
Enable Apple Pay with hosted checkout or select an embedded implementation for your supported platform.
Review mobile SDKs, SoftPOS and SmartPOS options, or connect an e-commerce platform with a supported plugin.
Not sure which integration is right for you? Compare the available integration paths →
Recommended path: Hosted Checkout
Hosted Checkout is the recommended starting point for most online integrations. Your server creates a checkout session, your customer completes payment on a DigetPay-hosted page, and your server verifies the final payment result before fulfillment.
Your Server
↓
Create Checkout Session
↓
Receive redirectUrl
↓
Redirect Customer to DigetPay
↓
Customer Completes Payment
↓
Verify Final Payment Status
↓
Fulfill the OrderFor the complete payment lifecycle, redirects, webhooks, and server-side payment verification, see Hosted Checkout Overview →.
Verify the final payment resultDo not rely on a customer redirect alone to determine whether a payment was successful. Confirm the final transaction status using a webhook or the transaction status API before fulfilling an order.
Build your first payment
Complete these steps in order using the Fin staging environment.
Generate and securely store the credentials required for your integration.
Configure your application to use the Fin staging environment and its test credentials.
Create a hosted checkout session and receive the checkout URL.
Redirect the customer to the returned redirectUrl.
Verify the final transaction result using webhooks or the transaction status API before fulfilling the order.
Test your integration and complete the Go-Live Checklist before moving to production.
Core payment APIs
| Operation | Method and path | Use it to |
|---|---|---|
| Create Payment Link | POST /payment/checkout/intiate | Create a hosted checkout session and obtain redirectUrl. |
| Query Transaction Status | GET /payment/checkout/status | Confirm a payment and review its current transaction status. |
| Process Refund | POST /payment/refund | Submit a full or partial refund for an eligible transaction. |
Use the right identifierDifferent payment operations use different identifiers. Store the checkout session ID returned when creating the payment, but use the required transaction identifier for payment verification, refunds, and other supported operations.
Plan your implementation
Security and compliance
- Keep API keys and other secrets on your server and load them from a secrets manager or protected environment variable.
- Never commit API keys or secrets to source control.
- Never expose server-side credentials in browser or mobile applications.
- Hosted Checkout can reduce the amount of payment data handled directly by your application. Review your PCI DSS responsibilities with your compliance team.
- Test your complete integration in Fin staging before requesting production credentials.
Regulatory and compliance communicationsUse only regulatory, licensing, and authorization statements that have been approved by DigetPay's legal or compliance team. Do not make claims about regulatory approval or authorization in customer-facing materials unless those claims have been explicitly approved.
Continue building
Review the complete Hosted Checkout payment flow and payment verification process.
Compare hosted, embedded, Apple Pay, SDK, and in-store payment options.
Browse available endpoints, request schemas, and response details.
Find answers to common integration questions.
Updated about 1 month ago

