Tagging Instructions


BTCMap.org uses an open source dataset provided by OpenStreetMap. If you are serious about supporting bitcoin adoption in your area, you should consider opening an OSM account and contributing to our mission to enable Bitcoiners to easily find places to spend sats anywhere on the planet.



OSM contributors are reminded never to add data from any copyrighted sources (e.g. Google Maps or printed maps) without explicit permission from the copyright holders.

Noobs 🙂

If you only want to add a few places and you aren't planning to maintain them, there is a simple form you can fill and our community will add your data to the OSM database. Our resources are limited so please consider learning how to add and edit data on OSM yourself if you have time.

If you want to verify information on an existing location there is also a simple form to do that.

You can learn more about OSM tagging in the Beginners Guide. We have also made a walkthrough video.

You can also slide into the BTC Map Discord if you have any questions. You'll be editing like a Shadowy Supertagger in no time!

Shadowy Supertaggers 🥷

Earn badges, sats and recognition on BTC Map for your contributions. Your efforts will be featured on our Activity Feed, Leaderboard and you will get your very own Tagger Profile too!

Once you have an OpenStreetMap account, you can use the OSM iD web app to edit the maps directly on OpenStreetMap.org.

A video tutorial can be found here.


Add new or update existing locations directly as you see fit or help with the backlog of submissions from the Noob Form at one of the links below:

If you're a serious tagger, please consider joining the Shadowy Supertagger Team on GitHub so you can manage issues. We have a Supertagger Discord channel to get you onboarded.

Please use the following guidance when editing locations:

Physical Verification and Local Knowledge

Our main goal is to provide the public with an accurate data-set and locals know best. Please try to prioritize locations with close physical proximity to you. Make sure that you're relying on the most accurate data, such as:

  • On-site survey.
  • Direct phone/email (e.g.)/social media survey.
  • Various online sources (be careful about copyright), not all online data is free to use! The official website of the merchant is usually the best online source.

Relying on a form submission without any additional checks is discouraged. An extra step of due diligence should be taken to ensure we are adding accurate data to OpenStreetMap and being good stewards of the database.

Double-check Coordinates

If taking on issues submitted from the Add Location form, you can and should make adjustments to the exact pin location IF you notice it is incorrect. The person submitting the location will not be a mapping expert and that it ok - this is where the extra validation by the Supertagger can help improve the data accuracy. Any submissions with completely invalid locations (like in the middle of the ocean) can be closed as not-planned with the reason provided in a comment.

Source of Data

Each submission will contain information about the source of the data so that taggers will know if it was completed by the business owner, a customer, or by another method. Some submissions may also include contact information which can be used to follow-up if further information is required.

Tagging Guidance

Points, not Ways

Please tag points and not ways. If ways already exist, do not create any additional points and tag the existing ways instead. More information on element types can be found here.

Required Tags

currency:XBT=yes - This denotes the bitcoin currency is generally accepted, but doesn't specify the supported payment types.

currency:XBT=no - This denotes the bitcoin currency is not generally accepted.

The following tags drive the behavior of our apps and so please be as specific as you can when tagging.

payment:onchain=yes - Denotes that on-chain payments are accepted.

payment:onchain=no - Denotes that on-chain payments are not accepted.

payment:lightning=yes - This denotes that Lightning payments are accepted.

payment:lightning=no - This denotes that Lightning payments are not accepted.

payment:lightning_contactless=yes - This denotes that NFC Lightning payments are accepted.

payment:lightning_contactless=no - This denotes that NFC Lightning payments are not accepted.

Verified tags - more information

survey:date=yyyy-mm-dd - Use this tag when the location has been physically verified in person by you. Please use the correct ISO date format as shown.

check_date=yyyy-mm-dd - Use this tag when the location has been verified with local knowledge or extrapolation. Please use the correct ISO date format as shown.

check_date:currency:XBT=yyyy-mm-dd - You can reduce the scope of the information checked by using this tag. For example, if you had only checked the bitcoin tags. Please use the correct ISO date format as shown.

You should verify all the present tags (if possible) when you are adding bitcoin tags to an existing location.

Legacy Tags

payment:bitcoin=yes - This is a very popular legacy tag implying both currency:XBT=yes and payment:onchain=yes. You should remove the payment:bitcoin=yes tag when adding the currency:XBT=yes tag.

We still search for these legacy tags for general display in the apps, but we won't be specific on the payment types supported. You should really remove them when updating with the current tagging rules.

Here is the full list of the legacy places and you are encouraged to verify them. Clicking on any place in that list will open the OSM iD editor. If the place still exists, modify it using the guidance above. If the place doesn't exist, you can remove it from OSM. In a case when a place still exists but no longer accepts bitcoins, simply remove the payment:bitcoin=yes tag.

Other OpenStreetMap tags

OpenStreetMaps is an incredibly flexible platform with tags for a variety of different features.

Here are some useful links that may be useful for your location:

It is easy to look up all the available tags and their use-cases in the OSM Wiki.

Changeset Comments

Every edit on OpenStreetMap has the option to add a changeset comment. This is an important way for other OSM contributors to get a quick idea of what the edit contained. You can include a short description of your changes in this field.

Additionally, another OSM contributor may ask a question for clarification about one of your edits. You should receive an e-mail notification when this happens. Please make an effort to respond to any non-frivolous and respectful questions.

Please include the #btcmap hashtag in your changeset comments so that the activity is associated with our initiative.

Completing Issues

After you have added or edited a location on OpenStreetMap and before closing the GH Issue as complete, it is good practice to leave a comment listing any additional steps you took to verify the accuracy of the data. Please also paste a link to the changeset on OSM so others can reference it and provide additional comments if necessary.