Recued
Menu
← Back to packs

Dispute Defense Operations - Adyen

by recued-core v1 app_pack 5 views

Adyen Disputes v30 defense-reason retrieval and explicitly approval-gated accept, defend, document-supply, and document-delete operations. Generated from Adyen current official commit-pinned OpenAPI 3.1 source. Every mutation is grant-off, requires approval every run, and every admitted POST mutation requires a caller-owned idempotency key of at most 64 characters. Reads are uncached; the seven terminal-setting and payment-method reads whose official schemas can materialize passcodes or acquirer credentials are marked sensitive-read. Auth is connection-owned, pagination follows provider links or documented offsets, and no financial resource is misrepresented as a work-entity Source.

What this pack installs

  • adyen-disputes Ingredient

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Destructive Web APIs adyen-disputes external change
Destructive: general.post_accept_dispute · Always asksDestructive: general.post_defend_dispute · Always asksDestructive: general.post_delete_dispute_defense_document · Always asksRead: general.post_retrieve_applicable_defense_reasons · No approvalDestructive: general.post_supply_defense_document · Always asks

Data it touches

SurfacesWeb APIs

About

Tags

pack:adyenadyendisputeschargebacksdefenseapicomposition