Connect Adyen and Vouchery.io

Both apps 27Adyen 12Vouchery.io 15

• Trigger
  New payment authorisation

  Webhook AUTHORISATION: result of authorisation request.

• Trigger
  New refund

  Webhook REFUND: result of refund request.

• Action
  Add payment

  Starts a payment (authorisation) in Adyen Checkout for the given amount, payment method and merchant account, and returns the payment's PSP reference and result code.

• Action
  Add payment link

  Creates an Adyen Pay by Link payment link that a shopper can open to pay the given amount.

• Action
  Cancel payment

  Cancels an authorised payment that has not been captured yet, releasing the funds back to the shopper. The final outcome arrives later in Adyen's CANCELLATION webhook.

• Action
  Capture payment

  Captures an authorised payment (full or partial amount). Adyen processes the capture asynchronously: the response always has status "received" and the final outcome arrives later in a CAPTURE webhook.

• Action
  Delete stored payment method

  Deletes (disables) a shopper's stored payment details token in Adyen.

• Action
  Get payment link

  Retrieves the details of a payment link, including its amount, status (active, completed, expired or paymentPending), url and expiry.

• Action
  List payment methods

  Retrieves the payment methods available for a transaction, based on details such as amount, country and currency, plus the shopper's stored payment methods when a shopper reference is given.

• Action
  List stored payment methods

  Lists the tokens for payment details stored for a shopper, with a summary of each stored card or account.

• Action
  Refund payment

  Refunds a captured Adyen payment, fully or partially. Adyen acknowledges the request immediately; the final outcome arrives later in a REFUND notification.

• Action
  Update payment link

  Updates the status of an Adyen payment link. Adyen only allows setting the status to expired, which forces the link to expire so shoppers can no longer pay with it.

• Trigger
  New Voucher

  Triggers when a new voucher is created in the selected Vouchery campaign.

• Action
  Add campaign

  Creates a promo campaign in Vouchery — either a main campaign or a sub campaign under an existing main campaign — and returns the new campaign.

• Action
  Assign vouchers to customer

  Assigns one or more voucher codes to a customer and returns the customer's updated record.

• Action
  Cancel redemption

  Cancels a redemption by its redemption ID, marking it as cancelled.

• Action
  Confirm redemption

  Confirms a redemption so it counts toward the campaign's budget and total redemptions. Returns the confirmed redemption.

• Action
  Create Customer

  Creates a customer in Vouchery with their unique identifier, contact details, segment categories and metadata.

• Action
  Create Redemption

  Redeems a voucher code for a purchase, recording the order total or line items and returning the redemption with the discount and rewards granted.

• Action
  Delete customer

  Deletes a customer from your Vouchery project by their identifier.

• Action
  Find Voucher

  Finds a voucher by its code and returns its status, campaign, customer and redemption details.

• Action
  Get campaign

  Returns a single Vouchery campaign by its ID, including its rules, rewards, budget and voucher statistics.

• Action
  Get customer

  Returns a single customer by their identifier, including profile details, segments, loyalty points and voucher/redemption statistics.

• Action
  Get redemption

  Returns a single redemption by its ID, including its voucher, campaign, customer, confirmation status and granted rewards.

• Action
  List campaigns

  Returns the campaigns in your Vouchery project, optionally filtered by name, team, status, template or loyalty program.

• Action
  List customers

  Returns the customers in your Vouchery project, optionally filtered by identifier or email.

• Action
  Update customer

  Updates an existing customer's name, email, referral code, birthdate, segments or metadata. Only the values you provide are changed.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.