vm1172

[ornate elk]

Hi 👋

[fluid mesa]

Is there somewhere else I can get the reference?

hey

[ornate elk]

It's a cutom value you supply

But it's to help you keep tax calculations separate in a single API call

So you just need to provide the amount and something like ref_123

[fluid mesa]

got it

does the reference need to change if the price of an item changes over time?

or can it be tied to a single uid?

like the productId we have internally for example?

for context: we're only purchasing a single item at a time, so we will only have a single lineItem in the array.

[ornate elk]

If you are only making a single line item calculation the number can be whatever you want, since it's only required that it be unique for each line item. But I would recommend using a value that makes it easy to link it to the payment or product.

[fluid mesa]

thank you! one last thing.

we're calculating tax from our PlatformPayButton which triggers Apple Pay and then we calculate the tax after we receive the user information via onShippingContactSelected.

Does the reference need to change if the user changes their address in a single session or it can stay the same

[ornate elk]

Let me be clear because I think it's lost here. The reference number only matters to the API call

If you make a second API call you can use the same number or a differnet one if it makes sense for your integration

[fluid mesa]

gotcha thank you, this was super helpful

[ornate elk]

Happy to shed what 💡 I can 🙂