Empress Brosephine

[cunning walrus]

Hey Dingbot! 🙂

hi hanzo lol

[spare marsh]

Hello 👋
Can you provide more information?
amount_received reflects the amount collected by Stripe (if charging automatically) or amount sent by the customer for push-based payment method such as ACH Credit Transfer

But yes, the field is controlled by Stripe

[cunning walrus]

Sure thing. So the stripe partner test wants us to create a payment intent using the following parameters:

customer_id
amount
description

We're sending them over, but I guess the testing software Stripe set up is looking for the following:

    expect(completePaymentResponse.body.payment.amount_capturable).to.eq(0);
    expect(completePaymentResponse.body.payment.amount_received).to.eq(123);

but not sure if we should be setting amount_received or stripe shoudl

[spare marsh]

amount_received is a parameter that Stripe will set when funds are successfully pulled from the payment method or pushed by the customer

[cunning walrus]

hmm okay, so likely a error with Stripe then on that front?

like this is what the stripe test bed is sending in:

       'complete-lesson-payment',
        {
            payment_intent_id: scheduleLessonResponse.body.payment.id,
            amount: '123'
        }

wait i might've answered my own question lol ignore me

[spare marsh]

Great! Also, the Integration Challenge for our Professional Developer Certification is an assessment of your skills as a developer using Stripe. In order to pass the challenge, you must solve it without outside assistance 🙂

If you think your app is working but are having trouble passing the tests, please try the following steps:

• Check that you are passing the relevant Cypress test suite on your own machine.
• Check that you are committing to dev and getting our automated feedback comments.
• Dig into the Actions tab to find the logs emitted during your last test run. The logs will include line references to the test files, which you can read to determine which part of your implementation isn't working.

If you are confident that your implementation is working and you have found a bug in the test suite, please reach out to the Training & Certification team via [e-mail] and include the following information:

• Test case ID: You can find the Test case ID by searching the test failure logs in the Actions tab. The name of the test case will end in an ID shaped like "2.3.11". Please include the IDs of test cases that you think are incorrectly failing.
• Failing line of test code: When you read through the failing test cases, please link to the line of code which you think is inaccurately assessing your implementation.
• Your working implementation: Based on whichever test case is failing, please link to the line of code where you correctly implemented the specified behavior.

[cunning walrus]

Will do, thanks 🙂

we've run into a few issues along the way, so just wanted to make sure we weren't hitting another bug lol

[spare marsh]

yeah I'd say reach out to: [e-mail]
As they're the one with full context on this test. Our team wouldn't be able to help with this.

[cunning walrus]

sweet thanks hanzo, have a great day

[spare marsh]

Have a good one & Good luck! 🙂