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 Checkout

For 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.

Run the Quick Start →


Choose your integration

Select the integration that matches where payment details are collected and how you want to build your checkout experience.

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 Order

For the complete payment lifecycle, redirects, webhooks, and server-side payment verification, see Hosted Checkout Overview →.

Verify the final payment result

Do 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.

Learn how to verify payments →


Build your first payment

Complete these steps in order using the Fin staging environment.


Core payment APIs

OperationMethod and pathUse it to
Create Payment LinkPOST /payment/checkout/intiateCreate a hosted checkout session and obtain redirectUrl.
Query Transaction StatusGET /payment/checkout/statusConfirm a payment and review its current transaction status.
Process RefundPOST /payment/refundSubmit a full or partial refund for an eligible transaction.

Use the right identifier

Different 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.

See Transaction Identifiers →


Plan your implementation

For Developers

Build and integrate your payment solution using DigetPay APIs, SDKs, and webhooks.

For Business & Operations

Complete merchant onboarding, manage your account, review transactions, and manage settlements.

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 communications

Use 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


Did this page help you?