#mrroyals.

1 messages · Page 1 of 1 (latest)

summer saffronBOT
stone gust
#

Can you send me the ID of an intent that this happened for? I think this may be something I have to direct you to our support to handle more closely but am happy to take a look first

candid bane
#

can i send something from test mode or does it have to be from production

stone gust
#

If you have an example of this in test mode I can definitely look at it

candid bane
#

seti_1NsrYKIACAYMzG11AjSzeLLB

#
{
  "payment_method_data": {
    "us_bank_account": {
      "account_holder_type": "company",
      "account_number": "********6789",
      "routing_number": "110000000",
      "account_type": "checking"
    },
    "billing_details": {
      "name": "Testing Test"
    },
    "type": "us_bank_account"
  },
  "customer": "cus_OdFVRx7aesjA2V",
  "payment_method_options": {
    "us_bank_account": {
      "verification_method": "microdeposits"
    }
  },
  "payment_method_types": {
    "0": "us_bank_account"
  }
}```
#

when i go to the verify page, i see this

stone gust
#

Thanks for the ID, checking it out. And where are you seeing "SA-XXXX"?

candid bane
#

sorry i meant SM-XXXXX

#

i want to be consistent and use only microdeposit values over 0.01 DESCRIPTOR CODE VALUES

stone gust
#

Gotcha, thanks for the clarification. Still looking in to this and will get back with what I can find

candid bane
#

ok thanks

stone gust
#

Hey @candid bane thanks for your patience. Unfortunately it is not possible to force this one way or the other at the moment. We initially try to use the descriptor code format ("SMXXX") and if the bank does not support it, we fall back to the two amount method

candid bane
#

when the descriptor code is sent, will the value sent always be 0.01?

stone gust
#

The amounts will change. The consistent .01 is just a test mode thing

candid bane
#

i see thank you

#

i think i'm all set

summer saffronBOT