Transaction Types
Authoritative reference for every transaction action in Cresora Commerce.
Understanding the distinction between an auth reversal, a void, and a refund is essential for correct integration and dispute management.
Quick reference
| Action | When | Settlement | Cardholder impact |
|---|---|---|---|
| Auth reversal | Before capture; same day | None | Hold released immediately |
| Void | Before capture; next day+ | None | Hold released (may take 1–5 days at issuer) |
| Refund | After capture | Credit issued | Credit in 3–7 business days |
| ACH reversal | Same-day ACH only | Reversed | Debit cancelled |
| ACH refund | After ACH settlement | Credit | New credit ACH entry |
Card transactions
Auth reversal vs. void
An auth reversal releases the authorization before capture, on the same day the authorization was created. The hold is released immediately at the issuer.
A void also cancels an uncaptured authorization, but applies when the authorization is not same-day. Void may take 1–5 business days to release at the issuer.
# Auth reversal
POST /v1/payments/{id}/voidRefund vs. credit
A refund reverses a captured payment. It requires the original payment ID and creates a linked credit to the cardholder.
POST /v1/refunds
{
"payment_id": "pay_xxx",
"amount": 5000 # partial refund; omit for full refund
}ACH transactions
ACH adds two additional transaction types because of NACHA's return window rules:
- ACH return — initiated by the receiving bank (R-code). Cresora fires
ach.return.received. Not initiated by you. - ACH reversal — same-day reversal you initiate before the ACH file settles.
- ACH refund — credit entry after the debit settles.
Disputes (chargebacks)
A dispute is initiated by the cardholder through their bank. Cresora fires dispute.created and you have a limited window to submit evidence.
Dispute management via the API is on the Phase 1 roadmap. At MVP 0, disputes are handled through the Partner Portal.