default_payment_method
, which can be updated in the User Object. The default_payment_method
will automatically be set to the last payment method used by the user to pay for an order.method
string
stripe
and vipps
, but more options coming soon.name
string
payment_method_id
string
size
number
page
number
sort
string
payment_method_id
string
source
string
card
object
setup_intent
object
Setup Intent
object.id
string
client_secret
string
status
string
succeeded
, require_payment_method
, etc.2019-02-01
POST /payment_methods
with payment_method to ask for an Setup Intent ID. 2)PUT /payment_methods
to update the payment method with the Stripe payment method, e.g.: pm_D1as56d14a6
token
has been replaced by payment_method_id
**Until the 14th of September 2019**, you can still use the APIs as you've used so far. After this date, if you keep using the old Stripe Tokens to do your payments, you'll be getting errors from the Banks requiring further authentication and you'll have to upgrade your APIs accordingly to use the new Payment Intent APIs. Go to our SCA section to read more.SetupIntent
object, where you will find 3 important fields: id
, client_secret
and status
. On your client you will need both the id
and client_secret
to generate a Stripe payment method, using the Stripe SDK.payment_method
string
stripe
for a Stripe payment method.payment_method_id
string
customer_number
string
payment_method
string
vipps
for a Vipps payment method.customer_number
string