#mark.at.deco

1 messages · Page 1 of 1 (latest)

proud dirgeBOT
scarlet sedge
#

Hi orakaro, I missed your last response from my previous issue (I dont keep discord open). My script worked to figure out which countries can create an onboarding link so that problem is now solved.

clear slate
#

hey, no worry

scarlet sedge
#

But I noticed the capabilites list referred to "klarna" which is odd

clear slate
#

I think it's just the name. Why do you think it should be klarna_payments?

scarlet sedge
#

this is one of the elements returned from the API:

#

{
"id": "klarna",
"object": "capability",
"account": "acct_1LsG5YFwTcGdshSn",
"future_requirements": {
"alternatives": [

      ],
      "current_deadline": null,
      "currently_due": [

      ],
      "disabled_reason": null,
      "errors": [

      ],
      "eventually_due": [

      ],
      "past_due": [

      ],
      "pending_verification": [

      ]
    },
    "requested": false,
    "requested_at": null,
    "requirements": {
      "alternatives": [

      ],
      "current_deadline": 1668487572,
      "currently_due": [
        "legal_entity.controllers_provided"
      ],
      "disabled_reason": "requirements.fields_needed",
      "errors": [

      ],
      "eventually_due": [
        "legal_entity.controllers_provided"
      ],
      "past_due": [
        "legal_entity.controllers_provided"
      ],
      "pending_verification": [

      ]
    },
    "status": "unrequested"
  }
#

all the other "id" s match the API docs except Klarna

clear slate
#

I think it's just the name. Which API Docs you refer to?

scarlet sedge
#

Stripe::Account.list_capabilities("acct_1LsG5YFwTcGdshSn")

#

for instance, the "id" elements for an AU account are: "afterpay_clearpay_payments",
"au_becs_debit_payments",
"bancontact_payments",
"card_payments",
"eps_payments",
"giropay_payments",
"ideal_payments",
"p24_payments",
"sepa_debit_payments",
"sofort_payments",
"transfers"

clear slate
#

I think it's just the name 🙂

scarlet sedge
#

and a german account has

#

"bancontact_payments",
"bank_transfer_payments",
"blik_payments",
"card_payments",
"cartes_bancaires_payments",
"eps_payments",
"giropay_payments",
"ideal_payments",
"klarna",
"link_payments",
"p24_payments",
"sepa_debit_payments",
"sofort_payments",
"transfers"

#

i dont think its a name...

#

what would it be called "id" if its a name?

clear slate
#

I mean, it's just how we call it klarna instead of klarna_payments I agree it looks a bit inconsistent

scarlet sedge
#

every other instance perfectly matches the list you would send when updating an account to request capabilites

dense vector
#

Hi @scarlet sedge I'm taking over

scarlet sedge
#

hi

dense vector
#

Let me know if you have any follow-up questions

scarlet sedge
#

ummm.. so you agree that the "id" from Stripe::Account.list_capabilities should NOT match the capabilities hash keys when calling Stripe::Account.update ?

dense vector
scarlet sedge
#

yes, thats the capabilities hash key you would set to true if you were to request klarna

#

but when you request the list of capabilities against an account, the "id" of the klarna capability is "klarna", not "klarna_payments"

#

everyu other capability matches

dense vector
#

Did I miss anything?

scarlet sedge
#

so when you get the "extended" list of capabilities calling Stripe::Account.list_capabilities you get "klarna", not "klarna_payments"

dense vector
#

OK, you are talking about the capabilities API, not accounts API. Let me take a look.

#

Got it. Thanks for letting me know about this inconsistency, and I'll feed back to the owning team.

scarlet sedge
#

ok

#

cya