m3terDocumentation

On this page

Configuring Stripe Integrations

You can define and manage native integrations for sending your end customer Account Bills generated in m3ter outbound into your Stripe system:

Creating the Integration

You can quickly set up a native Stripe integration from the Configurations page in the Console.

Notes:

  • Stripe or Stripe (Test mode)? The difference between these two integrations is: selecting Stripe means an integration destination into your Stripe production environment; selecting Stripe (Test mode) means an integration destination into your Stripe test environment. The configuration settings are the same for both destinations.

  • Tip: Reviewing Integration Runs! When you've set up an integration with Stripe for your Organization in your production environment, you can review details of the integration runs performed for the integration. See Reviewing Integration Run Details.

To define a m3ter - Stripe integration:

1. Select Integrations:

The Configurations page opens in Grid view.

2. Under Stripe, select Create new integration>Integrate bills with Stripe:

The Create page opens and the Entity type - Bill and Integration destination - Stripe are shown at the top of the page.

3. Use the Global Configuration panel to:

  • Enter a Name for the Integration. This is required and is useful if you intend to create multiple Integrations for the same Destination/Entity Type and need to clearly differentiate them.

  • Select the Accounts you want the integration to apply to:

    • Account ids. Select the Accounts you want to include - all selected Accounts are treated as allowed for the integration.

    • Restricted account ids. Select the Accounts you want to exclude - all selected Accounts are treated as disallowed for the integration.

Notes:

  • If you want to include all Accounts in the integration, leave both Accounts ids and Restricted account ids empty.

  • Any filtering by Account ids you define using these settings to control which Accounts the integration runs for will be in addition to any filtering you define using the Account filter option - see the following step for Entity Configuration options.

  • Select Users for Email notifications if disabled:

    • Integration disabled notification users. Select Organization Users you want to receive an Email notification if the integration is automatically disabled.

Notes:

  • An integration is automatically disabled if there have been 10 successive previous error Event responses to earlier attempts to run the integration. See Reviewing and Resolving Integration Events for more details.

  • If you select Organization Users to receive an Email notification when the integration is automatically disabled, their User id will be listed under Configuration Data on the Integration Details page.

4. Use the Entity configuration panel to configure the m3ter entity you will be synchronizing with for the integration. In the case of a Bill integration, this entity will be the Bill generated for a customer Account in m3ter:

  • Only send bill on approval. Enable this if you only want Bills to be sent when they have been approved. If disabled, the Bill will be sent every time it is regenerated. Default is disabled. Note that:

    • The frequency of Bills sent will depend on the billing frequency defined for the Account Plan attached to the Account - such as daily/weekly/monthly/annually.

    • If an Account has a Prepayment on it and the billing for Prepayment fees is configured to run on a customized schedule, Bills will be sent when scheduled Bills are generated.

    • If a Bill is manually recalculated the updated Bill will be sent.

    • If you enable this, then the integration will not run for all Bill Jobs.

  • Use external mapping account code. Enable this if you want the integration to look in the External Mappings for the Account identifier code, which means you can use an external Id. If this is disabled, the m3ter Account Id is used. Default is disabled.

  • Excluded line item types. Optionally filter the Bill line items you send to the destination system. For example, only send charges or credits and exclude all other line items.

  • Account filter. Optionally, enter an expression that is run on the Account to determine whether or not the integration is run. You can use this setting if you have multiple destinations for sending Bills outbound to your Stripe system. For example:

    • customFields != null AND customFields.country = = UK

    • In this example, the integration will run for an Account only if you have created a Custom Field for the Account called country and given the field a value of UK.

Notes:

  • Other Account fields for Account filter expression? You can reference other fields on the Account object in the Account filter expression. For details and another example, see Managing Multiple Third Party Destinations for Integrations.

  • Additional filtering? Any global filtering you define using the settings to include/exclude Accounts for integration runs by Account ids will be in addition to any filtering you define using the Account filter option - see the previous step for Global Configuration.

  • Enforce external mappings for config. Optionally enable this if you want the integration to use only those external mappings specified as being for this configuration.

    • Note that when creating External Mappings, you can select the Parent Configuration for a mapping. If you enable the Enforce external mappings for config setting for your Stripe integration, please ensure you have used the Parent Configuration setting to define which mappings are to be used by your Stripe integration. See Creating and Managing External Mappings for more details.

5. Use the Destination configuration panel to enter the settings specific to the destination system. These settings include field mappings as well as other system-specific configurations. Note that these settings will change for each destination:

  • Create stripe invoice. Enable this if you want the integration to create a Stripe invoice:

    • Set this switch to true if you are using Stripe Subscription Invoicing.

    • Set this switch to false if you are using Stripe Subscriptions.

  • Price data product id. Enter the Product Id in your Stripe Product List in order to enable the integration to set tax-related fields on line items that should be sent from m3ter. Only one Product Id is required.

  • Po number custom field. Enter the name of the custom field in the Stripe system that will used for the Purchase Order number that appears in the m3ter Bill.

  • Sort line items by. Optionally, select a property to sort line items by before they are sent out to the external system. Three options:

    • None

    • Subtotal

    • Aggregation ID

  • Send due date. If you want the m3ter Bill due date to be sent through when creating Stripe invoices, enable this switch. Note that this should be disabled if Stripe is configured to automatically charge invoices. Default is disabled.

6. Select Create integration. You are taken to the details page for the integration, where you can immediately complete the configuration by setting up authentication to allow the integration to connect with your Stripe system - see the following Setting Up Authentication section for details:

  • Note that if you are not ready to continue your workflow immediately and set up authentication, you can do this at a later time.

Setting Up Authentication for the Integration

When you have created a Stripe integration, you can select an Integration Credential you've created for authentication allowing the integration to connect with your Stripe system:

  • Note that if you've followed the workflow given in the earlier section for creating the integration, on creation you'll be taken directly to the Integration Details page to continue and immediately set up authentication. The procedure described in this section assumes you've returned at a later date to set up authentication for the integration - the main steps you need to follow if you're setting up authentication immediately after creation are the same.

To set up authentication for your m3ter - Stripe integration:

1. Select Configurations. The Configurations page opens in Grid view.

2. Under Stripe, select the NAME hotlink text of the Stripe integration you want to set up authentication for. The Integration details page opens:

  • Notes:

    • A warning is shown that the integration is not yet connected to your Stripe system.

    • The ID of the integration configuration is shown at the bottom of the Details card, and you can copy the ID directly to your clipboard.

3. Select Add Credential. A Select one credential modal appears.

4. Select a Credential you created earlier and want to use to authenticate the integration with Stripe. See Creating Stripe Integration Credentials.

5. Select Confirm. The modal closes and on Integrations details, the integration now shows as CONNECTED:

  • If at any time you want to disconnect the integration, select Disconnect.

  • If you want to use a different Credential for connecting the integration, select Update credential. The Select one credential modal appears and you can select a different Credential.

Tip: Testing your Native Integration Setup? Your Stripe integration is now available for use. However, it remains in Beta release and we strongly recommend you test the implementation in your m3ter Sandbox or QA environment before releasing it to your Production environment. See section 7. of our Terms of Service for Beta Usage.

Tip: Integrations API Calls? When you have set up your Stripe integration, you can review and manage the integration using a full set of API Calls. See the Integrations section of our API Reference Docs.

Next: Managing Multiple Third Party Destinations for Integrations


Additional Support

Login to the Support portal for additional help and to send questions to our Support team.