Skip to main content

Include Charge ID & Customer ID in Refunds

🔍 Problem Statement

The finance team is unable to efficiently reconcile refunds between NetSuite and Pelcro because the charge_id and associated customer_id are not available in the refunds API response. This prevents accurate tracking of refunds back to their original transactions and customers.

💡 User Story

  1. As a developer, I want the /refunds API response to include the charge_id and customer_id so that I can link each refund to its originating transaction and customer record for reconciliation and reporting.

🎯 Definition of Done (DoD)

  1. The List /refunds Core API response includes both charge_id and customer_id fields.

Status: Available1 comment

Log in to comment and vote

Comments1

  • Mike Gilbert

    •

    Sep 17

    •

    Merged request

    •

    2 votes

    Core API: Refund support

    🔍 Problem Statement

    The Pelcro Core API does not currently support issuing refunds programmatically. Clients who need to process refunds must do so manually through the dashboard or directly via their payment gateway, which slows resolution and prevents automation of refund workflows.


    💡 User Story

    As a developer integrating with Pelcro, I want a Core API endpoint to issue refunds, so that I can automate refund processing without manual dashboard intervention or direct gateway calls.


    🎯 Definition of Done (DoD)

    A feature is done when:

    ✔️ Given a paid invoice or payment, when a developer calls the refund API endpoint with valid parameters, then the refund is processed through the payment gateway, the invoice/payment status is updated in Pelcro, and the transaction is reflected in accounting reports.