Very simply, Bitpanda Custody can enable automatic co-signing of outbound transactions that meet certain rules. Used in conjunction with our trustvault-co-signing-service, you can specify a set of rules that will allow our trustvault-co-signing-service to sign the transaction to help automate your transaction sending flow.

Imagine you have an operations dept that you would like to send your transactions if the transaction value is below £2,000. However, if the transaction value is £2,000 or above you'd like it signed by management instead.

We can create a wallet policy such that the transaction is sent if;

OR

The trustvault-co-signing-service will take trusted data from the Bitpanda Custody and only sign if the rules are met. The trustvault-co-signing-service rules would simply be:

Of course, the wallet policy can be far more flexible and allow overrides or mixing and matching of signatures

Since you are utilising the trustvault-co-signing-service you could include different rules. Only sign if its BTC? Only sign if its ETH but to a particular address?

The rules are very configurable with the only limits being that they can operate on values present in the transaction. If you wanted to only sign if the weather in London was above 5C then that is possible but we'd need to look at weather feeds.

If you would like to include more sensitive data in your rules or you'd like to call a private API we suggest you run the co-signing-service yourself. There is an open-source co-signing-service framework available to help you.

It should be noted that not all transactions can be valued. Sending ETH or BTC is quite straight forward, as is sending supported ERC-20 tokens. However, when sending to contracts it can get difficult to value the transaction. As such, we currently only sport valuing the following:

(At this time ETH transfers to any contract (including a on-chain wallet or vault) are not valued)