# Enemy At The (Billing) Gates

{% hint style="info" %}

#### Originally published [<mark style="color:red;">here</mark>](https://docs.sendwithses.com/random-stuff/enemy-at-the-billing-gates) on our old blog.

{% endhint %}

#### If you sell any product/service online, the journey of money from a paying customer to your bank account has a story to tell.

We launched [**Send With SES**](https://www.sendwithses.com) ~~a few months ago~~ in early 2018. Currently **Send With SES** accepts only USD. This means, if you are a customer outside USA, you are charged in your local currency but your bank/card company pays us in USD. **Send With SES** is based in Singapore. So [Stripe](https://stripe.com) (our payment gateway) which receives this USD amount on our behalf, converts it to SGD and transfers it to our bank account.

#### Well, that’s the theory. Let’s see a real life case ...

A customer (and friend) from India recently subscribed to our Medium Plan ($150).&#x20;

#### Expectations ...

Customer expects to pay USD 150 (INR 10,620) and Send With SES expects to receive USD 150 (SGD 204).

#### Reality ...

1. **Customers Bank adds its fees and charges Customer INR 11,049 (USD 156)**
2. Stripe receives: USD 150 (SGD 204)
3. Stripe currency conversion charges: 2% x 204 = SGD 4
4. Gross Stripe Amount: 204 - 4 = SGD 200
5. Stripe charges: 3.4% x 200 + 0.5 = SGD 7.3
6. **Net paid by Stripe to Send With SES: 200 - 7.3 = SGD 192.7 (142 USD)**

#### In effect, this is what has happened ...

* Customer expects to pay USD 150 but pays USD 156
* Business expects to receive USD 150 but receives USD 142
* **An online payment of USD 150 has generated USD 14 for the middlemen.**

There is nothing wrong in this. Banks and Payment Gateways like Stripe play a '*valuable*' role in the movement of money. This is the price we pay for the ease of doing business.&#x20;

{% hint style="success" %}
**Bank and Payment Gateway charges can be significant. You need to account for these in any** [**CashFlow Projections**](/simple-startup-cashflow-projections-spreadsheet.md) **you do. I would suggest you calculate these charges at&#x20;**~~**5%**~~**&#x20;6% of your revenue.**&#x20;
{% endhint %}

#### Just understand that when it comes to online payments, you always pay more ...&#x20;

<img src="/files/pwgWXKdtrPLpqyTPfKsd" alt="Customer bank statement" width="360">

#### ... or receive less than what you expect.&#x20;

![Stripe statement for Send With SES](/files/Gh6XTEGNuuTvByOin8nV)

#### There are few ways to reduce these charges ...

1. Show and accept prices in local currencies so your customers know exactly how much they are paying. Stripe and most other payment gateways allow you [to do this](https://stripe.com/docs/currencies#presentment-currencies).&#x20;
2. Get a bank account which accepts the same currency as your [settlement currency](https://stripe.com/docs/payouts#supported-accounts-and-settlement-currencies). This will help you avoid currency conversion charges.
3. Register your business in a [low-stripe-charge](https://stripe.com/ie/pricing) country.
4. If you have a large payments volume, you can negotiate with Stripe (or your payment gateway) to reduce them.&#x20;

Do you know of any other ways? Let us know .. hello<@>sendwithses<.>com.

{% hint style="info" %}

#### **Note:** All currency conversions done using [xe.com](https://www.xe.com) on 31-October-2019

{% endhint %}

{% hint style="success" %}

#### Discuss this article on HN: <https://news.ycombinator.com/item?id=21565784>

{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.sendune.com/enemy-at-the-billing-gates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
