john-zaprite

The following is the ideal flow Zaprite would like to have when using the Ibex Pay API.

API key

Zaprite should have it's own 'partner' API key that we store as an environment variable in our Next JS app.

Permissions

1. Create public invoices on a user's behalf

john-zaprite

The following is the ideal flow Zaprite would like to have when using the Galoy API.

API key

Zaprite should have it's own API key that we store as an environment variable in our Next JS app.

Permissions

1. Create public invoices on a user's behalf
2. Watch for settlement of those invoices

john-zaprite

import { NextApiRequest, NextApiResponse } from 'next'

export default async (req: NextApiRequest, res: NextApiResponse) => {
	const challenge = req.query.challenge
	const LNESCROW_USER = process.env.LNESCROW_USER
	const LNESCROW_PSWD = process.env.LNESCROW_PSWD

	try {
		const response = await (
			await fetch('https://api.satsarcade.com/getsession/', {

john-zaprite

import {
	Box,
	Button,
	Heading,
	HStack,
	Image,
	Input,
	Spinner,
	Stack,
	Text,

john-zaprite

Keybase proof

I hereby claim:

• I am john-magill on github.
• I am jmagill (https://keybase.io/jmagill) on keybase.
• I have a public key ASBGZ8yuqsMDZY_04zjOHql8JhSrn20kWbwCzxptGZJZ7wo

To claim this, I am signing this object:

john-zaprite

Verifying my Blockstack ID is secured with the address 1FDB6yhUhFmD6HYjwxYo8NZPLz3PRxzQhu https://explorer.blockstack.org/address/1FDB6yhUhFmD6HYjwxYo8NZPLz3PRxzQhu