Skip to main content
Card processors can be either classified as open or closed-loop processors. A processor is defined as being open-loop when it allows processing a subsequent transaction that had its initial transaction with a different processor. Additionally, open-loop processors generally support network tokens as well. A closed-loop processor on the other can only be used to make subsequent transactions that were originally started with the same processor. For these processors, subsequent transactions can only ever be created using the same proprietary PSP token, limiting its re-use.

Merchant-initiated transactions

As a consequence of the preceding, in the subsequent merchant-initiated transaction (MIT) scenario, there are limitations as to what connection can be used to process the transaction, regardless of what the flow routing rules may define. For a merchant-initiated transaction with a stored payment method, Gr4vy only considers the following connections.
  • Open-loop connections, which receive the card data from the vault.
  • Closed-loop connections that hold their own token for the card, because the card was stored through that connection.
A stored scheme transaction ID doesn’t decide which connection processes the payment. Flow routing rules still apply. To keep a subsequent payment on the connection that processed the initial transaction, set payment_service_id to that connection’s ID. The transaction then skips routing rules.

What closed loop means in practice

  • A closed-loop connection only processes merchant-initiated transactions for cards stored through it, using its own token. Other closed-loop connections in the rule are left out.
  • A card stored only through open-loop connections can’t fall back to a closed-loop connection for a merchant-initiated transaction.
  • Customer-initiated transactions, including the first payment in a series, can still fail over between open-loop and closed-loop connections.
  • Network tokens are only used with open-loop connections.
When you add a closed-loop connection to a Flow rule, the dashboard shows a reminder of these limits.

Closed-loop connections

The following card connections are closed loop. The following card connections are closed loop by default, and can be switched to open loop. The provider has to allow open-loop processing on your account first. Once it has, turn on Open loop in the connection’s settings in the dashboard. To set this through the API instead, pass open_loop: true when you create or update the payment service. If you leave it out when you create the payment service, the connection is closed loop. Sending open_loop for a connection that can’t be switched returns a validation error. On these connections, provider tokenization follows the open-loop setting. A closed-loop connection stores a provider token for the card, and an open-loop connection doesn’t. Leave payment_method_tokenization_enabled out of the request, because sending it for these connections returns a validation error. Network tokens are only available on open-loop connections. Sending network_tokens_enabled: true for a closed-loop connection returns a validation error.

Switch an existing connection

You can switch a connection that already has stored cards. The switch applies to every stored card, including cards stored before the change.
  • After you switch to open loop, Gr4vy sends the card data from the vault, or a network token, for every stored card. It no longer uses the provider tokens that the connection created while it was closed loop.
  • After you switch back to closed loop, cards stored before the open-loop period still have their provider token and work as before. Cards stored while the connection was open loop have no provider token for it. A customer-initiated transaction on the connection creates one, but until then the connection can’t process merchant-initiated transactions for these cards. Route those transactions to an open-loop connection instead.
  • If you turned on network tokens while the connection was open loop, send network_tokens_enabled: false in the same request that sets open_loop: false.
All other card connections that process payments are open loop.