Follow this guide to use the Account Updater API resource to set up a recurring Account Updater harvest for specific payment cards. In response to this request, card brands' Account Updater programs receive card data and ensure their associated information is up-to-date. Account Updater also generates a unique request_id that you can use to check the status of the request. See Submit Account Updater Request in our API Reference for field definitions.

Please note the following:

• You may harvest up to 100 card IDs in one request.
• You may submit multiple Account Updater requests per day.
• It typically takes 3-4 business days to receive a response from the issuers on card updates.

To check the status of an Account Updater request, do any of the following:

• Subscribe to the account_updater_request_created webhook event to be notified when the request creation is complete. Do so via Maast Manager or a Webhooks API request.
• Subscribe to the account_updater_request_completed webhook event to be notified when the request response is received. Do so via Maast Manager or Webhooks API request.
• When you send Submit Account Updater Request, save the request_id value from the response. Use that value in Get Summary of an Account Updater Request to check the status of your request at any time.

Prerequisites

1. See Create a Sandbox Account to sign up and log in to the Maast Manager portal.

2. Follow the steps in Get Your API Credentials to save a sandbox ID and API key.

3. See Authentication to format the credentials and generate your API token. (Alternatively, use the credentials as-is to test this endpoint with our 'Try It!' feature.)

4. Follow the steps in Account Updater in Maast Manager to enroll in the Account Updater service.

Implement

1. Write a POST request to send to the /platform/aus/add endpoint.
2. In the request body, add card numbers and associated expiration dates in a data array.
3. Optionally, you can create a new ID of your choice for each card in this request for your personal reference using the card_id field. This value is distinct from the tokenized card IDs used by Customer Vault and Payment Gateway API.

Once configured, your request will resemble the sample code below:

curl --request POST \
     --url https://api-test.maast.com/platform/aus/add \
     --header 'accept: application/json' \
     --header 'authorization: Basic OjllZGVjMjFhMzFjMHh5ejc4OWUzMGEzNDE2YWJjMTIz' \
     --header 'content-type: application/json' \
     --data '
{
  "data": [
    {
      "card_number": "4111111111111111",
      "exp_date": "0430",
      "card_id": "0001"
    },
    {
      "card_number": "5544666666666664",
      "exp_date": "0125",
      "card_id": "0002"
    }
  ]
}
'

Integrate

Send your request. You will receive a response like this from the Maast server:

{
  "code": 0,
  "message": "Success",
  "data": {
    "request_id": "1537"
  }
}

Check the code field in the request response: 0 confirms that you have successfully sent the request to the Account Updater service. If the value is something other than 0, check Platform API Response Codes in Reference. See Submit Account Updater Request in API Reference for field definitions.

Check and save the request_id value in the data field. You can use this value to check the status of the Account Updater's request at any time.

🚧

Save the Request ID

Be sure to save the request_id value that appears in your request response. You will need it to interact with this request through the API.

Test and Go Live

See our Test and Go Live guide to test your API integration and to start transacting with an active production account.