# Support source: https://developer.mastercard.com/identity-insights-for-accounts/documentation/support/index.md ## FAQ {#faq} ### Identity Insights for Accounts {#identity-insights-for-accounts} Mastercard Identity Insights for Accounts optimizes your account opening workflows with dynamic identity data to accurately assess risk and convert more consumers. It brings together device intelligence, individual attributes (PII) and predictive signals in a single API for simplicity and improved risk management. Businesses can use the scores, accompanying metadata, or reason codes separately or together, depending on the use case you are looking to solve and how each feature performs in your model. We advise using the scores alongside the other top predictive signals accompanying each insight type to finetune your models. #### Device Insights: {#device-insights} **Device Risk Score** Risk score associated with the consumer device, with a higher score indicating a riskier individual. A number between 0 and 1 rounded to three decimal places. #### User Insights: {#user-insights} **Identity Risk Score** Based on five core attributes (name, email, address, phone, and IP) leveraging data sources with 7+ billion identity elements and 5+ billion digital interactions. **IP Score** Assesses the risk of a given IP address in real-time, as well as the network data that surfaces from the previous use of the same IP address. **Predictive Signals** Additional metadata that provides more detail and context to help in enhancing risk decisions. This product follows a progressive tiered price-per-query model. This product is available in North America, Europe, and Asia Pacific. Identity Insights for Accounts customers utilize a single API integration that delivers identity and device details in a single payload. Mastercard teams will assist customers during integration to ensure that they can effectively move to production. Once in production, Mastercard offers 24/7 technical support to ensure that Identity Insights for Accounts effectively meets customer needs. Yes. All Identity Insights for Accounts customers will be required to have a CID and billable ICA. Customers can connect with their Mastercard representative to ensure that Franchise onboarding processes are followed to obtain a CID and ICA to invoice for the service. There are two environments where onboarding will be performed: Member Testing Facility (MTF or Sandbox) environment where all the tests and pre-production validations will happen and the Production environment which will be used for commercial deployments. Mutual Transport Layer Security (MTLS) Message-level encryption is required to consume this API. The client needs to encrypt the request using the Mastercard's public key which can be downloaded from the client project created in MC Developers. The customer needs to request a client certificate for the sandbox environment via the Key Management Portal (KMP), a tool within Mastercard Connect. Subsequently, the customer registers with the Mastercard Developer portal and requests access to Identity Insights for Accounts API and uploads the MTLS Client Certificate. The customer must receive the Certificate and Project approval email notification before proceeding. For **North America**, use the following endpoints: * Sandbox: sandbox.idv.mastercard.com * Production: idv.mastercard.com For **Europe**, use these endpoints: * Sandbox: sandbox.idv.mastercard.eu * Production: idv.mastercard.eu For **South East Asia**, use these endpoints: * Sandbox: sandbox.idv.mastercard.asia * Production: idv.mastercard.asia No. You will need separate certificates. Yes. You may use the same certificate (For example, Sandbox or Production) for other products within the same Identity Insights suite. MTLS certificates are valid for two years while the Mastercard Developers encryption keys are valid for one year. The KMP will provide numerous warnings, starting 120 days before expiration. Mastercard Developers will provide notification to the user starting 30 days before expiration. ### Metrics {#metrics} 100 TPS/customer. If a customer intends to send more than this, they need to engage with the CTS team so the engineering team can autoscale the application. 100 TPS/customer. If more than 100 TPS per customer is received that customer will see errors. The client service does not need to be PCI compliant to access the Identity Insights for Accounts API. PCI and PII data is handled following the PCI security guidelines to ensure the application complies with the PCI DSS standards. Yes. Identity Insights for Accounts will process the request as a new request and will not return any duplicate data error. ### Response Data FAQ {#response-data-faq} Error descriptions can be found in the Mastercard Developers [Code and Formats section](https://developer.mastercard.com/identity-insights-for-accounts/documentation/code-and-formats/index.md). Response descriptions can be found in the Mastercard Developers [Parameters page](https://developer.mastercard.com/identity-insights-for-accounts/documentation/parameters/index.md). Submit a support request ticket to the standard Customer Technical Support channel and be sure to include the Correlation ID, requestRefID as well as the unexpected value or score. The more information provided regarding the issue, the better we're able to expedite an effective response. Multiple IDs are autogenerated in the API response: **Request Ref ID:** This is the unique identifier for the overall request query. ### Pricing and Billing {#pricing-and-billing} Mastercard will bill Customer Fees regularly through the Mastercard Consolidated Billing System (MCBS). MCBS stands for Mastercard Consolidated Billing Services. The MCBS is the system that Mastercard will use to calculate and generate a monthly bill. Since Mastercard uses arrears billing, each bill is for the preceding month's usage. Mastercard will generate the invoice on the second Sunday of every month for the month prior. Billing for the Identity Insights for Accounts service will begin once the customer has moved to production. There may be a fee assessed by the customer delivery team conducting the onboarding and integration, which will be detailed during the contracting phase if applicable. ### Contact and Access {#contact-and-access} Please write to [Mastercard support team](mailto:AII.support@mastercard.com?subject=Mastercard%20Identity%20Insights%20for%20Accounts) for more information about Identity Insights for Accounts. Please write to [Mastercard support team](mailto:AII.support@mastercard.com?subject=Mastercard%20Identity%20Insights%20for%20Accounts) for any technical query. Customers should provide CTS representatives with the Identity Insights for Accounts requestRefID or Correlation ID of the request and any associated error or warning messages that they have received. Customers should also provide the environment being called and URL (EU or non-EU). Refer to [Access MC connect](https://static.developer.mastercard.com/content/identity-insights-for-accounts/ConnectOverview.pdf). Refer to [Access KMP portal](https://static.developer.mastercard.com/content/identity-insights-for-accounts/KMP-User-Guide.pdf). ## Get Help {#get-help} ### Contact us for technical support. {#contact-us-for-technical-support} Get Help