# Redirected payment pointers

**URL:** https://forum.interledger.org/t/redirected-payment-pointers/809
**Category:** Protocol Design
**Created:** [October 14, 2019, 2:15pm UTC](https://forum.interledger.org/t/redirected-payment-pointers/809 "2019-10-14T14:15:11Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![shortname](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@shortname](https://forum.interledger.org/u/shortname)
#### Post date: [October 14, 2019, 2:15pm UTC](https://forum.interledger.org/t/redirected-payment-pointers/809/1 "2019-10-14T14:15:11Z")

</div>

Hi,

As a end-user, say I wanted to use a shorter payment pointer for web monetization. E.g.

```
<meta name="monetization" content="$example.com">

```

What would be required to point this to the payment pointer provided by my wallet provider?

Is HTTP 302 redirecting `https://example.com/.well-known/pay` to `https://pay.stronghold.co/<myaccounthash>` enough?

---

<div class="post-metadata">

### Author: ![adrianhopebailie](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/adrianhopebailie/32/31_2.png) [@adrianhopebailie](https://forum.interledger.org/u/adrianhopebailie)
#### Post date: [October 14, 2019, 2:48pm UTC](https://forum.interledger.org/t/redirected-payment-pointers/809/2 "2019-10-14T14:48:10Z")

</div>

The specification is not actually specific on this so it will really depend on the client.

`ilp-protocol-spsp` is the reference client and uses `node-fetch` which will follow redirects by default so I’d say the answer is YES.

I’ll update the spec to reflect this

---

<div class="post-metadata">

### Author: ![shortname](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@shortname](https://forum.interledger.org/u/shortname)
#### Post date: [October 14, 2019, 3:36pm UTC](https://forum.interledger.org/t/redirected-payment-pointers/809/3 "2019-10-14T15:36:23Z")

</div>

> [@adrianhopebailie](#):
>
> I’ll update the spec to reflect this

Thanks for the clarification! Remember to specify the max number of redirects and that the whole redirect-chain must use HTTPS.

Update: Oh, and 301 permanent can be cached whereas 302 shouldn’t be cached longer than `cache-control:max-age=sec` response header allows. HTTP basics but people don’t know these things.

---

<div class="post-metadata">

### Author: ![shortname](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@shortname](https://forum.interledger.org/u/shortname)
#### Post date: [October 14, 2019, 3:59pm UTC](https://forum.interledger.org/t/redirected-payment-pointers/809/4 "2019-10-14T15:59:58Z")

</div>

I’ve deployed this redirected short-form payment pointer on [my blog](https://www.ctrl.blog/). Hopefully it will still work with Coil.

There’s less data and a lot less unique data in a short-form payment pointer that matches the site’s domain compared to the full payment pointer from Stronhold. Switching from one to the other shaved off an average 2,97% of the total compressed filesize for my webpages.

Please let me know if anyone encounters issues with my redirected short-form vanity payment pointer. (Or if the spec changes so this no longer works.)