Stripe Integration Overview
Get an overview of the Stripe integration in Maica.
Last updated
Get an overview of the Stripe integration in Maica.
Last updated
In Maica, there are two main processes that the Stripe Integration supports, these are:
Manual Sync via Process Invoice Quick Action
Automated Sync via Salesforce Flow
To learn about the Manual Sync Process, click here.
This article further explains and provides an overview of the Automated Sync via Salesforce Flow in Maica.
The below diagram outlines the steps involved in the automated Stripe sync, as well as the outcomes of the process.
Condition | Description |
---|---|
| In order for the Processing Sync to be triggered, the
These conditions are further explained below. |
| Once the above conditions are met, the Sync will be executed. This essentially means the Sync will be active 24/7 and triggered to run at any time the conditions are met.
A Sync can also be manually executed if required, click here to learn how to manually Process an Invoice.
The Flow responsible for this Automation in Maica is the |
| Once the Sync is executed, an |
| Immediately after the |
| Once the You can learn more about the Payment Record fields below. |
| For traceability, the
These fields will assist you in locating the Payment/Invoice in Stripe. The creation of the
The Invoice |
| The process completes. |
Once the Invoice
is created in Stripe, the Invoice Amount
cannot be edited in Maica at the Invoice
level. This is managed by Maica's validation; for additional information, click here.
The following table further outlines the required conditions for the Sync to commence.
Condition | Description |
---|---|
| The invoice must have an outstanding balance that is greater than zero. This means there's an amount that still needs to be paid. |
| The total amount for the invoice must be greater than zero. This ensures that only invoices with actual charges are processed. |
| The invoice status must be marked as |
| This condition checks that the invoice has not already been processed through Stripe. If the invoice has a Stripe ID, it means it has already been synced. |
( | The invoice is either for a self-managed participant or it is marked as a co-payment invoice, meaning the participant is responsible for a portion of the payment. |
| The participant or your organisation has authorised automatic billing through Stripe by checking the |
| The participant must have a valid |
As mentioned, after a Payment has been applied to an Invoice a Payment Record will be created. It includes a number of important fields, including:
Field | Description |
---|---|
| This field indicates the type of Payment Record, whether it is a transaction processed via Stripe or a Reconciliation following a Payment applied to an invoice in the Finance System (Xero). |
| This field indicates how the Payment was created. |
| This field indicates if the Payment has been successfully processed. For example, the Invoice has been reconciled in Xero and synchronised with Maica. |
| This field indicates if the Payment Amount should be included in the rollup to the |
| This field indicates the Date & Time in which Payment was received |
| The unique identifier of the Payment record in an external system. Maica uses this field as part of the Xero integration. |
| The amount of the received Payment. This can be the full or a partial amount of the total Invoice. |
| The ID of the corresponding Payment record in Stripe. |
| The ID of the corresponding Invoice record in Stripe. |
| The Error Code returned by Stripe |
| The Error Message returned by Stripe |