Schedule running the Account Updater

post/scheduleAccountUpdater
Deprecated in version 68

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.
Endpoint destination URL
https://pal-test.adyen.com/pal/servlet/Recurring/v68/scheduleAccountUpdater
additionalDataobject

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

cardobject

Credit card data.

Optional if shopperReference and selectedRecurringDetailReference are provided.

merchantAccountstringRequired

Account of the merchant.

referencestringRequired

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.

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

  • 400 - Bad Request

    A problem reading or understanding the request.

  • 401 - Unauthorized

    Authentication required.

  • 403 - Forbidden

    Insufficient permissions to process the request.

  • 422 - Unprocessable Entity

    A request validation error.

  • 500 - Internal Server Error

    The server could not process the request.