Can I use my own payment infrastructure with Request Network requests?

[MantisClone]

I'm building an established payment project and I want to add decentralized invoices built using Request Network. Is Request Network compatible with my existing payment infrastructure? Can I integrate my existing payment infrastructure into Request Network?

[MantisClone]

Yes. Request Network is open to integrating 3rd party payment infrastructure as long as the integration is open-source and results in Pull Requests (PRs) into the Request Network SDK that enables all of the Builders in our ecosystem to benefit and use the payment infrastructure.

Details

• Request Network payment detection relies on events emitted during the payment transaction that contain a paymentReference which ties the payment to the request. The paymentReference is an 8-byte hash derived from the request ID.

Option 1: Update the 3rd party payment smart contract to emit the paymentReference event.

This means adding a new payment network. This would require updates to the following components:

• payment-subgraph repo - indexes on-chain payment events
• requestNetwork monorepo
  • payment-detection - functions to query the payment-subgraph
  • advanced-logic - payment network definitions
  • payment-processing - functions to call the smart contracts
  • request-client - functions to create and update requests

Example

These PRs added the ERC20TransferableReceivable payment network

• feat: ERC20TransferableReceivable payments-subgraph#48
• feat: ERC20TransferableReceivable payment network #1033

Option 2: Update the 3rd party payment smart contract to call one of the existing Request Network payment network smart contracts.

In this case, the existing payment detection system should work out of the box without changes. This may, or may not involve adding a new payment network. This would require updates to the following components:

• requestNetwork monorepo
  • payment-processing - functions to call the smart contracts
  • request-client - functions to create and update requests

Option 3: Deploy a One Time Proxy smart contract for each request.

This option is not yet available and will be implemented in #1283