Checkout Page Overview

The customer pays on the hosted page returned by redirectUrl from Create Payment Link. Your server never sees card data.

📘
The checkout page is fully hosted by DigetPay. You only redirect the customer to redirectUrl — no iframe or embedded card fields required.

🚧
Send customerPhone when creating the payment link if you want Apple Pay available on checkout.

❗️
Critical: Your server must always confirm payment via status API or webhook. Redirect to successUrl does not guarantee payment succeeded.

What the customer sees

flowchart LR
  A[Your store] -->|302 redirect| B[DigetPay Checkout]
  B --> C[Select payment method]
  C --> D[Pay]
  D --> E[successUrl / failureUrl]

The hosted checkout page is rendered by DigetPay after you redirect the customer to redirectUrl.

PCI benefit: Card entry, 3-D Secure, and Apple Pay all happen on DigetPay infrastructure — not yours.

Payment methods available

Method	Supported networks	Notes
Card	Visa, Mastercard, Mada, Amex	3-D Secure when required by issuer
Saved card	Prior cards for returning customers	Same email at link creation
Apple Pay	Safari / iOS	Requires `customerPhone` at link creation

Details: Payment Methods

Your integration responsibilities

You build	DigetPay builds
Create payment link	Checkout UI
Redirect to `redirectUrl`	Card / Mada form
Handle return URLs	3-D Secure
Confirm via status/webhook	Apple Pay button

Code: Hosted Checkout Code

Fin staging URLs

Outcome	Recommended URL
Success	`https://fin-admin.digetpay.com/pay/checkout/success`
Failure	`https://fin-admin.digetpay.com/pay/checkout/failure`

On production, use your own HTTPS success and failure URLs.

Next steps

Payment Methods

Card, Mada, saved cards, Apple Pay.

Customer Journey

Step-by-step checkout flow.

Create Payment Link

API reference for link creation.