Mastercard Crypto Credential

Notabene supports access to Mastercard's Crypto Credential service using the same API access as the wider Notabene API, for ease of use an integration.

A crypto credential is a human-readable username (likealice.m4.mastercard) that you can use instead of a long address when sending or receiving crypto.

These are unique across ALL of mastercard's crypto credential network.

Why use a crypto credential?

  • Simpler and safer than using long crypto addresses
  • Helps ensure funds are only sent to verified wallets
  • Reduces the risk of errors and lost funds

How it works

  1. Create your Crypto Credential with your wallet provider (if supported)
  2. Share your Credential (e.g., alice.m4.mastercard) when requesting funds
  3. The sender’s platform will verify your Credential and route the funds securely

Is it secure?

Yes, Mastercard verifies that Crypto Credentials are tied to legitimate and compliant wallet providers. Your wallet’s address is never shared directly and all communication is encrypted.

Where can I use it?

Crypto Credentials are supported only between compatible wallet platforms and exchanges that participate in Mastercard’s network. Check with your provider to see if it’s enabled.

How to start using via Notabene?

  1. Login to Notabene
  2. Go to Marketplace
    1. Follow instructions →

Further information

Detailed documentation on information flows can be found in Mastercard's developer documentation.

All Crypto Credential notifications will be delivered to your Multi-message webhook, for ease of use.

High level information flows

Generally speaking, crypto credential will be used before interacting with Notabene's APIs. e.g.

  1. generate an alias for your customer, e.g. alice.m4.mastercard`
  2. provide a crypto address for the alias. (this is optional, you can provide one just-in-time when you receive a request if needed)
  3. Assuming you've received a destination alias from another party, create an "alias resolution request" between two aliases, for a given asset
  4. listen for alias resolution, via webhooks, or via polling for results. This will give you your destination blockchain address, and validate the destination can receive the given asset
  5. use the blockchain addresses in txCreate

Did this page help you?