List of Contact Payment Methods is MISSING the Credit Card ID in the return payload

API Q&A
1

For this endpoint:

api.infusionsoft.com/crm/rest/v2/contacts/{contact_id}/paymentMethods

The return payload is missing the credit_card_id

  • “records”: [

    • {

      • “contact_id”: 123,

      • “payment_method_id”: 123,

      • “credit_card_id”: “string”, THIS IS MISSING

      • “merchant_account_type”: “STRIPE”,

      • “merchant_account_id”: “string”,

      • “payment_method_type”: “CARD”,

      • “created_time”: “2024-05-21T14:30:00Z”,

      • “card_info”: {

        • “brand”: “string”,
        • “fingerprint”: “string”,
        • “card_type”: “CREDIT”,
        • “last_four”: “string”,
        • “expiration_year”: “string”,
        • “expiration_month”: “string”

        },

      • “status”: “EXPIRED”

      }

    ],

  • “next_page_token”: “string”

}

2

You can use the List Payment Methods endpoint and filter by contact_id to retrieve the credit_card_id, since it’s not available in the /contacts/{contact_id}/paymentMethods response.

3

Is there a plan to correct the Contact Payments endpoint?

4

This is something we haven’t discussed yet. I’ll give you an update here in case it is decided to add it.

5

With all due respect, it IS in the docs as there, it should be corrected, as we have built code as if it is there.

I would rather not do another work-around for something that Keap documented was live already and is not.

This really is a bug that should be corrected.

With all due respect.

6

Looking into this, you’re correct. It is documented, but the value is currently not being returned by the endpoint. I’ll raise this as a bug internally so the team can get it resolved.

Thanks for calling this out.

7

Is there an anticipated fix date for this bug?

8

We expect to release the solution by the end of next week.