ElectroNeek

Integrations · payment processing

ElectroNeek + Pinch Payments

Australian payment processing platform for direct debits, credit cards, and recurring payments. Create payers, process payments, manage subscriptions, and handle payment sources with comprehensive webhook support. Ships with 8 ready actions and 14 event triggers — usable in agent workflows without code.

What agents can do with Pinch Payments

Actions · 8

  • Create or Update Payer

    Create a new payer or update an existing one

  • Create Realtime Payment

    Create a real-time payment against a credit card or bank account

  • Add Source to Payer

    Add a payment source (bank account or credit card) to an existing payer

  • Create or Update Scheduled Payment

    Create a new scheduled payment or update an existing one

  • Add Subscription

    Create a subscription between a payer and a plan

  • Find Event

    Find an event using the Event ID

  • Find Payer

    Find a payer by their Payer ID

  • Find Subscription

    Find a subscription using the Subscription ID

Triggers · 14

  • Bank Results Event

    Triggers when a bank account transaction returns (may result in dishonour status)

  • Payer Created

    Triggers when a new payer record is created

  • Payer Updated

    Triggers when a payer record is updated

  • Realtime Payment

    Triggers when a realtime payment is executed

  • Payment Created

    Triggers when a payment is created (via Save Payment endpoint or Subscription)

  • Subscription Created

    Triggers when a subscription is created for a payer

  • Subscription Cancelled

    Triggers when a subscription is cancelled

  • Subscription Complete

    Triggers when a subscription is run to completion

  • Refund Created

    Triggers when a refund is created

  • Refund Updated

    Triggers when a refund is updated (e.g., status change)

  • Scheduled Process

    Triggers when scheduled payments are processed (daily on business days)

  • Transfer Created

    Triggers when a transfer is created to settle funds to a merchant

  • Dispute Created

    Triggers when a dispute is created

  • Dispute Updated

    Triggers when a dispute is updated

How Pinch Payments fits an agent workflow

01

Trigger or read

An agent starts from a Pinch Payments event or reads Pinch Payments data as part of a broader workflow.

02

Decide with AI

The agent classifies, matches, or drafts — with your guardrails and human approvals where it matters.

03

Act across systems

Results post back to Pinch Payments and to the rest of your stack — ERP, spreadsheets, email — in one run.

Ship a Pinch Payments workflow this month — built and run by us.