AVAILABLE BY PLAN & APPROVAL

Cash App
PayPal
Crypto
Chime
Apple Pay
Google Pay

Cash App payment integration paths for approved merchants.

PD Cash is an independent payment-orchestration layer, not Cash App or Block. It supports hosted links, signed status webhooks, supported BYOK credentials, and API automation through approved provider or channel-partner routes.

Hosted checkout pilotSigned status webhooksRoute review required
PDPD-LINK-8421
Your payment toYour Store
Amount$50.00 USD
Pay with

Demo methods shown for comparison. Live availability is plan-, account-, region-, and approval-dependent.

Scan to pay

Interactive demo: no payment request is created and no funds move.

1. Review the route

Confirm the business model, region, provider setup, and eligible methods.

2. Pilot hosted checkout

Validate the approved buyer journey before investing in deeper automation.

3. Connect signed status

Verify provider-backed status before fulfillment, access, or reporting.

Independent orchestration, clearly scoped. API access and live routes require separate review. Settlement remains with the connected provider or approved channel partner.

START WITH THE BOUNDARY

Know what the integration does

Use an approved payment route without confusing an independent orchestration layer with Cash App or Block.

What PD Cash provides

Hosted checkout, signed status webhooks, supported BYOK connections, and reviewed API automation through approved provider or channel-partner routes.

What approval controls

Eligibility depends on business model, jurisdiction, documentation, underwriting, provider policy, and current partner availability.

INTEGRATION FLOW

Move from route review to verified status

Pilot the buyer journey first, then connect server-side status and fulfillment controls.

  1. 01
    Review the route

    Share the business model, jurisdiction, current provider setup, and intended checkout flow.

  2. 02
    Pilot approved checkout

    Validate the buyer journey with a hosted link or QR path limited to methods enabled for that account.

  3. 03
    Connect signed status

    Receive a payment-status webhook and verify it using the current integration documentation before acting.

  4. 04
    Confirm, then fulfill

    Confirm final status through the approved provider or orchestration API and retain available reconciliation references.

STATUS DISCIPLINE

Build fulfillment around verified status

Keep the operational rules clear even when the underlying provider or route changes.

Verify every status message

Validate each signed webhook using the current integration documentation before it changes an order or account.

Confirm authoritative status

Treat browser redirects and client-side states as progress signals. Confirm provider-backed status before fulfillment.

Preserve reconciliation context

Keep your internal order reference and the provider transaction reference when available so support can match payment to order.

FAQ

Frequently asked questions

GET STARTED

Map the approved route before you build

Share your business model, current provider, and integration goal. The review maps the eligible hosted-checkout and automation path.

No monthly plan fee · API access and live routes require separate review

Request API route review