Developer Tools

Give engineers one clean integration surface

EFundFlow keeps developer configuration close to the payment objects that use it: API credentials, site-level payment webhooks, refund webhooks, authentication guidance, and documentation for payment operations.

Explore docs View API reference
EFundFlow API credentials dashboard
API
Credentials and auth
Webhooks
Payment and refund callbacks
SDK
Integration resources
Credentials

Manage API access from the dashboard

Developers can use dashboard-managed credentials while operations teams retain visibility into which merchant and site configuration is being used.

  • Merchant-level API credential management
  • Authentication guidance for server integrations
  • Clear separation between dashboard users and API access
Webhooks

Configure callbacks by site

Set payment and refund webhook URLs at the site level so each domain and payment setup can receive events through the correct endpoint.

  • Payment webhook URL per site
  • Refund webhook URL per site
  • URL validation and ownership checks before saving
Integration

Support multiple checkout models

Choose the integration approach that fits each site, from direct server API to hosted cashier and JSSDK iframe flows.

  • Direct API for full server-side control
  • Cashier flow for faster hosted checkout launch
  • JSSDK iframe for embedded checkout experiences

A cleaner integration workflow

The goal is to let engineering integrate once while operations can still manage site settings, processor credentials, and callbacks without code releases.

1

Create credentials

Generate and manage API credentials through the merchant dashboard.

2

Configure site webhooks

Attach payment and refund callback URLs to the site that owns the payment flow.

3

Build against docs

Use API documentation, authentication guidance, and examples to complete the integration.

4

Operate from dashboard

Monitor transactions, refunds, disputes, routing, and reports after launch.

Developer console
POST /v1/payments
{
site_id: "site_us",
webhook: "refund.created",
processor: "routing_policy"
}
Step 1
Create credentials
Step 2
Configure site webhooks
Step 3
Build against docs

Built for payment engineering

status: ready
webhook: verified
integration: one surface
01

Engineers can keep one API integration while business teams expand processors and sites through dashboard configuration.

02

Site-level webhook settings reduce confusion when a merchant operates multiple storefronts or domains.

03

Operations teams can inspect configuration without asking engineers to search code or processor portals.

04

Authentication, webhook, and payment resources stay connected to the product workflow.