Stripe

The Stripe connector lets you perform insert, delete, update, and read operations on Stripe dataset.

Before you begin

Before using the Stripe connector, do the following tasks:

• In your Google Cloud project:
  • Ensure that network connectivity is set up. For information about network patterns, see Network connectivity.
  • Grant the roles/connectors.admin IAM role to the user configuring the connector.
  • Grant the following IAM roles to the service account that you want to use for the connector:
    • roles/secretmanager.viewer
    • roles/secretmanager.secretAccessor

    A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. For more information, see Creating a service account.

  • Enable the following services:
    • secretmanager.googleapis.com (Secret Manager API)
    • connectors.googleapis.com (Connectors API)

    To understand how to enable services, see Enabling services.

  If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.

• For information about creating a Stripe account, see Create Stripe Account or Create an account and learn how to start using Stripe.

Configure the connector

Configuring the connector requires you to create a connection to your data source (backend system). A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following steps:

1. In the Cloud console, go to the Integration Connectors > Connections page and then select or create a Google Cloud project.

   Go to the Connections page

2. Click + Create New to open the Create Connection page.
3. In the Location section, choose the location for the connection.
   1. Region: Select a location from the drop-down list.

      For the list of all the supported regions, see Locations.

   2. Click Next.
4. In the Connection Details section, complete the following:
   1. Connector: Select Stripe from the drop down list of available Connectors.
   2. Connector version: Select the Connector version from the drop down list of available versions.
   3. In the Connection Name field, enter a name for the Connection instance.

      Connection names must meet the following criteria:

      • Connection names can use letters, numbers, or hyphens.
      • Letters must be lower-case.
      • Connection names must begin with a letter and end with a letter or number.
      • Connection names cannot exceed 49 characters.
   4. Optionally, enter a Description for the connection instance.
   5. Optionally, enable Cloud logging, and then select a log level. By default, the log level is set to Error.
   6. Service Account: Select a service account that has the required roles.
   7. Optionally, configure the Connection node settings:
      • Minimum number of nodes: Enter the minimum number of connection nodes.
      • Maximum number of nodes: Enter the maximum number of connection nodes.

      A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.

   Note: You can customize the connection node values only if you are a Pay-as-you-go customer.
   8. Account Id: The ID of the Account that you want to use.
   9. Use proxy: Select this checkbox to configure a proxy server for the connection and configure the following values:
   • Proxy Auth Scheme: Select the authentication type to authenticate with the proxy server. The following authentication types are supported:
     • Basic: Basic HTTP authentication.
     • Digest: Digest HTTP authentication.
   • Proxy User: A user name to be used to authenticate with the proxy server.
   • Proxy Password: The Secret manager secret of the user's password.
   • Proxy SSL Type: The SSL type to use when connecting to the proxy server. The following authentication types are supported:
     • Auto: Default setting. If the URL is an HTTPS URL, then the Tunnel option is used. If the URL is an HTTP URL, then the NEVER option is used.
     • Always: The connection is always SSL enabled.
     • Never: The connection is not SSL enabled.
     • Tunnel: The connection is through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy.
   • In the Proxy Server section, enter details of the proxy server.
     1. Click + Add destination.
     2. Select a Destination Type.
        • Host address: Specify the hostname or IP address of the destination.

          If you want to establish a private connection to your backend system, do the following:

          • Create a PSC service attachment.
          • Create an endpoint attachment and then enter the details of the endpoint attachment in the Host address field.
   10. Optionally, click + ADD LABEL to add a label to the Connection in the form of a key/value pair.
   11. Click Next.
5. In the Authentication section, enter the authentication details.

   The Strip connection supports the API Key type authentication. Select the Secret Manager secret for the API key from the API Key drop-down, and then select the corresponding secret version.

6. Click Next.
7. Review: Review your connection and authentication details.
8. Click Create.

Connection configuration samples

This section lists the sample values for the various fields that you configure when creating the Stripe connection.

Live API Key connection type

Field name	Details
Location	us-central1
Connector	Stripe
Connector version	1
Connection Name	stripe-connection
Enable Cloud Logging	Yes
Service Account	SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com
Account Id	ACCOUNT_ID
Verbosity Level	5
Minimum number of nodes	2
Maximum number of nodes	50
Live APIKey	LIVE_API_KEY
Secret version	1

For information about the Live API key, see Live API Key.

Entities, operations, and actions

All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.

Note: You can view the entities, operations, and actions of a connector in the Connectors task.

• Entity: An entity can be thought of as an object, or a collection of properties, in the connected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.

  However, it is possible that a connector doesn't support or have any entities, in which case the Entities list will be empty.

• Operation: An operation is the activity that you can perform on an entity. You can perform any of the following operations on an entity:
  • List
  • Get
  • Create
  • Update
  • Delete

  Selecting an entity from the available list, generates a list of operations available for the entity. For a detailed description of the operations, see the Connectors task's entity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in the Operations list.

• Action: An action is a first class function that is made available to the integration through the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case the Actions list will be empty.

Note: All entities and actions will have a schema associated with them. For example, an action schema will have the parameter details such as; the parameter names, and its corresponding data type. The schema (metadata) for entities and actions is fetched by the connection at runtime from your backend. If there are any updates to the schema, such updates won't be automatically reflected in your existing connections; you must manually refresh the schema. To refresh the schema for a connection, open the Connection details page of the connection, and then click Refresh connection schema.

System limitations

The Stripe connector can process 6 transactions per second, per node, and throttles any transactions beyond this limit. By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.

For information on the limits applicable to Integration Connectors, see Limits.

Note: The number of Integration Connectors nodes will autoscale dynamically based on your usage. However, if you want to reserve capacity for large volumes without waiting for autoscaling, you can adjust the minimum node value for a connection. More nodes are required to process more transactions for a connection. Conversely, fewer nodes are required if a connection processes fewer transactions. To configure the node values, do the following:

• If you are a pay-as-you-go customer, configure the minimum and maximum node value in the edit connection page.
• If you are a subscription based customer, contact support.

The maximum transactions that a node can handle depends on various factors. So, before adjusting the minimum nodes for better throughput, it is recommended you check if your backend systems are set up optimally to handle the required traffic.

Use the Stripe connection in an integration

After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.

• To understand how to create and use the Connectors task in Apigee Integration, see Connectors task.
• To understand how to create and use the Connectors task in Application Integration, see Connectors task.

Actions

This section lists the actions supported by the connector. To understand how to configure the actions, see Action examples.

Note: The results of all the actions will be available as a JSON response in the Connectors task's connectorOutputPayload response parameter after you run your integration.

ConfirmPaymentIntent action

This action lets you confirm the payment intent.

Input parameters of the ConfirmPaymentIntent action

Parameter Name	Data Type	Required	Description
PaymentIntentId	String	Yes	The PaymentIntent Id.

For example on how to configure the ConfirmPaymentIntent action, see Action examples.

CapturePaymentIntent action

This action lets you capture the payment intent.

Input parameters of the CapturePaymentIntent action

Parameter Name	Data Type	Required	Description
PaymentIntentId	String	Yes	The PaymentIntent Id.

For example on how to configure the ConfirmPaymentIntent action, see Action examples.

CancelPaymentIntent action

This action lets you cancel the payment intent.

Input parameters of the CancelPaymentIntent action

Parameter Name	Data Type	Required	Description
PaymentIntentId	String	Yes	The PaymentIntent Id.

For example on how to configure the CancelPaymentIntent action, see Action examples.

AttachPaymentMethodToCustomer action

This action lets you attach a PaymentMethod object to a Customer.

Input parameters of the AttachPaymentMethodToCustomer action

Parameter Name	Data Type	Required	Description
PaymentMethodId	String	Yes	The PaymentMethod Id.
CustomerId	String	Yes	The Id of the customer to which to attach the PaymentMethod.

For example on how to configure the AttachPaymentMethodToCustomer action, see Action examples.

DetachPaymentMethodFromCustomer action

Detaches a PaymentMethod object from a Customer. After a PaymentMethod is detached, it can no longer be used for a payment or re-attached to a Customer.

Input parameters of the DetachPaymentMethodFromCustomer action

Parameter Name	Data Type	Required	Description
PaymentMethodId	String	Yes	The PaymentMethod Id.

For example on how to configure the DetachPaymentMethodFromCustomer action, see Action examples.

FinalizeInvoice action

To finalize the draft Invoice.

Input parameters of the Finalize Invoice action

Parameter Name	Data Type	Required	Description
InvoiceId	String	Yes	The QuoInvoicete Id.

For example on how to configure the FinalizeInvoice action, see Action examples.

FinalizeQuote action

To finalize the drafted quote.

Input parameters of the FinalizeQuote action

Parameter Name	Data Type	Required	Description
SouQuoteIdrcePath	String	Yes	The Quote Id.

For example on how to configure the FinalizeQuote action, see Action examples.

AcceptQuote action

This action lets you to accept the quote and generate the Invoice for the accepted quote.

Input parameters of the AcceptQuote action

Parameter Name	Data Type	Required	Description
QuoteId	String	Yes	The Quote Id.

For example on how to configure the AcceptQuote action, see Action examples.

CancelQuote action

This action lets you To cancel the drafted quote.

Input parameters of the CancelQuote action

Parameter Name	Data Type	Required	Description
QuoteId	String	Yes	The Quote Id.

For example on how to configure the CancelQuote action, see Action examples.

Action examples

This section describes how to perform some of the actions in this connector.

Example - Confirm payment intent

This example shows how to confirm the intent of the specified payment.

1. In the Configure connector task dialog, click Actions.
2. Select the ConfirmPaymentIntent action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "ReturnUrl": "http://google.com/",
   "PaymentIntentId": "pi_3OggwFANHgX3SHp71AVrNtT3"
   }

If the action is successful, the ConfirmPaymentIntent task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true",
"id": "pi_3OggwFANHgX3SHp71AVrNtT3",
"object": "payment_intent",
"amount": "33000",
"amount_capturable": "0",
"amount_received": "33000",
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"client_secret": "pi_3OggwFANHgX3SHp71AVrNtT3_secret_YEfjrYL5uHQZrGCx66cJbedlA",
"confirmation_method": "automatic",
"created": "1707196279",
"currency": "usd",
"invoice": null,
"last_payment_error": null,
"latest_charge": "ch_3OggwFANHgX3SHp71uYScRAw",
"level3": null,
"livemode": "false",
"next_action": null,
"on_behalf_of": null,
"payment_method": "pm_1Oggu6ANHgX3SHp7zaRNKNVL",
"payment_method_configuration_details": null,
"payment_method_options.card.installments": null,
"review": null,
"setup_future_usage": null,
"statement_descriptor_suffix": null,
"status": "succeeded",
"transfer_data": null,
"transfer_group": null
}]

Example - Capture payment intent

This example shows how to capture the intent of the specified payment.

1. In the Configure connector task dialog, click Actions.
2. Select the CapturePaymentIntent action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "PaymentIntentId": "pi_3Ogh4sANHgX3SHp72YB0YotA"
   }

If the action is successful, the CapturePaymentIntent task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true",
"id": "pi_3Ogh4sANHgX3SHp72YB0YotA",
"object": "payment_intent",
"amount": "33000",
"amount_capturable": "0",
"amount_received": "33000",
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "manual",
"client_secret": "pi_3Ogh4sANHgX3SHp72YB0YotA_secret_jgqc0olEAOTcurQSDeQThJa3X",
"confirmation_method": "automatic",
"created": "1707196814",
"currency": "usd",
"customer": "cus_Okyi4e7t7BImUL",
"description": null,
"invoice": null,
"last_payment_error": null,
"latest_charge": "ch_3Ogh4sANHgX3SHp72uGBS7g4",
"level3": null,
"livemode": "false",
"next_action": null,
"on_behalf_of": null,
"payment_method": "pm_1Ogh4FANHgX3SHp7GBJJvfGR",
"payment_method_configuration_details": null,
"payment_method_options.card.installments": null,
"payment_method_types": null,
"processing": null,
"receipt_email": null,
"review": null,
"statement_descriptor_suffix": null,
"status": "succeeded",
"transfer_data": null,
"transfer_group": null
}]

Example - Cancel payment intent

This example shows how to cancel the intent of the specified payment.

1. In the Configure connector task dialog, click Actions.
2. Select the CancelPaymentIntent action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "PaymentIntentId": "pi_3Ogh7HANHgX3SHp738skMdSQ"
   }

If the action is successful, the CancelPaymentIntent task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true",
"id": "pi_3Ogh7HANHgX3SHp738skMdSQ",
"object": "payment_intent",
"amount": "33000",
"amount_capturable": "0",
"amount_received": "0",
"canceled_at": "1707197160",
"cancellation_reason": null,
"capture_method": "manual",
"client_secret": "pi_3Ogh7HANHgX3SHp738skMdSQ_secret_NqQsBexbdyk19ETdMnpQXF19j",
"confirmation_method": "automatic",
"created": "1707196963",
"currency": "usd",
"customer": "cus_Okyi4e7t7BImUL",
"description": null,
"invoice": null,
"last_payment_error": null,
"latest_charge": "ch_3Ogh7HANHgX3SHp73LJMZiy5",
"level3": null,
"livemode": "false",
"next_action": null,
"on_behalf_of": null,
"payment_method": "pm_1Ogh75ANHgX3SHp79MNT6IHs",
"payment_method_configuration_details": null,
"receipt_email": null,
"review": null,
"setup_future_usage": null,
"shipping": null,
"status": "canceled",
"transfer_data": null,
"transfer_group": null
}]

Example - Attach payment method to a customer

This example shows how to attached a payment method to the specified customer.

1. In the Configure connector task dialog, click Actions.
2. Select the AttachPaymentMethodToCustomer action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "PaymentMethodId": "pm_1OYm2nANHgX3SHp7ihGfm5U8",
   "CustomerId": "cus_PNX7n9xMDsMPH4"
   }

If the action is successful, the AttachPaymentMethodToCustomer task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true"
}]

Example - Detach payment method from a customer

This example shows how to detach payment method from a customer.

1. In the Configure connector task dialog, click Actions.
2. Select the DetachPaymentMethodFromCustomer action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "PaymentMethodId": "pm_1OYm2nANHgX3SHp7ihGfm5U8"
   }

If the action is successful, the DetachPaymentMethodFromCustomer task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true"
}]

Example - Finalize an invoice

This example shows how to finalize an invoice.

1. In the Configure connector task dialog, click Actions.
2. Select the FinalizeInvoice action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "InvoiceId": "in_1OhnXRANHgX3SHp73ufStlXy"
   }

If the action is successful, the Finalize Invoice task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true",
"id": "in_1OhnXRANHgX3SHp73ufStlXy",
"object": "invoice",
"account_country": "US",
"account_name": "ZBTA_US_SAPDPA_TestAccount",
"billing_reason": "manual",
"charge": null,
"collection_method": "charge_automatically",
"created": "1707459976",
"currency": "usd",
"discounts": null,
"due_date": null,
"effective_at": "1707460034",
"ending_balance": "0",
"footer": null,
"lines.data": null,
"lines.has_more": "false",
"lines.total_count": "0",
"livemode": "false",
"next_payment_attempt": null,
"number": "F3C0E263-0004",
"on_behalf_of": null,
"paid": "true",
"paid_out_of_band": "false",
"payment_intent": null,
}]

Example - Finalize a quote

This example shows how to finalize a quote.

1. In the Configure connector task dialog, click Actions.
2. Select the FinalizeQuote action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "QuoteId": "qt_1ObiPfANHgX3SHp7KT7DXaJe"
   }

If the action is successful, the FinalizeQuote task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true"
}]

Example - Accept a quote

This example shows how to accept a quote.

1. In the Configure connector task dialog, click Actions.
2. Select the AcceptQuote action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "QuoteId": "qt_1ObmqKANHgX3SHp7ahHydwav"
   }

If the action is successful, the AcceptQuote task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"InvoiceId": "in_1Obmr5ANHgX3SHp7HKi6bJDu",
"Success": "true"
}]

Example - Cancel a quote

This example shows how to cancel a quote.

1. In the Configure connector task dialog, click Actions.
2. Select the CancelQuote action, and then click Done.
3. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "QuoteId": "qt_1Obmu3ANHgX3SHp7as57wBLf"
   }

If the action is successful, the CancelQuote task's connectorOutputPayload response parameter will have a value similar to the following:

[{
"Success": "true"
}]

Entity operation examples

This section shows how to perform some of the entity operations in this connector.

Example - List all customers

This example lists all the customers in the Customer entity.

1. In the Configure connector task dialog, click Entities.
2. Select Customer from the Entity List.
3. Select the List operation, and then click Done.
4. Optionally, in Task Input section of the Connectors task, you can filter your result set by specifying a filter clause. Specify the filter clause value always within the single quotes (').
.

Example - Get a customer record

This example gets the specified customer record.

1. In the Configure connector task dialog, click Entities.
2. Select Customer from the Entity list.
3. Select the Get operation, and then click Done.
4. In the Task Input section of the Connectors task, click EntityId and then enter cus_OxHsz0u5bCGWuy in the Default Value field.

   Here, cus_OxHsz0u5bCGWuy is a unique record ID in the Customer entity.

Example - Create a payment intent

This example creates a payment intent in the PaymentIntent entity.

1. In the Configure connector task dialog, click Entities.
2. Select PaymentIntent from the Entity list.
3. Select the Create operation, and then click Done.
4. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "PaymentMethod": "pm_1OXN5YANHgX3SHp7Q5Y0rb39",
   "Currency": "usd",
   "Amount": 1500.0
   }

   If the integration is successful, your connector task's connectorOutputPayload response parameter will have a value similar to the following:

   {
   "Id": "pi_3OXN69ANHgX3SHp70tgsxkuR"
   }

Example - Update a customer record

This example updates the details of the specified customer.

1. In the Configure connector task dialog, click Entities.
2. Select Customer from the Entity list.
3. Select the Update operation, and then click Done.
4. In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

   {
   "Name": "John"
   }

5. Click entityId, and then enter cus_OxHsz0u5bCGWuy in the Default Value field.

   If the integration is successful, your connector task's connectorOutputPayload field will have a value similar to the following:

   {
   "Id": "cus_OxHsz0u5bCGWuy"
   }

Example - Delete a customer record

This example deletes the specified customer from the Customer entity.

1. In the Configure connector task dialog, click Entities.
2. Select Customer from the Entity list.
3. Select the Delete operation, and then click Done.
4. Click EntityId and then enter cus_OxIqiMh1W335rE in the Default Value field.

Note: If your entity has a composite primary key, you can specify a filter clause.

Use terraform to create connections

You can use the Terraform resource to create a new connection.

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

To view a sample terraform template for connection creation, see sample template.

When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:

Parameter name	Data type	Required	Description
proxy_enabled	BOOLEAN	False	Select this checkbox to configure a proxy server for the connection.
proxy_auth_scheme	ENUM	False	The authentication type to use to authenticate to the ProxyServer proxy. Supported values are: BASIC, DIGEST, NONE
proxy_user	STRING	False	A user name to be used to authenticate to the ProxyServer proxy.
proxy_password	SECRET	False	A password to be used to authenticate to the ProxyServer proxy.
proxy_ssltype	ENUM	False	The SSL type to use when connecting to the ProxyServer proxy. Supported values are: AUTO, ALWAYS, NEVER, TUNNEL
account_id	STRING	False	The ID of the Account that you want to use.
verbosity	STRING	False	Verbosity level for connection, varies from 1-5. Higher verbosity level will log all the communication details (request,response & ssl certificates).

Get help from the Google Cloud community

You can post your questions and discuss this connector in the Google Cloud community at Cloud Forums.

What's next

• Understand how to suspend and resume a connection.
• Understand how to monitor connector usage.
• Understand how to view connector logs.