ADadyen
General

Schedule running the Account Updater

Changed on

When making the API call, you can submit either the credit card information, or the recurring detail reference and the shopper reference:

  • If the card information is provided, all the sub-fields for card are mandatory.
  • If the recurring detail reference is provided, the fields for shopperReference and selectedRecurringDetailReference are mandatory.
post/scheduleAccountUpdater

Request

  • Base URL
    https://pal-test.adyen.com/pal/servlet/Recurring/v67
  • URL
    https://pal-test.adyen.com/pal/servlet/Recurring/v67/scheduleAccountUpdater
  • Auth
    • HTTP basic
    • or API key in header X-API-Key

Request body

additionalDataobject

This field contains additional data, which may be required for a particular request.

merchantAccountstring required

Account of the merchant.

referencestring required

A reference that merchants can apply for the call.

selectedRecurringDetailReferencestring

The selected detail recurring reference.

Optional if card is provided.

shopperReferencestring

The reference of the shopper that owns the recurring contract.

Optional if card is provided.

Response

OK - the request has succeeded.

pspReferencestring required

Adyen's 16-character unique reference associated with the transaction. This value is globally unique; quote it when communicating with us about this request.

resultstring required

The result of scheduling an Account Updater. If scheduling was successful, this field returns Success; otherwise it contains the error message.

Changes

  • v67ea137aa7acdeRevision changes
    • info

      the request property / became optional

    • info

      the request property / became optional

  • v6728b2ade28b68Revision changes
    • breaking

      the request's body type changed from no type to object

    • breaking

      the request property type changed from no type to object

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status