Payments API: New flags for createPayment

Announcements
1

You can now flag a payment as seller_keyed_in or customer_initiated to help banks better assess the risk of payments and increase payment authentication rates for sellers, particularly in UK/EEA markets where authentication is mandated.

Check out the docs.

3

Thank you for the update! Flagging payments as either “seller_keyed_in” or “customer_initiated” is a valuable enhancement to improve payment authentication rates, especially in regions like the UK/EEA where authentication is mandatory. This should help streamline the payment process and enhance security for both sellers and customers.

4

For clarification…

Currently in the UK for customer initiated:

  • we use the Card Form to gain a card token
  • then we request 3DSecure verification to gain a new a verification token
  • this verification token is used in the backend to process a payment

So how does this work for seller keyed? Is it just:

  • we use the Card Form to gain a card token
  • this card token is used in the backend to process a payment (and we set seller_keyed)

Is it that simple for these seller keyed / moto transactions?

Does this CustomerDetail object key passed through in the webhooks? I couldn’t see it in the docs.

Thanks,
P

5

Yeah, its that easy. :slightly_smiling_face:

1 Like