# Support source: https://developer.mastercard.com/payment-account-management/documentation/support/index.md ## FAQ {#faq} [About PAM API](https://developer.mastercard.com/payment-account-management/documentation/support/index.md#about-pam-api) [Onboarding \& Testing](https://developer.mastercard.com/payment-account-management/documentation/support/index.md#onboarding--testing) [About the Endpoints](https://developer.mastercard.com/payment-account-management/documentation/support/index.md#about-the-endpoints) ## About PAM API {#about-pam-api} Mastercard issuers can use the API to uniformly perform account lifecycle management events on accounts held across different Mastercard systems. The PAM API can currently be used by Mastercard issuers to submit lifecycle management events that also update associated MDES tokens. It is available for Automatic Billing Updater (ABU)-implemented issuers to submit account updates that the ABU system processes at regular intervals. In addition, the PAM API provides the ability to inquire the PAR vault for getting the PAR value, when a Primary Account Number (PAN) or MDES Token is provided. Issuers and issuer's processors can access the PAM API. In order to use the PAM API, your organization must be a registered Mastercard Issuer, or one of the Issuer's registered processors or service providers. The PAM API is available regardless of whether an issuer has subscribed for any Mastercard service as Automatic Billing Updater (ABU), Mastercard Digital Enablement Service (MDES), or Consumer Controls. Yes, the PAM API is available to MDES and non-MDES Mastercard issuers. Non-MDES Mastercard issuers can call for existing non-digitized card numbers to generate PAR. The PAM API provides the customer access at the CID level. A traditional issuer will only have one CID. An issuer processor might need access to multiple CIDs for the issuers they support. If an issuer uses a sponsor bank, the PAM API currently does not support the capability to access at the account range level. It is part of a future enhancement. The updates to ABU are subject to the ABU fees. Contact your Mastercard representative for futher information. ## Onboarding \& Testing {#onboarding--testing} Yes, a CIS project is required for the MTF and Production access and testing. Implementation should typically take around 4-8 weeks. The time to implement will vary depending on the complexity of your own systems and will include registration, testing connectivity, key exchange, determining testing scope, and testing within the various environments. Yes, you can use the same Client id (Consumer Key) across APIs provided they are all added to the same project. The Client Encryption Keys and Mastercard Encryption Keys will need to be separate for each API. A client ID is associated to a particular project and is specific to Sandbox and Production credentials. Refer to [Environments and Key Usage](https://developer.mastercard.com/payment-account-management/documentation/api-basics/index.md#environments-and-key-usage) table to identify which keys are to be used for specific environments. The sandbox environment will return static responses to correctly formatted requests. Sandbox is a good environment to make sure that you can correctly authenticate with the gateway using OAuth 1.0a and encrypt sensitive data in the requests and decrypt data from the responses. Refer to the [Environments and Key Usage](https://developer.mastercard.com/payment-account-management/documentation/api-basics/index.md#environments-and-key-usage) table below to identify which keys are to be used for specific environments. The keys are created as part of project creation and available for download from the Project Dashboard. The recommended approach is to create a new key but a no service interruption approach is also possible. \[How to renew your project keys\]( New encryption keys can be added in the Project dashboard. After a new key is created, the old key will remain valid until it's expiration date or is revoked. Refer to the [Encryption and Signature Verification Keys guide](https://developer.mastercard.com/platform/documentation/credential-management/encryption-and-sig-ver-key-management/). ## About the Endpoints {#about-the-endpoints} Please refer to the [API overview](https://developer.mastercard.com/payment-account-management/documentation/api-overview/index.md) section. No, the [**addAccount**](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md#add-account) and [**overrideForDeleteAccount**](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md#override-for-delete-account) call will only provide the updates to ABU. Refer to the overview (/documentation/api-overview/) page to understand which interfaces will consume updates from specific APIs. If customers are signed up for ABU and MDES, the update will apply to both systems. If customers are only signed up for ABU, the update will apply only to ABU and not MDES. If customers are only signed up for MDES, the update will apply only to MDES and not ABU. If existing tokens are tied to the closed account and the customer has not opted out of the automatic token deletion process, the associated active and suspended tokens are deleted permanently. If customers are signed up for ABU and MDES, the update will apply to both systems. If customers are only signed up for ABU, the update will apply only to ABU and not MDES. If customers are only signed up for MDES, the update will apply only to MDES and not ABU. The recommendation is to wait at least 60 seconds after the initial account management call to submit the Request Status call for the request ids. The customer can also choose to request the status at the end of the day in batches of up to 100 request ids. Yes, setting the `assingPar` parameter within the [**getPaymentAccountReference**](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md#get-payment-account-reference) call to true will cause a new PAR will be created if one has not been previously generated for the card number. Yes. Per the AN 2747---Enhancement to the Interaction of the Automatic Billing Updater and Mastercard Digital Enablement Service announcement Issuers that manage card account maintenance as a separate process from token maintenance may need to opt out of the automated token deletion service. If issuers need to opt out of their MDES tokens being automatically deleted in the event of ABU submitted closed account notification need to submit a request to [digital.support@mastercard.com](mailto:digital.support@mastercard.com) stating "I wish to opt out from the MDES automated token delete default setting". Please load the accounts through the [**addAccount**](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md#add-account) call with reason code of INITIAL_LOAD. We recommend uploading through a phased approach of 500k cards per day and under 40 peak tps. In order to keep MDES performance as high as possible and provide the most optimized response time, Mastercard reserves the right to throttle during peak periods. ABU consumes the updates at regular intervals and MDES consumes it near real-time. No, two separate calls need to be made to update Expiry date and PAN sequence number. Refer to [**updateAccount**](https://developer.mastercard.com/payment-account-management/documentation/api-reference/index.md#update-account) call for the respective reasons codes and parameters to be used. However, the sequence of the two calls will dictate the content of the request payload. For example: If you plan to update Sequence number first: 1. Add the old expiry date in both `oldCardInfo` and `newCardInfo` 2. Next, update expiry date with old date in `oldCardInfo` and new date in `newCardInfo`. DO NOT send pan sequence number in this request. If you plan to update expiry date first: 1. Update expiry date without any PAN sequence number with old date in `oldCardInfo` and new date in `newCardInfo`. 2. Update Pan Sequence should contain new expiry date in both `oldCardInfo` and `newCardInfo`. ## Get Help {#get-help} For additional support please [Contact Us](https://developer.mastercard.com/support)