> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe - Payment Intent Configuration

| Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? |
| - | - | - | - | - | - | - | - | - |
| Stripe Payment Provider (Payment Intent API ) | US and Canadian Cards | [Supported Currencies List](https://stripe.com/docs/currencies#presentment-currencies) | \*\*Credit/Debit Cards -\*\**Yes* **SEPA DD**- *No* **Tokenized Credit Card**- *Yes* **Hosted Pages** - *No* **Alternative Payments** - *No* **Digital Wallets** - *No* | **Tokenized Credit Card** - *Yes* **Detokenize PAN** - *No* **Detokenize BIN**- *No* **Partial Auth** - *No* **Forced Deposit** - *No* | Yes, via webhook. | No | Payment Intent | Yes |

## Required Merchant Information

\[<img src="https://mintcdn.com/amdocs-slm/ifa3y22T11JlqvtT/portal/vindiciaSubscribeAndNewRetain/subscribePaymentProviderIntegration/images/download_button.png?fit=max&auto=format&n=ifa3y22T11JlqvtT&q=85&s=74864737190e56d2ac71f7232f0900ac" alt="" width="150" height="38" data-path="portal/vindiciaSubscribeAndNewRetain/subscribePaymentProviderIntegration/images/download_button.png" />

]\(../images/StripeIntent.xlsx)

| Name | Expected Value | Value | Description |
| - | - | - | - |
| StripeIntent:account | Acct\_66891233 | | Account Id is generated by merchant when they connect (Stripe Connect) with Vindicia |
| StripeIntent:SECRET\_KEY | st\_522IB653CXtAABehHYh12GwOFtEog4IqwR74zfspfckTwW0N380S45 | | This is a string value of a secret key needed only for resellers. When a reseller is used, the reseller is already connected to the merchant with the generated key and therefore we need an alternate key. This same key will then be used for all merchants connected to the reseller. **Note:** For a reseller scenario, **StripeIntent:KEY\_TYPE** NVP also needs to be defined as **BASIC**. See Name Value Pairs section below for more details. |
| VIN\_SCA\_provider | 2001 | | This is the value of the SCA provider. Here we just need the name of SCA provider from Merchant, based on that we will mark its entry in our DB and generate this ID. We don’t need to ask this ID to merchant, but need to ask SCA provider name. |
| Does provider need to whitelist IPs | No | | |
| Does a merchant need to grant access to Vindicia | Yes | | |
| Chargeback feed | Yes | | Via webhook events (`charge.dispute.create` and `charge.dispute.update`) |
| Account Updater | No | | |

## Desired Merchant Configuration

| Name | Value | Comments |
| - | - | - |
| N/A |   |   |

* **[Stripe Intent Merchant Setup Instructions](../topics/stripeIntentConfiguration_r#)**

* **[Stripe Intent Detailed Information on Integration](../topics/stripeIntentConfiguration_r#)**

**Parent topic:**[Payment Provider Specific Configuration](../topics/PaymentProvidersSpecificConfiguration)

## Stripe Intent Merchant Setup Instructions

The following Instructions are written for Vindicia CTS and services delivery staff.

To configure a merchant to use Stripe Intent payment processor:

### Merchant Payment Providers

1. In Subscribe Portal 1.0, using you’re admin account, go to **Admin** > **Merchant Configurations**.
2. Select the relevant **Merchant** from the drop-down list.
3. Click **Edit Merchant Configurations**.
4. Enter the **Jira Ticket #** for configuring your merchant payment setup.
5. Add Stripe Intent to **Merchant Payment Providers**:

   | Payment Provider Name | Account Number | PP Type | Active |
   | - | - | - | - |
   | StripeIntent (1079) | \<blank> | BRD(1) | 1 |

   1. Select **StripeIntent (1079)** as the payment provider and click **ADD**.
   2. Leave **Account Number** blank.
   3. Set **PP Type** as **BRD**.
   4. Set **Active** to **1**.

### Routing Rule

1. Add a **Routing Rule** for Stripe Intent.

   | Ordinal | Payment Provider | Value | Rule Method | Active |
   | - | - | - | - | - |
   | 1 | StripeIntent (1079) |   | default\_method(1) | 1 |

   1. Select **StripeIntent (1079)** as the payment provider and click **ADD**.
   2. Add an **Ordinal** value of **1**.
   3. Leave **Value** blank.
   4. Add a **Rule Method** value of **default\_method(1)**.
   5. Set **Active** to **1**.

      **Note:** If the test payment provider is configured, set its **Active** value to **0**.

**Note:** If a merchant account is set up with several payment providers, the payment provider with highest **Ordinal** value has priority. If routing will be shared amongst payment providers, see [Configuration Method - Payment Providers Routing Rules](routingRulesAbout) for examples of possible configurations.

### Name/Value Pairs

The below api\_key value is for Vindicia internal testing and should not be shared with merchants.

| ID | Name | Value |
| - | - | - |
| 100012273 | StripeIntent:account | Acct\_7665656566 |
| | StripeIntent:SECRET\_KEY | key stringA reseller secret key needed when a merchant is already enabled with a billing platform. Vindicia connects through the reseller for all the relevant merchants. **Note:** When using the reseller secret key, the key type must also be configured to basic auth- see below. |
| | StripeIntent:KEY\_TYPE | BASIC This NVP is needed when using a reseller key rather than than a merchant key that is hard-coded. The reseller key will use basic auth rather than bearer auth and so needs to be configured. |

### Chargeback Webhook Events

**Note:** The following steps are performed by the merchant in their payment provider portal.

1. In the Stripe Connect Dashboard, click on **Developers** in the upper right corner of the page.

   **Note:** Toggle the **Test mode** on for the staging environment or leave cleared for production.

2. In the Developers options, click **Webhooks**.

3. To add an event, click **Add endpoint**.
   * For production, enter `https://secure.vindicia.com/billinginterface/stripe/StripeConnect.html`.
   * For staging, enter `https://secure.staging.us-west.vindicia.com/billinginterface/stripe/StripeConnect.html`.

4. Once the endpoint is added, click the URL and add the following events:
   * `charge.dispute.created`
   * `charge.dispute.updated`

### Merchant Materials for Account Configuration

For Merchant documentation, provide merchants with the following links to the How To guide:

* [Stripe Account Presentation](https://docs.vindicia.com/bundle/howTo/page/topics/stripeAccountConfiguration.html)
* [Stripe Chargeback Configuration](https://docs.vindicia.com/bundle/howTo/page/topics/chargebackConfigurationStripe.html)

**Parent topic:**[Stripe - Payment Intent Configuration](../topics/stripeIntentConfiguration_r#)

## Stripe Intent Detailed Information on Integration

Vindicia supports the following Payment Operations for Stripe Intent:

| Payment Operation | Yes/No | Notes |
| - | - | - |
| **Standard Implementation Features** | | |
| Verification (no Auth) | Yes |   |
| Minimal Authorization (\$0) policies, by card type) | Yes |   |
| AVS check with standard result mapping | Yes | Use Ignore\_avn\_policy =0/1 attribute when AVS validation is not required. |
| CVV/CVN check with standard result mapping | Yes | Use Ignore\_cvn\_policy=0/1 attribute when CVN validation is not required |
| Support real-time authorization (stand-alone Auth) | Yes |   |
| Void | Yes |   |
| Conditional deposit (auth and capture combination) | Yes |   |
| Capture (stand-alone capture) | Yes |   |
| One-time transactions (real-time) | Yes |   |
| Recurring transactions (flagged recurring) | Yes |   |
| Refunds - Full | Yes | Refund refunds the captured transaction, which is settled on Stripe's end. |
| Refunds - Partial | Yes |   |
| 3DS | Yes |   |
| CITMIT/Card On File | Yes | All the transactions are getting handled using token, so no need of CITMIT |
| Map error/response/result codes to standard actions (Success/Decline/Reject) | Yes |   |
| **Special Implementation Features** |   | |
| Implemented via Payments Microservice | Yes |   |
| Store paymentProcessorTransactionId | Yes |   |
| Retrieve and store Extended Card/Auth Attributes | No |   |
| Support tokenization (for Retain) | Yes | For PaymentIntent API, Token starts with "PM\_". However, it supports the token which can also start with "src\_" and "card\_". |
| Support BIN/Last-4/Expiry Retrieval from external Token | No |   |
| Support detokenization (Subscribe retrieves full PAN/CC details) | No |   |
| Support Card Type identification (from BIN or API) | No |   |
| Support Visa/general "Stored Credential" flags | No |   |
| Account Updater/Amex Card refresher | No |   |
| Automated/manual chargeback feed | Yes | Webhook |
| **Retain Support** |   | |
| Support token as payment method | Yes |   |
| Support detokenization to full PAN | No |   |
| Support detokenization to get BIN | No |   |
| Support Partial Authorization | No |   |
| Support Balance Retrieval | No |   |
| Support Forced Deposit | No |   |

### Payment Processor Documentation

Links to docs:

* [https://stripe.com/docs/api/payment\_intents](https://stripe.com/docs/api/payment_intents)

**Parent topic:**[Stripe - Payment Intent Configuration](../topics/stripeIntentConfiguration_r#)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.