# Make a Micro Donation
source: https://developer.mastercard.com/donations/documentation/use-cases/make-donations/micro-donations/index.md

Micro donations allows cardholders to make a recurring donation, which takes into account all the transactions that were authorized on a enrolled card over a month, and make a donation to a selected charity with a fixed amount per authorized transaction.

![Microdonations](https://static.developer.mastercard.com/content/donations/documentation/use-cases/make-donations/images/microdonation_img.png "Microdonations")

## 1. Select a Charity {#1-select-a-charity}

The donor starts by selecting the charity they care about. You determine which charities you wish to present to the donor during the onboarding process.

### Technical Details {#technical-details}

The following diagram displays the sequence of events:
Diagram selectcharity

#### Steps {#steps}

The following details the steps in the above sequence diagram:

1. The Donor selects a charity from the Partner's user interface.
2. The Partner's user interface sends the *charityId* to the Partner's server. The *charityId* associated with the charity is defined during the Partner onboarding process.
3. The Partner's server temporarily stores the *charityId*.

## 2. Select the Donation type {#2--select-the-donation-type}

The donor selects the type of donation they wish to make. In this case they select a micro donation.
Diagram selectdonationtype

### Steps {#steps-1}

The following details the steps in the above sequence diagram:

1. The Partner's server sends the supported donation types data to the Partner' user interface.
2. The Partner's user interface displays the donation type screen to the donor.
3. The donor selects *MICRO*.
4. The Partner's user interface sends the *donationType=MICRO* to Partner's server.
5. The Partner's server temporarily stores the *donationType=MICRO*.

## 3. Enter an amount {#3-enter-an-amount}

The donor then enters the amount to donate (per transaction) and the maximum amount which they accept to donate to the selected charity each month. They should approve the terms and conditions associated with recurring micro donations.
Diagram amount

### Steps {#steps-2}

The following details the steps in the above sequence diagram:

1. The Partner's server sends the *donationType*.
2. The Partner's user interface displays the amount entry screen.
3. The donor enters the *amount* and *max limit* for the micro-donation.
4. The Partner's user interface sends the *amount* to Partner's server.
5. The Partner's server temporarily stores the *amount*.

## 4. Select a Payment card {#4-select-a-payment-card}

The donor selects the payment card they wish to use to make the donation.
Diagram paymentcard Tip: Design Guidelines  

<br />


When designing the manner in which cardholders select their payment card you should:

* If the donor has only one card enrolled for donations, then the same card should be marked as the default.
* A visual indication as to which card is default should be provided.
* If the donor has enrolled multiple payment cards the default should be displayed at the top of the list.
* The rest of the cards should be displayed per the sequence of their entry by the donor.
* Donors should be able to change the default card.
* Payment cards that are expired or soon to be expired should be indicated as such.
* Donors should able to select any branded payment cards(see Note below) when configuring micro-donations.   
  *Note:* Mastercard representative to confirm accepted brands

### Steps {#steps-3}

The following details the steps in the above sequence diagram:

1. The Partner's server sends the payment card data associated with the *donorId*.
2. The Partner's user interface displays the payment card selection screen. Note that the Partner should only display Mastercard branded payment cards for micro-donations.
3. The Donor selects the payment card.
4. The Partner user interface sends the *cardId* to the Partner's server.
5. The Partner's server temporarily stores the *cardId* along with the associated *donorId*.

## 5. Donation processing {#5-donation-processing}

The Partner's server will then send the micro-donation configuration to the Mastercard Donate Service. The Mastercard Donate Service will send the total amount of micro-donations to the Charity's Acquirer each month.

### Technical Details {#technical-details-1}

The following diagram displays the sequence of events:

Diagram microdonationsetup

#### Steps {#steps-4}

The following details the steps in the above sequence diagram:

3. The Partner's back-end server sends the micro-donation setup information to the Mastercard Donate Service.
4. The Mastercard Donations Server generates a unique *donationSetupId* for the micro-donation and stores the setup data.
5. The Mastercard Donations Server returns the *donorId* and the *donationSetupId* to the Partner's server in the response.
6. The Partner's server stores the *donationSetupId* with the *donorId*.
7. The Partner's server generates the micro-donation confirmation screen.
8. The Partner's user interface displays the micro-donation confirmation screen to the donor.

Note: During the setup of a recurring donation, card information will be securely tokenized. More details on tokenization, Please refer to [Tokenization](https://developer.mastercard.com/donations/documentation/api-basics/index.md#tokenization).