import { CommonCredentialRequest, CredentialRequestJwtVcJson, CredentialRequestJwtVcJsonLdAndLdpVc, CredentialRequestSdJwtVc, Grant } from './Generic.types';
export type CredentialRequestV1_0_12 = CommonCredentialRequest & (CredentialRequestJwtVcJson | CredentialRequestJwtVcJsonLdAndLdpVc | CredentialRequestSdJwtVc);
export interface CredentialOfferPayloadV1_0_12 {
    /**
     * REQUIRED. The URL of the Credential Issuer, as defined in Section 11.2.1, from which the Wallet is requested to
     * obtain one or more Credentials. The Wallet uses it to obtain the Credential Issuer's Metadata following the steps
     * defined in Section 11.2.2.
     */
    credential_issuer: string;
    /**
     *  REQUIRED. Array of unique strings that each identify one of the keys in the name/value pairs stored in
     *  the credential_configurations_supported Credential Issuer metadata. The Wallet uses these string values
     *  to obtain the respective object that contains information about the Credential being offered as defined
     *  in Section 11.2.3. For example, these string values can be used to obtain scope values to be used in
     *  the Authorization Request.
     */
    credential_configurations: string[];
    /**
     * OPTIONAL. A JSON object indicating to the Wallet the Grant Types the Credential Issuer's AS is prepared
     * to process for this credential offer. Every grant is represented by a key and an object.
     * The key value is the Grant Type identifier, the object MAY contain parameters either determining the way
     * the Wallet MUST use the particular grant and/or parameters the Wallet MUST send with the respective request(s).
     * If grants is not present or empty, the Wallet MUST determine the Grant Types the Credential Issuer's AS supports
     * using the respective metadata. When multiple grants are present, it's at the Wallet's discretion which one to use.
     */
    grants?: Grant;
    /**
     * Some implementations might include a client_id in the offer. For instance EBSI in a same-device flow. (Cross-device tucks it in the state JWT)
     */
    client_id?: string;
}
//# sourceMappingURL=v1_0_12.types.d.ts.map