{"id":3274,"date":"2023-03-17T14:32:28","date_gmt":"2023-03-17T13:32:28","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=3274"},"modified":"2026-06-04T15:23:52","modified_gmt":"2026-06-04T13:23:52","slug":"bank-contracts-how-to-add-them","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/bank-contracts-how-to-add-them\/","title":{"rendered":"Banking contracts \u2013 Set them up"},"content":{"rendered":"\n
\"Smart<\/figure>\n\n\n\n

[Reading time: 4 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

A Banking contract<\/strong> connects INO cx to the payment processor that actually executes your transactions. Two processors are supported:<\/p>\n\n\n\n

    \n
  • Ino pay<\/strong>: (only available in France) the INO cx in-house payment service, attached to a bank with a VAD or VADS acceptance contract.<\/li>\n\n\n\n
  • Stripe<\/strong>: integration with a Stripe account, configured with the public and secret keys of the Stripe dashboard.<\/li>\n<\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    A banking contract is a prerequisite for any payment module<\/strong>: when you create a payment module, you pick which banking contract handles the actual transactions for it. You can configure several banking contracts in parallel \u2014 for example one Ino pay contract and one Stripe contract \u2014 and use them on different payment modules.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    1. Access and permissions<\/h2>\n\n\n\n

    Banking contracts are configured in the Maker<\/strong>, in the Payment<\/strong> module. From the left menu, open Payment > Banking contracts<\/strong>. The module is part of the Smart licence.<\/p>\n\n\n\n

    To access and configure banking contracts, the user\u2019s role must include the appropriate rights on the Banking contracts<\/strong> entity:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n
      \n
    • Read<\/strong> \u2013 view the list and details of banking contracts.<\/li>\n\n\n\n
    • Create<\/strong> \u2013 create a new banking contract.<\/li>\n\n\n\n
    • Modify<\/strong> \u2013 edit an existing banking contract.<\/li>\n\n\n\n
    • Delete<\/strong> \u2013 delete a single banking contract or several at once.<\/li>\n<\/ul>\n\n\n\n

      These permissions are managed in the Roles<\/strong> module of the Maker.<\/p>\n\n\n\n

      2. The list view<\/h2>\n\n\n\n

      The Banking contracts list shows five columns:<\/p>\n\n\n\n

      Column<\/th>Description<\/th><\/tr><\/thead>
      Contract type<\/strong><\/td>The processor \u2014 Ino pay<\/em> or Stripe<\/em>, shown as a coloured tag.<\/td><\/tr>
      Status<\/strong><\/td>The current state of the contract: Active<\/em>, Inactive<\/em> or Error<\/em> (see section 5).<\/td><\/tr>
      Name<\/strong><\/td>Display name of the contract.<\/td><\/tr>
      Bank<\/strong><\/td>For Ino pay contracts, the linked bank. Empty (--<\/code>) for Stripe.<\/td><\/tr>
      Contract number<\/strong><\/td>For Ino pay contracts, the contract number provided by the bank. Empty for Stripe.<\/td><\/tr>
      AS rank number<\/td>For Ino pay contracts, the 3-digit number of the acceptance system. Empty for Stripe.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      A search bar at the top lets you find a banking contract by its name.<\/p>\n\n\n\n

      3. Create a banking contract<\/h2>\n\n\n\n

      To create a new banking contract:<\/p>\n\n\n\n

        \n
      1. Go to Maker > Payment > Banking contracts<\/strong>.<\/li>\n\n\n\n
      2. Click the +<\/strong> button at the top right.<\/li>\n\n\n\n
      3. Pick the Contract type<\/strong> \u2014 Ino pay<\/em> or Stripe<\/em>.<\/li>\n\n\n\n
      4. Fill in the Name<\/strong> of the contract (display name only).<\/li>\n\n\n\n
      5. Fill in the fields specific to the chosen type \u2014 see section 3.1 or 3.2 below.<\/li>\n\n\n\n
      6. Click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
        \"\"<\/figure>\n\n\n\n

        3.1. Ino pay contract<\/h3>\n\n\n\n

        When the contract type is Ino pay<\/strong>, the following fields are displayed and required:<\/p>\n\n\n\n

        Field<\/th>Required<\/th>Description<\/th><\/tr><\/thead>
        Bank<\/strong><\/td>Yes<\/td>The bank associated with the contract. Pick it from the list of banks available on the platform.<\/td><\/tr>
        Contract number<\/strong><\/td>Yes<\/td>The contract number provided by the bank. Up to 255 characters.<\/td><\/tr>
        Contract type<\/strong><\/td>Yes<\/td>VAD<\/em> or VADS<\/em> \u2014 the acceptance contract type provided by the bank.<\/td><\/tr>
        AS rank number<\/strong><\/td>Yes<\/td>3-digit number of the acceptance system (Syst\u00e8me d\u2019Acceptation).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        3.2. Stripe contract<\/h3>\n\n\n\n

        For a complete walk-through of the Stripe integration \u2014 creating a Stripe account, retrieving the API keys from the Stripe dashboard, the Stripe-specific limitations inside INO cx \u2014 follow the dedicated Stripe<\/strong><\/a> article of the help center. The fields described below are what appears on the Banking contracts form once you have your keys ready.<\/p>\n\n\n\n

        When the contract type is Stripe<\/strong>, the following fields are displayed and required:<\/p>\n\n\n\n

        Field<\/th>Required<\/th>Description<\/th><\/tr><\/thead>
        Stripe public key<\/strong><\/td>Yes<\/td>The publishable key from your Stripe dashboard. Used by the client-side of the payment form.<\/td><\/tr>
        Stripe private key<\/strong><\/td>Yes<\/td>The secret key from your Stripe dashboard. Used by the server-side to authorise transactions.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Saving a Stripe contract automatically sets up everything needed on your Stripe account to confirm the payments made through INO cx. Make sure the secret key is correct \u2014 an invalid key will prevent the contract from being saved.<\/p>\n\n\n\n

        Both keys are found in your Stripe dashboard. Treat the secret key as a password \u2014 do not share it.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        4. Status of a contract<\/h2>\n\n\n\n

        Once saved, a banking contract is automatically tested against the processor. Its Status<\/strong> column in the list reflects the result:<\/p>\n\n\n\n

        Status<\/th>Meaning<\/th><\/tr><\/thead>
        Active<\/strong><\/td>The contract is valid and ready to be used by a payment module.<\/td><\/tr>
        Inactive<\/strong><\/td>The contract is not yet ready. This usually means the bank has not confirmed it yet. To stop using a contract, detach it from its payment modules and delete it \u2014 there is no manual switch to deactivate it.<\/td><\/tr>
        Error<\/strong><\/td>The contract could not be validated by the processor. Check the keys, the contract number or the AS rank and save again.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \"\"<\/figure>\n\n\n\n

        Only contracts in the Active<\/em> state can be selected when creating or editing a payment module.<\/p>\n\n\n\n

        5. Edit, duplicate or delete a banking contract<\/h2>\n\n\n\n

        From the Banking contracts<\/strong> list, each row provides the following actions:<\/p>\n\n\n\n

        Action<\/th>Description<\/th><\/tr><\/thead>
        Edit<\/strong><\/td>Modify the Name, the Contract type and all the type-specific fields.<\/td><\/tr>
        Duplicate<\/strong><\/td>Create a copy of the contract. Useful when several contracts share most of their parameters. The duplicated contract keeps the original type and field values; update them as needed.<\/td><\/tr>
        Delete<\/strong><\/td>Remove the contract. Before deleting a contract that is still referenced by a payment module, detach it from the module first, otherwise the module will no longer be usable.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Several contracts can be deleted at once by selecting them in the list and using the bulk delete action.<\/p>\n\n\n\n

        6. Next step<\/h2>\n\n\n\n

        Once at least one banking contract is in the Active<\/em> state, you can use it from a Payment module<\/strong> to define how, when and through which channels payments are taken. See the Payment modules \u2013 Set them up<\/strong> article of the help center.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Bank contracts are the key to the use of payment modules in your interactions with your customers. In this article, we will see how to add them in the Maker and set them up.<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[107],"ht-kb-tag":[147,131],"class_list":["post-3274","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-configuring","ht_kb_tag-admin","ht_kb_tag-maker"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3274","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=3274"}],"version-history":[{"count":7,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3274\/revisions"}],"predecessor-version":[{"id":6639,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3274\/revisions\/6639"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=3274"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=3274"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=3274"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}